From Code Writer to Code Judge

The biggest challenge in AI coding adoption is not technical. It is psychological. I was talking to a developer recently who wanted to carefully curate which work to send to Tembo, saving most of the hard problems for himself. I told him: send everything. If the agent gets it wrong, you can still do it manually. If it gets it right, you just got the work done way faster. There is no downside.

He was uncomfortable with that, and I understand why. Most developers built their identity on being the person who writes the code. Asking them to hand off the writing feels like asking them to give up the part of the job they actually enjoy. But this requires a fundamental mindset shift, and there is no graceful way around it.

The role is changing from primary code writer to wise critic and reviewer. Even if you are a 21-year-old developer two years out of school, you need to step into the seat of the experienced judge — the one who approves or rejects engineering work based on architectural fit, business context, and good taste. That is the seat that does not commoditize.

Within five to ten years, I think 80% of code will be written by AI and reviewed and accepted by humans. The value is not in the typing. It never really was. The value is in the judgment, the architectural decisions, and the understanding of what the business actually needs. The typing was just the artifact people happened to be paid for.

I have argued elsewhere that democratizing software engineering is what makes this shift unavoidable. Once non-engineers can request real work, the senior engineer's only durable job is judgment. The faster you embrace that, the better positioned you are. The longer you cling to typing, the harder the next five years are going to feel.

— Ry