
Writing technical standards people follow
Most technical standards are written once, read twice, and ignored. What separates the ones teams follow: short, reasoned, enforced by tooling, and ow
Tag archive

Most technical standards are written once, read twice, and ignored. What separates the ones teams follow: short, reasoned, enforced by tooling, and ow
A team chat goes quiet for weeks, then someone posts "How is everyone?" into the void and nothing...
Defensiveness Is Ruining Your Code Reviews (Here's How to Fix It) A few years ago, I...
Feedback isn't just about code reviews. Create a culture where everyone feels safe to share ideas and...

I spent a day inside a small, YC-backed team in London expecting to learn about product or strategy. What stuck with me was smaller and more useful: great output is in the details, and behind every small detail there was intent.
Code ownership isn't about blame. It's about accountability and pride. Foster a culture where devs...
Sebagai CTO, saya belajar bahwa tim yang sehat tidak selalu menghasilkan kode sempurna. Ini 5 tanda yang justru lebih penting dari code quality.
Hi y'all. It’s been a minute. (Is that something we only say in New York? If you say that and...
Before I get into this, I need to address something from my last post. I used the word "terrified"...
Imagine this: Your development team is cruising along, deadlines are being met, and everything feels...
It’s college football season here in the US and that means I get lots of quality time with my...

A quiet team can feel safe on the surface — no conflict, no interruptions, no awkward moments. But...