Jake Lundberg's Blog

When an agent helped write a pull request, the first question most reviewers ask is who wrote it.

When your team stops trusting its AI code review, the obvious fix is to add a second AI.

On a lot of teams, code that a pair of devs wrote usually gets a lighter code review.

A one-line warning in my deploy log took my site down for thirty minutes.

Nothing logs a 1:1.

Tech debt you can see, point at, and put on a ticket.

When making something gets cheap but judging it stays expensive, the cost slides downstream...social media did it to your feed, AI code generation does it to your repo.

The risky PR is rarely the big one...it's the one carrying money code, a migration, or a red build, regardless of size.

Deleting a year-dead feature flag turned a forgotten feature back on and broke production...here's why flag cleanup is a runtime change, not tidying, and how the context you need decays while the flag sits there looking harmless.

Big PRs don't come from lazy engineers.

Most merge standards are wiki decoration.

The three targets I set for my engineering team — PR size, open-to-merge time, and change failure rate — and why these are the three that matter.

Most code-review checklists ask "does this work?"

Building software is like traveling between destinations.

Hello, hello!

"If you can't explain something to a first-year student, then you haven't really understood."...

Ever feel like you're juggling too many tasks, and letting too many things fall through the cracks?...

Let's face it: in software engineering, change is as inevitable as bugs in a first release.

Once again, I'd like to start this week's post off with a question.

Continuous learning.

Hello hello 👋 I'd again like to start this week's post off with a question.

Let's face it: the world of software development is massive, and it's only getting bigger.