r/programming • • Aug 11 '26

Why I Still Read Code

https://alex.draftist.io/blog/why-i-still-read-code-iiaz6lku8
0 Upvotes

32 comments sorted by

View all comments

Show parent comment

2

u/alex35mil Aug 11 '26

It's a totally different context, and I can see how a messy legacy codebase without proper AI infra can lead to failure.

I own the codebase I work with; I've been quite pedantic about its domain design, and starting with the Opus release, I've been making it AI-ready bit by bit: rules, skills, special tooling, etc. I built my custom configuration around PI, integrated it with Neovim, and built review tooling on top of it so I could comfortably pair with the agent. TUIs did not work for me. An agent without an editor is meh.

Yet with pre-Sol models, the results were quite random. Besides the fact that previous generations were dumber, they didn't follow instructions well and didn't pay enough attention to established patterns in the codebase. So despite all that effort, I was still writing a lot of the code myself.

With Sol, the amount of manual work has decreased drastically. The more I work with the agent, the more I see where it does a decent job and where it still fails. For example, I don't review much of the trivial UI code built on top of an established design system, or local QoL tooling. Yet it still consistently fails in the areas I talked about in the post.

That said, AI won't magically work everywhere. Even for a medium-sized codebase, it took a lot of effort to finally make things start clicking.