I call it Tradcoding. Not using AI for anything. (You just copy-paste from StackOverflow, as our forefathers once did ;)
I also have two levels "beneath" vibe coding:
- Power Coding: Like power armor, you describe chunks of code in English and it's built. Here you outsource syntax and stdlib, but remain in control of architecture and data flow.
- Backseat Coding: Like vibe coding but you keep peeking at the code and complaining ;)
- Vibe Coding: Total yolo mode. What's a code?
I feel like this distinction isn't made often or clearly enough. AI as a superpowered autocomplete is far more useful to me than trying to one-shot entire programs or modules.
Agreed. I'd also add that I have varying levels of watchfulness: paid work I inspect (and understand) every line, and iterate. JS for my blog, I inspect. Throwaway scripts, I skim.
I dunno; I think Tradcoding would go beyond regular modern coding, and rather imply some kind of regressive Nara Smith "first grind and sift the flour in your kitchen"-style programming.
No Internet connection, no cache of ecosystem packages, no digitized searchable reference docs; you sit in a room with a computer and a bookshelf of printed SDK manuals, and you make it work. I.e. the 1970s IBM mainframe coding experience!
This isn't terribly far from "Knuth-coding" to call it something - imagining the program in WEB in its purest form and documenting what it does, almost irregardless of the actual programing language and how it is done.
I did something kinda like that when I realized I worked way better when I disconnected my internet. So I had to download documentation to use offline. Quite refreshing honestly.
Not necessarily more efficient, but it feels healthier and more rewarding.
If you have a good stdlib (which in my case would mean something like Java for its extensive data structures) Tradcoding is entirely possible.
I'm waiting for someone to polish a well thought out interface for power coding
The process that Get Shit Done forces is pretty good, with Claude Code as the interface.
Harness/fill in the gaps coding: you define a bunch of tests/reference output/validation procedures, let the AI spin until all lights are green
I think 'tab coding' should be a distinct group. When wast majority of the code just written through accepting autosuggestions.
There's also the popular Tab Complete, which is roughly on the Power Coding level.