Writing code was never the bottleneck

Hard, hard disagree here from my view.

> Since engineers have consistently said they wish they had more time to write code, AI adoption should focus on where frustration and bottlenecks are prevalent.

I wanted more time to write code _because code can take a long time to write_. Everyone wants results ASAP, but we're waiting for me to have enough information, no meetings, flow state, etc. and actually get it done - and I might get stuck on some peculiarity that I simply haven't dealt with before and wind up in google hell.

Instead, now, the code is writing itself, it's taking me way less time to turn around on changes, and I don't want "more time writing code" - now I want clearer decisions. I want more features in products that have become featureless due to the testing burden - well, AI can write test cases for you, so we should be able to start having featureful apps again. I want more time to actually deliver value to my end users; that's not something coding TIME did, it's something that new features, new integrations, and other simple improvements actually do.

Previously discussed: https://news.ycombinator.com/item?id=44429789