1. DevToolsDigest
  2. issue #326

DevToolsDigest: Issue #326

This week's digest includes news and resources from Rill Data, Heroku, and more.

Subscribe to the DevToolsDigest

All you need is 3 minutes a week to stay ahead of the devtools space. Get the most relevant industry updates, insightful discussions, and top-notch resources delivered straight to your inbox.

    2 MIN

    The Week in Developer Tools

    Introducing a SQL-based Metrics Layer Powered by DuckDB

    For metrics to be useful, they need to be explorable. If revenue is trending down, it could be because MAUs are off, or because of uptime issues in a particular cloud region. Investigation into metrics requires fast exploration, and fast exploration requires a fast backend.

    Contributing to the Twelve-Factor Project

    The Twelve-Factor approach to software development has inspired architecture and development practices for more than a decade. Now, through open source collaboration, we have the opportunity to evolve these principles to better serve today’s developers while maintaining the operational rigor that made Twelve-Factor so influential in the first place.

    Industry Research

    AI Analogies

    There is a lot going on right now! If you read any news about AI at all, you’ll see all kinds of new tools, debates about whether AI is really useful, whether something is AGI or not1, and so on. Analogies by definition are just an approximation so they don't really tell you the whole story, but they can be helpful as a tool to understand the moment we are in.

    API Economy Trends for 2025

    More organizations are making use of APIs from external sources than ever before. And an ever-expanding suite of APIs is available to choose from. These APIs offer direct functionalities or access to datasets and are used as components that help the API user build out their digital product (or automated workflow) to enable transactions or tasks to be performed.

    OKRs for Internal Products

    If OKRs measure success in terms of customer behavior, it’s relatively easy to identify the humans who are your customers. These are the buyers and users of the products and services you build. What if, however, the products you make are used by internal teams? Who are you customers in that situation? And, equally as important, how do we measure their success?