This breakdown of the CLI shift is razor-sharp. The Jaana Dogan example really cuts through the noise, when a Principal Engineer at Google builds in an hour what their team iterated on for a year, that's not just tooling it's a fundamental workflow realignment. I tried the multi-tool appoach last quarter (Claude for arch, lighter tools for docs) and the context window consistency alone justfied the switch. IDE's still have a place but orchestartion at the terminal just handles complexity better once you get past the initial learning curve.
Thank you, and agree 100%. I feel like now giving up the IDE is the dividing line between engineers that "get it" (no reflection on skill), and those who don't. Or, in referencing an earlier article, do you want to be a "Canut" or a shop owner? (hmm good topic for a new article)
This breakdown of the CLI shift is razor-sharp. The Jaana Dogan example really cuts through the noise, when a Principal Engineer at Google builds in an hour what their team iterated on for a year, that's not just tooling it's a fundamental workflow realignment. I tried the multi-tool appoach last quarter (Claude for arch, lighter tools for docs) and the context window consistency alone justfied the switch. IDE's still have a place but orchestartion at the terminal just handles complexity better once you get past the initial learning curve.
Thank you, and agree 100%. I feel like now giving up the IDE is the dividing line between engineers that "get it" (no reflection on skill), and those who don't. Or, in referencing an earlier article, do you want to be a "Canut" or a shop owner? (hmm good topic for a new article)