3 ms·
IME you're gonna screw it up the first time anyway, and the simplest option is usually the easiest to patch once you figure out what you actually need.
by daxfohl 4y ago
IME you're gonna screw it up the first time anyway, and the simplest option is usually the easiest to patch once you figure out what you actually need.
- morkalork 4y agoThis is mine too and I feel like people's personal biases make them think otherwise. 9 times out of 10, the extra effort and concern put into making a new thing more scalable or generic wasn't needed, that time and effort could have been better spent doing other things. Also, skipping the work and going for the simpler option wouldn't have blown timelines nearly as much. Problem is, you don't feel that wasted time very harshly, but for that 1 in 10 you have to go back, throw out code and re-do it, the pain is very sharp and acute so everyone takes the more burdensome path and pats themselves on the back for being a good architect.
- doctor_eval 4y agoThis is true and I agree, but not every project is the first time. When you already know the territory, the question often becomes “now or later”? The correct answer is most often “later”… but the trick is being able to work out what you need today.