Tag: Engineering Practices

We made writing code nearly free, and the constraint didn't disappear — it moved downstream. Agents now produce more code than humans can carefully read, and review is where velocity quietly dies. Here's why verification is a skill to engineer, not a chore to endure.

The most productive people I know are also the laziest — in the right way. They automate mercilessly, delegate to machines, and refuse work that doesn't need doing. AI makes this approach accessible to everyone. Here's how to be strategically lazy.

Sprint planning sessions that pull every team member into a room for two hours are a drag on productivity. Not everyone needs to be there — here's how alignment should actually work across teams, and why selective participation produces better plans.

Side projects used to be an all-week affair — late nights, lunch breaks, any spare moment. But as work demands grew, I learned to protect my weekends for the code that matters most. Here's why side projects became a weekend ritual and how that shift made me more productive at both.

We used to measure engineering output in pull requests. That metric is about to break in ways that matter. The real artifact of work is shifting upstream — to the prompt, the spec, the intent. Here's what that means for how we work, review, and hire.