Post

"Do You Still Read Code Written by AI?": The question every developer is asking their colleagues. Here's my honest answer: I use AI every day, and it's made me more productive than ever. But I still review every line that ships. Luca and I will unpack it all next Wednesday!

Matteo Collina

@nodeland.dev

My bottleneck is no longer coding. It's review. When AI hands me a fix, I don't just check if the tests pass. I ask: does this actually close the attack vector? Are there edge cases the model missed? Is this the right fix, or just a fix?

Matteo Collina

@nodeland.dev

That's the shift I wrote about in my newsletter piece "The Human in the Loop." Review is now the primary skill of a senior engineer, not one of many. adventures.nodeland.dev/archive/the-...

Matteo Collina

@nodeland.dev

The moment I stop reviewing is the moment I stop being responsible for what I ship. AI is just another contributor now. I review its PRs like I review anyone else's, and I decide if it's good enough.

Matteo Collina

@nodeland.dev

My worry isn't that software development is dying. It's that "I didn't review it, the AI wrote it" becomes an acceptable excuse. At AI speed, the scale of damage when you ship code you don't understand is enormous.

5/10/26, 3:59 pm0 reposts0 likes

Matteo Collina

@nodeland.dev

An academic paper just confirmed what I've been arguing: the bottleneck is judgment, and it's getting more valuable. Not prompting. Not "agentic infrastructure." Judgment. adventures.nodeland.dev/archive/the-...

Matteo Collina

@nodeland.dev

So do I still read code written by AI? Every single line. The human in the loop isn't a bug to be optimized away. It's the feature to protect. See you next wednesday for the full conversation 👇 streamyard.com/watch/PDmxZD...