I think many struggle with OLTP relational databases because we do a bad job educating people, and many of our best practices are not actually best practices. RDBMSes can do a lot more than most people think. Wanted to share a few contrarian principles that helped me out w/ them: 1. It's often better to add tables than alter existing ones. This is especially true in a larger company. Making changes to core tables that other teams depend on is very risky and can be subject to many approvals. This reduces your team's agility a lot.

We just shipped a new blog post I wrote on the @dagster blog. It's a step-by-step tutorial on how to build a ChatGPT-like bot that can answer technical questions about any GitHub repo using a great new Python library - @langchain - and the @OpenAI API. (1/4) One of the big challenges we've faced at the @dagster project is the rapid growth of our Slack community. We want to deliver a great support experience, so this means we have an engineer on-call basically full-time during the workday just answering Slack questions. (2/4)

the node.js readable stream api is wild. some great quotes from the docs: Readable streams effectively operate in one of two modes: flowing and paused. These modes are separate from object mode. A Readable stream can be in object mode or not, regardless of whether it is in flowing mode or paused mode.