Career on vnykmshr

The compiled person

Mon, 13 Apr 2026 00:00:00 +0000

I stopped being able to explain why I knew. That’s how I found out I’d been compiled. The patterns still fire, the fixes still land, but the source files are gone. No debug symbols, no way to step through my own reasoning.

A junior asked me how I’d known the bug was in the retry logic before I’d even read the function. I’d skimmed twenty lines. The answer was somewhere in my head. I tried to retrieve it and got nothing. Just the conclusion. The shape was right. I couldn’t tell you which pattern fired or where I’d learned it.

The side project mirror

Fri, 03 Apr 2026 00:00:00 +0000

The job title says architect. The side project says “why is this Dockerfile 300MB, let me fix this real quick” – three hours later, still shaving layers, completely happy.

Nobody assigns you ops on a side project. Nobody assigns you anything. But there you are, writing monitoring for something with twelve users, eleven of them are you in different browsers.

The role is what someone else decided you were good at. The side project is what your hands reach for when nobody’s directing them. Sometimes they match. Mostly they don’t. The backend engineer with strong opinions about font spacing. The tech lead who’d rather be tailing logs than running standups. The platform architect who writes a blog engine from scratch and tells you with a straight face that the existing ones were fine, just not the way they’d do it.

What compounds

Fri, 20 Mar 2026 00:00:00 +0000

Something shifted. Not the AI thing – everyone noticed that. What counts as proof.

Used to be your resume, your title, the logo. Still opens doors. But the gap between “I can do X” and “here’s the commit” got wide enough that both sides feel it. A merged PR has a commit hash. A CVE has a number. A library someone depends on has a git log. Credentials got easier to claim. Artifacts didn’t.

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.

Clean designs

Thu, 28 Oct 2010 00:00:00 +0000

Two years ago I walked into a classroom in our office. Not a meeting room. An actual classroom, whiteboard, rows of chairs. The company had hired an instructor to teach the new hires Java. Two hours a day, three days a week, for three months.

The training gave me syntax. Objects and classes. How inheritance works. What an interface is. The words for the things you do in code. Every week we wrote a small program and the instructor reviewed it.