4 ms·
I think she's trying to imply that we should not jump into coding without putting in some thought on all possible scenarios. Obviously there is no way that anyo
by ashwinaj 10y ago
I think she's trying to imply that we should not jump into coding without putting in some thought on all possible scenarios. Obviously there is no way that anyone can tabulate all possible scenarios, but the time spent on dwelling on possibilities helps to avoid initial flurry of bugs after a feature is deployed.
- dave2000 10y agoYeah, and it sounds exactly like something a non-technical manager might say to "help" their workers.
- ashwinaj 10y agoWell you can choose to ignore what a non-technical manager says (if you don't care for him/her). I don't know what your programming experience is, but if you've done some moderately complex projects this might sound obvious but is overlooked by a lot of people. Source: Personal experience which lead to a lot of sleepless nights
- FroshKiller 10y agoIt's like they say: Good programmers look both ways before crossing a one-way street.
- mfukar 10y agoYeah, but it's easier to think tweet-sized thoughts.
- hvmonk 10y agoSo, does that demean it? A thought is just a seed, and the onus of growing/nurturing it is on the thinker.