The Problem: Test Database Friction
As the team at Mental Health Match grew, we faced a familiar challenge: new developers struggled to get their test environments working correctly. Our integration tests required a properly seeded database with reference data and realistic sample therapist profiles. Without it, tests would fail with cryptic error messages:
It’s funny how deeply ingrained some tools can become in our workflows. Back around 2012, I stumbled upon Robby Russell's Oh My Zsh, and like many, it felt like a revelation. Suddenly, my terminal wasn't just a command line; it was this vibrant, supercharged environment. It was the gateway drug for many of us into the rich Zsh ecosystem, and for that, I'm genuinely grateful. It made the shell approachable and, dare I say, fun.
For over ten years, Oh My Zsh has been a steadfast companion. But as with all things in tech (and life!), needs evolve, perspectives shift, and sometimes, the tools that once felt indispensable start to feel a bit... much.
(Updated May 13, 2025)
I was watching popular AI-trending youtuber Matthew Bergan build a local environment for AI development the other day. And it was amazing how issues like virtual environments, package mangement and versioned dependencies were huge pain points and hurdles.
It occured to me that with all the excitement about AI and tooling, that there's common issues that folks who aren't used to the command line may run into – and be stopped dead in their tracks.
"We need a roadmap, is there a template we can use?"
I see this request all the time. From clients to peers, developers to product execs.
I get it. A roadmap feels like such a great thing, its an artifact that says "this is what we're doing, and how we'll do it".
In that way, its also misleading. Because most roadmaps look like this: