I've been using claude code for the past 2 months and I spend most of my time in it's planning mode, which is just amazing to flesh out a good plan. After havin

I've been using claude code for the past 2 months and I spend most of my time in it's planning mode, which is just amazing to flesh out a good plan. After having a very good/specific plan, it usually one-shots the implementation. If I have a bad plan, it executes poorly. The other thing that makes a big difference is using a language that has strong typing and a strict compiler. You can allow claude to call the complier, analysers, debuggers and so forth and it works amazing to keep code quality consistent if you tell it always follow your existing patterns. Lastly, I figured out recently, quite by accident, that claude can call adb/logcat on a connected android device, to ingest real debug logs while my app is running, which can be a firehose of logs. It cuts through it like candyfloss and spots runtime errors significantly faster than a human can read all those log. It found a bug for me that was nearly impossible to find with the IDE & breakpoints, just by ingesting the debug/logcats outputs directly. So overall the article is great, I do think the way we work can and will fundamentally change in the coming years.