Abstraction is necessary for managing complexity, but if you haven’t been rechecking the fit of your abstraction to your growing set of instances, then wouldn’t you want to at least consider the possibility that you’ve lost sight of the thing you were trying to manage?
Programmers have plenty of bad collective mental habits, but it's pretty hard to do the job and not learn this lesson quickly and forcefully.
-
-
What are some examples? I agree there are many individual bad habits. But I can’t think of many collective ones.
-
A few that come to mind quickly: confusing different notions of priority (in what sense is category theory more fundamental than algorithm design?); taking rules too literally (related: confusing precision and rigor); being too eager to burn things down and start over.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.