Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 4
    If you use that method to solve small to medium tasks, then, as others told you in their answwers, I'd say there is nothing wrong with it, preferrably with some unit tests as additional quality measure. If you intend to create the architecture of some big solution this way I'd recommend to rethink the approach. Commented Apr 28, 2013 at 20:15
  • 1
    I suggest you read Code Complete 2 (or at least the relevant parts), which talks a lot about the non-programming aspects of programming. You may try to plan more before you start coding so you have an idea of what your goals are, what the restrictions on the inputs are, etc. One strategy mentioned is to write pseudo-code before writing the actual code. You'll be able to see the same problems you see with real code, but will be able to get to that point much quicker. Commented Apr 28, 2013 at 22:41
  • Another suggest is Clean Code. The book maybe doesn't have the exact answer to your question, but there are some principles that you can use after make your code work. amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/… Commented Apr 29, 2013 at 10:37
  • 1
    "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- Antoine de Saint-Exupery Commented Apr 29, 2013 at 18:12
  • possible duplicate of When to refactor and of Prototyping vs. Clean Code at the early stages Commented Apr 30, 2013 at 22:38