Viewing profile — tonkkatonka

One approach could be the role of an automated verification engineer, a cross between a developer experience engineer and quality assurance.

Similar: https://www.aviator.co/blog/do-we-even-need-a-better-github/

Maybe. Humans just can't thoroughly review the amounts of code AI can produce. But the answer is not YOLO and just ship blindly whatever AI created. The answer is to move the human…

Some engineering organizations are measuring AI output via tokens burned, some compare engineers to executive chefs, and some rely on self-reporting.

The response to my piece about killing the code review was loud. This is my attempt to address the comments.

[dead]

Human-written code died in 2025. Code reviews will die in 2026.

What's working, what’s still vaporware, who should be paying attention, and what the real path forward looks like for teams that want to be ready when orchestration goes mainstream…

Stanford researcher shares insights from large-scale studies on developer output, why early AI productivity claims were overstated, and what engineering leaders should (and shouldn…

Four industry veterans — Kent Beck, Bryan Finster, Rahib Amin, and Punit Lad — shared their perspectives on how enterprises can adopt AI coding tools wisely.

Systemic engineering bottlenecks won’t disappear by just throwing AI at them. You’ve got to fix the roadblocks to realize the full value of AI tools.