-
Building Software Was Never the Hard Part
Building software is easier than ever. The AI tools work well enough really well. The low-code/no-code platforms work well enough really well. The vibe coding works well enough really well. That marketing director who shipped an internal tool over the weekend? They’re not wrong to feel empowered. They actually built something, it actually runs, and…
-
People Always Have an Opinion When They See a Wireframe
Getting good feedback is one of the hardest parts of product work. You send a doc. You ask for thoughts and it’s usually met with silence or “Looks good to me.” You follow up for more and maybe one person responds or you get, “move the button in the flow to the top right”. Everyone…
-
Implementing an RFC Process That Engineers Don’t Hate
The hardest part of an RFC process isn’t designing the template. It’s making sure people actually use it without feeling like they’re filing TPS reports. I’ve written before about When to Write an RFC and When Not To and how it helps in formalizing technical decisions as companies scale. This is the tactical follow-up on…
-
When to Write an RFC (and When Not To)
Growing engineering organizations face a communication problem that more meetings won’t solve. When you’re small, decisions happen naturally. Everyone knows what everyone else is working on. You can sit around a table and discuss problems and solutions. But as you add engineers and teams, that breaks down. You start seeing the symptoms: conflicting architectural decisions…
-
Shadow IT Isn’t a Threat, It’s a Signal
Someone on your team is using an AI tool you didn’t approve. Your solutions engineers built a custom data ingestion pipeline without telling anyone. A pre-sales engineer spun up a demo feature that customers are now asking about. Your instinct might be to enforce the policy and shut it all down while reminding everyone about…
