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*

4
  • 26
    +1 for "it's faster to write things two times that write anything perfect the first time" Commented Oct 8, 2013 at 17:23
  • 2
    +1 for sharing a personal story, which I expect will be recognizable and useful for the questioner. Commented Oct 8, 2013 at 18:43
  • 2
    I agree, you may be experiencing coders block (like writer's block). You can't manage the complexity, so you dally. The cure is the same as for writer's block; write something. Soon as you have something on the screen, it will give you ideas how to proceed. You have probably been given this advice in a less lucid form, as, "Don't worry about efficiency/errors/whatever, just get something done quickly." Well, that's half the answer. The other half is that once you get past the empty screen, doing the actual error handling, efficient algo or whatever is straightforward. Commented Mar 29, 2014 at 18:19
  • @SeattleCPlusPlus: I agree it's straightforward for simple problems, probably for most algorithmic code. It's no so simple when you want to get some good classes structures. Refactoring rules are not totally useless. Commented Mar 31, 2014 at 8:00