Pocock's definition of 'code quality'

What does "code quality" mean, in the age of coding AI?

Matt Pocock - an engineer and thought leader - gives my favorite definition. To quote him directly from an interview:

"Let's say you have a thing that you notice the agent always gets wrong, and you want to make that just impossible... That sort of comes down to code quality.

A good codebase is a codebase that's easy to make changes in. Easy to change stuff without things screwing up.

And that means that you have a lot of guard rails that the agent or the human is constrained to very narrow paths."

The key insight, in the middle:

High code quality means it's easy to change the codebase, without screwing things up.

That means easy for humans, and easy for coding agents.

Which is why coding AI is not a magic bullet, why engineering isn't dead, and why the need for software development expertise ain't going away.

If you think otherwise, I dare you to find even one software engineer job listing, where they say they don't care if you know how to code well. Go ahead and look; I double dog dare you. You won't find a single one.

But coding AI is important. Those same job listings are increasingly calling for not just experience, but actual expertise using coding agents, and using them well.

Also, I see the phrase "strong verbal and written communication skills" over and over in job listings. Apparently that's important, too.

Fortuitously, Boosted Code teaches you every single thing mentioned above.

If you are already in BC, now is a good time to re-watch the 'first hour strategy' video, in the 'Welcome' course. That's really all you need to focus on doing; then the rest will fall into place.

More about what you get from Boosted Code here: