Design by coding, its wrong but easier to visualize -

i'm sure others agree, when code hits pavement easier think of elements go application. meaning, once going, think of what's next because have reached point have design table or class.

the drawbacks of approach obvious , don't need go it.

the question is, of can't conceptualize design without "seeing it", how go design @ seat of our pants more structured methodology?

the solution can think of detailed specifications, forces 1 think of how things going work.

is case of how people think differently, or there else ignoring?

well, don't know if quite asking, reading question reminded me of tdd (test driven development).

the goal of tdd produce clean, testable code along suite of automated regression tests.

it amazing me how clean code can end when go @ tdd... think problems, write tests it, implement make tests pass, refactor ensure code clean , readable.

i don't think need lot of front design tdd, may help... i'm kind of on "design coding", @ same time can maybe catch major flaws ahead of time if think in bigger picture, if minimally.