Re:Our Development Workflow
by mtdewcmu on Friday November 07, 2014 @10:12AM
(#8572824)
>> 1. "Don’t optimize for the short-term" vs "Keep it simple and straightforward".
>> Often the simplest thing may not work in the long run. But its better to err on the side of keeping things simple.
IMO, the best reason for simplicity is that simple things can be torn out and replaced more easily than complex things. So the simplest thing isn't necessarily right, but you haven't wasted much resources by choosing it, so you've left your options open. You always want to have options.
Re:Our Development Workflow
by jiraaya on Monday November 10, 2014 @01:40AM
(#8582296)
Ah, that's what I meant by "erring on the side of keeping things simple". It is okay if you make decisions that are not optimal in the long run, but are simple since they can be torn apart.
>> Often the simplest thing may not work in the long run. But its better to err on the side of keeping things simple.
IMO, the best reason for simplicity is that simple things can be torn out and replaced more easily than complex things. So the simplest thing isn't necessarily right, but you haven't wasted much resources by choosing it, so you've left your options open. You always want to have options.