3 ms·
Indeed software engineering pretty much consists of abstractions. (And computer science is basically the science of formalized abstraction, that's basically wha
by jrochkind1 8y ago
Indeed software engineering pretty much consists of abstractions. (And computer science is basically the science of formalized abstraction, that's basically what CS is).
If we didn't have any abstractions at all.. we'd all be writing machine code in 1s and 0s. (and even that is an abstraction, of course...) That wouldn't get us very far.
People, including in this thread, also often talk about a particular abstraction being "a leaky abstraction". Implying some abstractions are, some aren't. Whereas in fact the 'law' quoted says that all "non-trivial abstractions, to some degree, are leaky." They're all leaky, the map is never the territory. But it's the business we're in. (But some abstractions are more useful, more successful, and/or more dangerous than others... in a given context of usage, always in a given context).
- alexandercrohde 8y agoI agree all engineering is abstractions. Every function, data-structure, program. >> [People] talk about a particular abstraction being "a leaky abstraction". Implying some abstractions are, some aren't. There are degrees of leakiness though, which matter a great deal. The concept of a "file" is an abstraction, instead we could all write direct to disk sectors. But its value outweighs the leak associated with it. Other abstractions aren't always so useful, sometimes a coworker makes a class that's riddled with exceptions and caveats.
- jrochkind1 8y agoSome abstractions are definitely more useful/successful/robust than others. (I think I want to say usually for a particular context, not as a universal/existential thing. Sometimes that context grows to be everyone's... we all use a 'file' abstraction because it was so useful the entire field adopted it, and stopped considering alternative abstractions, and everyone takes as a starting assumption to work within the context where 'file' is useful (except in extreme edge cases maybe) -- for better or worse.) Deciding which is which, whether a particular abstraction's value outweighs the "leak" in particular contexts or in "general" -- well, that's what endless internet debate is made of. It's usually not clear as a consensus until quite some time has passed (and even then heretics can challenge it). I agree it's the right question, but it can't be answered simply by saying "leaky abstraction".