Code-Review on vnykmshr

The detection trap

Sun, 08 Mar 2026 00:00:00 +0000

Read something recently about students deliberately making their writing “imperfect” so AI detectors don’t flag it. Removing polish, flattening style, adding imperfections on purpose. Their work got good enough to look suspicious.

We’re doing the same thing with code reviews.

I’ve been on both sides of this. Written a clean abstraction, consistent naming, proper error boundaries, and watched someone in review go “this looks generated.” Years of caring about consistency and now consistency is the tell.

The senior who stopped coding

Tue, 20 Jan 2026 00:00:00 +0000

The terminal closes slowly.

First it’s one meeting. Then a few more. Then you’re “senior” and your calendar is the job. Code reviews replace coding. Strategy replaces shipping. You advise. You guide. You no longer build. Seen this happen. Almost happened to me.

The problem is not the meetings. The problem is losing touch with the trade. Architecture diagrams don’t show you the queries that fan out under load. Sprint planning doesn’t show you the retry logic that fails silently. You can’t review what you can’t recognize.

Coding with LLMs

Tue, 13 Jan 2026 00:00:00 +0000

The tool changed. The craft did not.

Six months with AI assistants.

They write code faster than I read it. That is the problem.

Fast at CRUD. Slow at concurrency. Good at common patterns. Bad at your specific constraints.

The bugs are quieter now. No syntax errors. No obvious mistakes. Just wrong assumptions buried in correct-looking code.

I review more carefully than before. Code I did not write but will debug in production.

On Phabricator

Sun, 01 Sep 2013 00:00:00 +0000

I’ve been using Phabricator for several months now. Code review happened before Phab too – we weren’t shipping blind. Years of SVN, then Mercurial hosted on Unfuddle for a while. Reviews ran through email threads, commit comments, someone walking over to your desk. It worked. But the review was always a side channel. The diff wasn’t a first-class thing. You’d commit, someone would look at it, feedback would come through whatever medium was handy, you’d iterate, it would go in. Review happened around the code, not through a tool built for it.