Fragments

Short-form thinking on software craft, AI's effect on developer skill, engineering philosophy, and what we lose when we optimize for speed over depth.

All fragments 4 results

Research 3 MAY

I’m sure you remember that small hesitation when writing "return" — I do too. And how deep the reason goes genuinely surprised me.

A CPU Story: Why must a function return?

#Craft #Muscle-Memory #Programming #Learning

Go to paragraph

Thinking 2 MAY

Seniority is not measured by how much code you have written in the past. It is measured by owning the full cycle — knowing how your code will be maintained, what it produces when compiled, how it behaves across environments, and being able to develop with the real costs in mind: cpu cycles, memory allocation, request throughput. And then passing all of that on to your team.

standalone thought

Thoughts 1 MAY

The lazy developer is now a Vibe Coder — and we hate saying it out loud.

We’re Forgetting How to Sharpen Our Tools

#Craft #AI #Vibe-Coding #Engineering

Go to paragraph

Thoughts 29 APR

From Notepad to IDE, from IDE to the chat window. We gained some things, but lost far more.

We’re Forgetting How to Sharpen Our Tools

#Tools #Learning #Muscle-Memory #Ide

Go to paragraph