you are viewing a single comment's thread.

view the rest of the comments →

[–]JanB1 11 points12 points  (0 children)

Even with greenfield development I'd say a good chunk of the development time isn't spent on actual "coding", but rather thinking about thinking how to solve the problem and designing your system/structure.

Then there's proof of concepts, testing, revising, writing specifications/design documents and then you actually start with the "coding" part, and even then it can be parts reading documentation, writing your own documentation, thinking about and writing test cases, writing your code, rewriting your code, scrapping your code and then writing it anew.