News for hackers. Stuff that matters.
Re:Ask HN: What is your best advice for a developer to write... by collyw on Wednesday June 29, 2016 @11:28AM (#12002254)
"Weeks of programming can save hours of planning" is a favorite quote of mine.
Re:Ask HN: What is your best advice for a developer to write... by rhizome31 on Wednesday June 29, 2016 @02:36PM (#12003627)
While this is true, the opposite can also be true. That's called "Analysis Paralysis".
Re:Ask HN: What is your best advice for a developer to write... by Joeri on Wednesday June 29, 2016 @02:55PM (#12003780)
Most of the time analysis paralysis is a signal that you lack sufficient understanding of the needs to actually write the right code. There are two ways to break out of it: (1) understand the problem better, and (2) build something, anything, see why it wouldn't work, and then go back to the drawing board.
Re:Ask HN: What is your best advice for a developer to write... by epalmer on Wednesday June 29, 2016 @11:37AM (#12002329)
> "Weeks of programming can save hours of planning" is a favorite quote of mine.

I love this.

My two favorite generalizations are: - Slow down to speed up - Less is more

Re:Ask HN: What is your best advice for a developer to write... by shoo on Thursday June 30, 2016 @04:37AM (#12007298)
another variation of "slow down to speed up" is "slow is smooth / smooth is fast"