Just how do most software developers work?

Frägt sich auch Albert D. Kallal (der, bei dem Microsoft Access nicht sucks):

Have you ever been stuck on a design for a few days? You will notice that those several days seem very frustrating and very unproductive. However once your mind "SEES" the design that is going to work...then you are able to produce code like a hungry snow blower working on a snow bank in January.

Kann ich absolut nachfühlen. Was soll ich programmieren, wenn ich "keinen Plan" habe? Wie soll ich anfangen, wenn ich nicht ein bestimmtes Bild vor Augen habe? (Wobei ich mich immer frage, wo die Grenze zur berüchtigten "Analysis Paralysis" liegt.)

That idea of "seeing" the design or having a mental picture of the design is required before one can really zone in. Without this mental conceptual view then no real high rate of development will occur. In fact, for some no development will occur until the mind "sees" the picture. My point here is that when you slow down the rate of development, then the mind has more time to get that "view". Once the mind has that view then writing code is like finally starting up the snow blower (or, for you southern people...the lawn mower).

"See the picture"! Nett! Und dafür muss man manchmal langsamer machen. Genau.

Slowing down the rate of development gives the mind more time to "think design".

Ja, ein weiteres Paradox also: Langsamer machen, um schneller zu sein!