View profile

🐰 #23 Revive Dead Dashboards, terminusDB, DX; ThDPTh #23 🐰

Three Data Point Thursday
🐰 #23 Revive Dead Dashboards, terminusDB, DX; ThDPTh #23 🐰
By Sven Balnojan  • Issue #23 • View online
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
Are dashboards dead?
(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.
(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 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!
Did you enjoy this issue?
Sven Balnojan

Data; Business Intelligence; Machine Learning, Artificial Intelligence; Everything about what powers our future.

If you don't want these updates anymore, please unsubscribe here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue