4 ms·
> I (16+ years developer) prefer to iteratively go between coding and designing I have an extra ten years on you and couldn't agree more. There are two jokes:
by dkarl 2y ago
> I (16+ years developer) prefer to iteratively go between coding and designing
I have an extra ten years on you and couldn't agree more.
There are two jokes:
- A few months of programming can save weeks of design.
- A few months of design can save weeks of programming.
Inexperience is thinking that only one of these jokes is grounded in truth.
Recognizing which kind of situation you're in is an imperfect art, and incremental work that interleaves design with implementation is a hedge against being wrong.
- spartanatreyu 2y agoI like to say: - One hour of planning saves ten hours or programming... - and one hour of research saves ten hours of planning. You can also invert it: - Ten hours of programming saves one hour of planning... - and ten hours of planning saves one hour of research.
- baud147258 2y ago> - Ten hours of programming saves one hour of planning... If the planning is done with 5 or more people in a meeting, there still might be some time savings...
- jfengel 2y agoThe difference between DRY and YAGNI is experience. Both are predicting the future, and you can only do that by having watched code evolve.
- bena 2y agoWhat's that saying? "Once is a mistake, twice is a coincidence, three times is a pattern". Having to write something once, just write it. Having to write something twice with small differences, think about it. Having to write something three times? Consider refactoring.