Ever feel like your brain is blended and you can't even keep up with the things you're learning? Me too. But the good shit stays.

A project is something you do, a product is something you own.

Debate less, ship more.

Products not projects. Outcomes not features. Iterate.

Going from Big Vision to Series of Executable Steps is a key skill for senior+ engineers. PMs can help but they don't know everything.

How do you choose what to work on first? As an empowered engineer that's a key skill.

Accelerate is the empirical research behind books such as The Phoenix/Unicorn Project and (parts of) Software Engineering at Google. I loved it.

You can't learn to ride a bike from reading a book.

Why do some projects ship and others seem to drag on forever? You need 3 people to get this right.

A long design phase without shipping kills many software projects. Here's a story from production I haven't shared before.

You can't fix everything. Focus on the next big thing and let the small fires burn.

All the hard lessons learned using feature flags in production. Skips the why and gets to the how.

here's war story from last summer. I've talked about it in workshops but haven't written it down before. It's for a book I'm working on.

Many engineering challenges start with your roadmap

effective engineering teams should work *with* their product owner/manager, not *for* them

Unearth the surprising connection between the CIA's Simple Sabotage Manual and your productivity, and learn how to transform tiny actions into big wins. Dive into Swizec's engaging exploration of how small actions can make a huge impact on your progress.

The Buxton Index measures an entity's planning period and explains many of your work dynamics.

Lessons learned from running GPT-4 on lots of data using the same task.

What if you could focus on the fun _engineering_ part of your job, not on coding? You can!

You can't escape Conway's Law. Might as well use it for good.

Behind every thriving team is a dedicated manager who shields them from corporate chaos, sacrificing their own well-being for the team's success.

Learn how to build a powerful semantic search engine in just 2 hours with the OpenAI API.

ole Musky bought Twitter and the tech community threw a collective shitfit. The atmosphere of ragequitting, hand wringing, and aloof defiance gave me time to reflect: Why am *I* here?

When's the last time a piece of tech blew your mind? I tried stable diffusion on my new ipad and wow

how do you catch a critical deadline that cannot be missed? We're talking external stakeholders, millions on the line, and it all hinges on *your* team getting it done on time. No overtime

New members on our team invariably say 2 things: 1. Wow I've never seen a team move this fast 2. This approach feels weird. I'm uncomfortable Teams like this are not common.

If your approach works so well, why isn't every team doing this?

My entire career I've never seen a sprint finished on time. The new manager said "Oh I think we can fix that" ... 18 months later he proved me wrong

How would you rollout the covid vaccine for max fairness and speed?

A few years ago I was playing around with JavaScript trying to find the cleanest way to implement callbacks in functions. Primarily I wanted a readable way to make certain the last argument passed is a callback, withut having to rely on knowing how many arguments there are and so on. Instead I stumbled upon a pretty cool feature of how javascript handles function arguments.