3 ms·
> you have so many high-level considerations that also thinking about the low-level implications would simply be too much You still have to have a high-level p
by bad_user 18y ago
> you have so many high-level considerations that also thinking about the low-level implications would simply be too much
You still have to have a high-level perspective on how things are working, because abstractions are often leaky.
For example, I don't care much about tasks related to systems administration, allowing me to concentrate on what matters to me ... for instance I don't care about the difference between Postfix and Sendmail, or the difference between Apache and Lighttpd ... I just use the one I know until I have a problem with it, but when I do have a problem I have to find ways to solve it. And some knowledge on how the protocols and processes work really help.
- derefr 18y agoYou don't (usually) think about your oil when you're driving, and you especially don't change your oil while driving. Just because you understand how the low level works doesn't mean you keep it loaded in your working memory simultaneously to the high-level knowledge. You change your oil when the car is parked; you optimize when you're not in the middle of writing a feature or fixing a bug.