News for hackers. Stuff that matters.
Re:Code reviews aren’t just for catching bugs by gpderetta on Thursday May 12, 2016 @03:38PM (#11686121)
In my experience, no design document, no matter how carefully drafted survives contact with the enemy^W^W an IDE. At best you can define interface boundaries between independently developed modules.

Edit: broken leftover line

Re:Code reviews aren’t just for catching bugs by fishnchips on Thursday May 12, 2016 @04:02PM (#11686315)
Things change a lot during the project, I agree. But assuming everything will change and using that as an excuse not to plan at all sounds like a poor choice to me.

"In preparing for battle I have always found that plans are useless, but planning is indispensable." - Dwight D. Eisenhower

Re:Code reviews aren’t just for catching bugs by gpderetta on Thursday May 12, 2016 @04:37PM (#11686588)
I do actually agree that some amount of planning, and especially putting down a sketch on paper do help, in particular as a way to nail down requirements and figuring out obvious roadstops, but it is important to be under no illusion that the final project will resemble in any way the plan
Re:Code reviews aren’t just for catching bugs by lmm on Friday May 13, 2016 @07:52AM (#11689834)
> But assuming everything will change and using that as an excuse not to plan at all sounds like a poor choice to me.

I know that's how it sounds. But in my experience it turns out to be a lot more effective than planning.