< Skills I'm ceding to AI

Last year I used Claude Code to write something in Rust. I'm "read the book" familiar with Rust, but not much of a coder in it. I could follow along with the AI, but unlike other languages, I didn't feel the need to nitpick. Not quite vibe-coding, but in that direction. It was extremely productive and liberating.

That got me thinking: which of my everyday skills could I hand over the same way? They all have lots of prior art and fast feedback loops: areas where AI has vast training data and I can verify the output without needing to have written it myself.

I don't think giving up skills to AI arbitrarily is a universally good idea. But doing it with consideration is the way forward. Here is my current shortlist:

My aim on all these fronts is to stay competent enough to be "read-only" — a good reviewer, not a writer[1].

Then there are skills where the feedback loop is slow or the failure modes are subtle:

Another motivation here is the "Death of the Full-Stack Developer".

I've been (arguably) in the Full-Stack space for some time[2], but I do realize the limitations of keeping that title. Jumping from SQL to yet-another-browser-api to CORS to cookie edge-cases makes your head spin.

There are now enough APIs and frameworks that you really do need to pick your battles. AI lets you pick them more deliberately. Hand over what's well-trodden and easy to check.

Also read: Your Brain on GPS, Skilled Humans in the Loop, and Still choose boring technology.

Discuss and share via the meta page . Filed under AI, Code, and 100PR.

Footnotes

  1. Arguably that's the core competency of a Full Stack developer anyway. ↩

  2. Non-ironically: in Australia "stack" is often a term for crashing or wiping out. ↩