Sure, but my point is that being forced to be more methodical isn't a good thing. Not needing to be methodical is better (because your tools will catch your mistakes for you).
This sounds depressing.
Definitely true on the web side of things. Bootstrap+React+Angular+jQuery+whatever else, minify, deploy on docker, done.
I'm not all in on what I call "Poirot's doctrines," but there is almost always room for method. I grant that some methods aren't needed and speed is always of high value.
However, speed of bouncing from beep to beep in your tools are not always faster than stepping back and thinking.
As an example, no amount of fast feedback will help you complete all of the Euler problems.
I find this one almost a perfect counterexample. The Euler problems are almost ideally suited to high levels of interactivity, in order to tease out patterns and solutions.
By no means am I a massive Euler user, but when I was solving #555 I was sure glad to be using Python. If I had a >1m recompile time I probably would have just given up.
Also... I don't see how any single Euler problem could have minute plus compiles. No matter the language. :(
I also wasn't saying that any language would get long compile times on Euler questions -- they're far too short for that -- but that theoretically if they did it would cause problems.
It is worth noting that many of those problems originate from people that did them by hand. :)