Where I write about what actually works in software engineering and leadership. Honest lessons from building systems, coaching teams, and creating environments where engineers do their best work.
The Problem Wasn’t Triage Most AI workflows in software engineering still keep the human directly in the middle of triage. The AI might help write code. It might explain a stack trace. It might summar
There’s been a steady undercurrent of people switching tools lately. Copilot to Claude. Claude to something else. Codex quietly entering more workflows. A lot of confidence in different directions, of
It’s been said to me that at times my responses can come across as a “no” first-unintentionally, of course, but real all the same. Not long ago, someone on my team shared an idea they were exploring. I began with a caution, meaning to help them avoid...
The opening sentence of any message often carries more weight than everything that follows. I’ve learned this the hard way. Recently, a report shared something he wanted to pursue. I was supportive — I really was — but my first response came as a cau...
One of the things I’ve always been comfortable with is admitting when I don’t know something. To me, it’s one of the real distinctions between the more and less experienced engineers — and honestly, people in general. When you’re earlier in your care...
Silence can feel heavier than words. In conversations, especially as a leader, there's an instinct to fill every gap, to keep things moving, to show that you're engaged. But I've learned the most valuable moments often come when I do the opposite-whe...
Ownership is powerful. In our team, we lean into it hard - minimal hand-holding, maximum space for people to make their own calls. Most of the time, it works beautifully. But there are edge cases where ownership slips into something else entirely. On...
I've always been a fixer. My instinct is to protect, to solve, to step in. A close friend once told me I have “White Knight Syndrome” - I never checked if that's really a thing, but it fits. At my core, I want to take away the struggle, to shield oth...
In 1:1s, whether with my reports or on the rare occasion with my own lead, I’ve noticed something: the safe answer. You know the one. It’s in response to “How are you doing?” It’s polite. Acceptable. Technically honest — yet designed to sidestep the ...
A quiet team can feel safe on the surface — no conflict, no interruptions, no awkward moments. But here’s the problem: with a quiet team, you don’t know what you don’t know. When people keep thoughts in their heads, you can miss out on ideas, risks, ...
Technical ownership sounds great on paper. It means someone cares. Someone is responsible. Someone knows the system inside out. But like most things in engineering, it comes with tradeoffs. At a previous company, I was the sole owner of two codebases...
There's this quiet myth in engineering that once you hit “senior,” you'll just know. You'll have all the answers, solve problems on the fly, and be the go-to for anything and everything. But here's the truth I've come to learn: I often prefer not to ...
Every engineer has their perfectionist phase. I certainly did. There's a season early in your career where every line of code must be beautiful, every edge case handled, every abstraction future-proofed. That desire to do things “right” feels noble -...
In the pace of startup life, where speed often trumps formality, it's easy to sideline documentation - especially when a piece of work doesn't feel “big enough” to warrant it. But I've learned the hard way that even small misunderstandings can cause ...
Alignment isn't just about goals on paper-it's about shared understanding, belief, and behavior across the team. And when it's off, it doesn't always show up in the obvious ways. Often, the earliest signs are subtle. The First Signs: Repetition, Rein...
When you join a new team, it’s natural to want to prove yourself. But earning trust isn’t about delivering fast or showing off what you know—it’s about how you show up, listen, and slowly become part of the fabric of the team. At Loop, my first week ...
One of the most common fears for leaders is losing visibility. So we overcorrect. We hover, we ask for updates too often, we over-explain things that people were already doing well. We micromanage. But here's the thing: I've never really been the typ...
I used to think being “good at receiving feedback” meant nodding politely, taking notes, and promising to do better. But over time, I've learned that how we receive feedback can shape our entire trajectory-and it goes far beyond politeness. When feed...
Creating a culture of psychological safety is often misunderstood. It’s not about shielding people from hard conversations or protecting them from failure. It’s about creating an environment where people can take risks, can own mistakes, and can give...
Redefine What Innovation Looks Like Not every breakthrough is a moonshot. Sometimes innovation is finding a faster way to deploy, automating a flaky test, or rethinking how a screen flows. Encourage your team to innovate within constraints. Small, pr...