Wastes That Kill Your Flow

In my last post, I introduced nine wastes that hide in software teams.

Nine Wastes Hiding in Your Software Team

Measuring the productivity of software engineering teams is notoriously difficult and can often backfire. However, we don’t need complex metrics to recognise when time and effort are being wasted.

Blazing fast search

When I started building medi, my command-line notes manager, the goal was a fast, local-first workflow. But how fast is fast? Could it stay fast at scale? With a database of thousands of notes, would search grind to a halt?

Bringing tbdflow to the IDE

I love the terminal, but yes, most developers live in their IDE. It’s their primary workspace, and modern IDEs like IntelliJ have great, integrated Git support. You can stage, commit, push, and manage branches without ever touching the command line.

tbdflow ❤️ monorepo

Monorepos are a powerful strategy for managing code. By keeping all your projects in a single repository, you get a single source of truth, simplified dependency management, and easier cross-team collaboration. As influencial thought-leaders and others in the DevOps space have pointed out, monorepos are a natural fit for Trunk-Based Development (TBD) because they both revolve around a single, shared mainline of code.

Looking under the hood with a dry-run

One of the most valuable pieces of feedback I’ve had about tbdflow came as a simple question:

CHANGELOG.md

I’ve seen some teams and projects having really nice CHANGELOG.md and release notes but knowing from experience, writing release notes by hand is a pain. Scrolling through git log, guessing which commits count as features or fixes, and hoping you don’t forget something important isn’t exactly fun.

How I created the demo GIF for tbdflow

All projects need a good README.md, It’s the front door to the project and it needs to quickly show a potential user what the tool does and why it’s valuable. I put a lot of effort in having a good README for tbdflow but it was still static text, and the examples was buried deep down.

Why did I build medi?

Where are my files?

Stop re-installing your tools

When you publish a CLI tool on crates.io, you’ll often get a familiar question (at least I did):