21–30 of 177 posts
"premature optimisation is the root of all evil" is a saying that came from 1974 when computers were slower, languages were less effective and development processes immature. Today you should make your software fast.
It seems like this should work the other way too? If you want to break a habit, add a delay. This seems like a good idea for a browser extension. Maybe sometimes you want to undo the work that the website did making things go faster?
Obviously this only works over some kind of messaging service; face-to-face conversations have significantly different expectations around long pauses.
That's why the thing about "premature optimisation is the root of all evil" is mistaken and wrong in these modern times and yet many people still quote it and take it to heart and as a result don't prioritise speed when building software. "premature optimisation is the root of all evil" is a saying that came from 1974 when computers were slower, languages were less effective and development processes immature. Today…
That's why the thing about "premature optimisation is the root of all evil" is mistaken and wrong in these modern times and yet many people still quote it and take it to heart and as a result don't prioritise speed when building software. "premature optimisation is the root of all evil" is a saying that came from 1974 when computers were slower, languages were less effective and development processes immature. Today…
Wouldn't modern times make it more relevant ? I would choose "don't worry about speed, make it happen first".
At this mode, my mind uses all available time slots to make the best of them. For example, by the time my program compiles, my brain visualizes possible breakage scenarios and possible solutions, in case the compilation fails.
I could be on confirmation bias here, but this seems to be a neat trick to get more things done.
I really disagree with this. Aiming for something you actually think is unhealthy means you either think you should be working unhealthily ( :( ) or you don't trust your measure of healthy (in which case recalibrate that).
Work fast, don't think things through, make mistakes, pay for your haste by spending more time fixing your mistakes than you would have had you thought things through.
It seems like this should work the other way too? If you want to break a habit, add a delay. This seems like a good idea for a browser extension. Maybe sometimes you want to undo the work that the website did making things go faster?
When I do dev stuff with a slight sense of urgency, the probability of my mind wandering somewhere else goes down drastically. At this mode, my mind uses all available time slots to make the best of them. For example, by the time my program compiles, my brain visualizes possible breakage scenarios and possible solutions, in case the compilation fails. I could be on confirmation bias here, but this seems to be a neat…