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*

2
  • I'll suggest reading code complete in addition to pragmatic programmer too. You should also learn the subtleties of the language. Commented Oct 11, 2011 at 19:07
  • Don't do error checking. That way you complete 90% of the project in 10% of the time and call it 100% complete. IOW, you don't waste that other 90% of the time to finish the last 10%. Seriously, all your examples and most of the answers are about the writing code part, which in the big scheme of things takes next to nothing compared to deciding what code should be written and all the testing. Your accepted solution is by far the only one that will save significant time and mainly just the part of creating simpler solutions. Commented Oct 14, 2011 at 15:43