(Sarcasm alert.)
There is a nice self-regulation principle at work here: If you make software with a lot of bugs, you also spend time fixing those bugs. This hampers your ability to make more crap software. If you on the other hand produce quality software, much less time is spent at maintenance so you become more productive overall.
I think it is a fallacy to expect bugs to creep into your code. Eradicate them before writing the code lines. But what makes this hard for most people is that you don't think you need that amount of quality in your software.
Your sarcasm is misplaced and presumes bad code always comes before good code, it doesn't.
You should always make it easy for yourself to fix mistakes, even if you shouldn't have made them in the first place.
>...
>The effect is: you're forced to write shorter methods. And that's a Good Thing.
I find the opposite is true - I need to see more lines to appreciate exactly how goddamn awful that 200 line function is. And when I go to refactor it I need to be able to see as much as possible of it on the screen to start extracting bits out and make it shorter without losing context.