3 ms·
OTOH, its equally important to stress on this section of the post- "Not that we can do without abstraction. We need it to be able to write code at all" In the
by shaan7 8y ago
OTOH, its equally important to stress on this section of the post-
"Not that we can do without abstraction. We need it to be able to write code at all"
In the last 4-5 years I encountered a lot of such "hate" against abstraction and without knowing I _STOPPED_ writing abstractions. None at all. I feared writing abstractions because people advertised them as evil.
The years have gone by, but the codebase needs to be maintained. There are often days when I have to spend shitload of time doing something simple just because I never created abstractions where I should have.
So yeah, my fellow programmers, please do not scare off young programmers from using abstractions. They might write the wrong abstractions sometimes, but hey, how else do you learn if not from mistakes?
- Aeolun 8y agoWe had a ton of endpoints without any form of abstractions. Need to do something on all endpoints? Have fun copy/pasting into 80 source files.
- galangalalgol 8y agoWe don't need it to write code, and maybe not even to be efficient at it. Carmack wrote an article about the time he worked with Saabs aerospace people. They write flight controls track databases sensor contol targeting etc. with no calls or backward branches except the end of the main loop. So every matrix multiply is duplicated in place. That is very complicated code. Carmack was inspired by that and used a less strict form of that ruleset for his next project. He allowed for functions as long as they were pure but nothing else.