š° #23 Revive Dead Dashboards, terminusDB, DX; ThDPTh #23 š°
š° #23 Revive Dead Dashboards, terminusDB, DX; ThDPTh #23 š°
How to revive your dead dashboards, a cool new graphDB called terminusDB, and developer experience for dataĀ guys.
Data will power every piece of our existence in the near future. I collect āData Pointsā to help understand & shape this future.
If you want to support this, please share it on Twitter, LinkedIn, or Facebook.
(1)š® Make Dashboards LessĀ Dead
This is a great post by Tristan Handy. I think thereās a good use case for dashboards just as there is for any of your āBI artifactsā. This post contains an excellent plan on making dashboards āless deadā.
The post contains a roll-out plan for trustworthy dashboards & reports written by Alexander Jia:
Create a single source of truth in your dwh for a few curated data sets
Release curated standard-reports focused on high-level KPIs, work hand in hand with leadership
Support ad-hoc exploration of these curated data sets
Slowly chip away at old reports and replace them with better, new, curated ones
A recent post, Dashboards are Dead, sparked a conversation about the future of data reporting.
blog.getdbt.com Ā ā¢Ā Share
(2)š terminusDB
Iāve just written about data as code and realized not too many databases actually provide decent versioning. Dolt does, but then thereās a big void. This project however looks promising, itās a versionable graph document store, essentially made for most machine learning use cases.
They apparently use their own graph language WOQL which I donāt like. Iād rather see some convergence in the space of graph languages. But still the project looks worth a try.
They claim that āterminusDB is open source foreverā and provide a āterminusHubā on top of it as a commercial offering. That sounds like a decent package.
TerminusDB is an open source model driven graph database for knowledge graph representation designed specifically for the web-age.
terminusdb.com Ā ā¢Ā Share
(3)š„ Better Developer Experiences for Data Guys
I just stumbled over another ThoughtWorks article rallying for better ādeveloper experiencesā. Yet for some reason, I feel this topic is even more pressing in the realm of data.
And by that, I mean both, the data engineers, the machine learners, and the data scientists of this world but also the developers which should be able to work with their data easily. A developer shouldnāt spend his time writing a track function, he should be able to track his newly developed feature with one line of code!
So I suggest you read the article and think about how the data experience probably is for your developers. If youāre a developer, I suggest thinking about whether you donāt see any ways to āexchange the handsaw you got for a chainsawā.
Why you should invest in good Developer Experience today | ThoughtWorks
In over 50% of organisations, software developers only spent 30-40% of their timeā¦.
www.thoughtworks.com Ā ā¢Ā Share
š In Other News &Ā Thanks
Thanks for reading this far! Iād also love it if you shared this newsletter with people whom you think might be interested in it.
P.S.: I share things that matter, not the most recent ones. I share books, research papers, and tools. I try to provide a simple way of understanding all these things. I tend to be opinionated. You can always hit the unsubscribe button!
Data; Business Intelligence; Machine Learning, Artificial Intelligence; Everything about what powers our future.
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue