24 ms·

> Hidden complexity you don't control is the most expensive kind I think. That's called encapsulation. :) Seriously, encapsulating complexity is the foundatio

> Hidden complexity you don't control is the most expensive kind I think. That's called encapsulation. :) Seriously, encapsulating complexity is the foundation of most programming paradigms.

franklyt 6y ago
Actually, it's called abstraction, as a technical point.
- jamiesonbecker 6y ago
  Good point. This is what I was referring to: https://en.wikipedia.org/wiki/Encapsulation_(computer_programming) https://en.wikipedia.org/wiki/Encapsulation_(computer_progra...
userbinator 6y ago
In the real world, it turns out that code you didn't write can also have bugs or not behave as you expect it to, so the less of that there is, the better. Encapsulation/abstraction should really be a tool of last resort. From experience, it doesn't actually help reduce complexity if overused, but just makes it hidden and more likely to surprise you when you're debugging.
- jamiesonbecker 6y ago
  > In the real world... From experience... Does jQuery (est. 2006) have more bugs in it than your code?
- scubbo 6y ago
  Have fun implementing everything from scratch in assembly.
- quattrofan 6y ago
  As has been seen many times recently third party libraries are a major attack vector for the bad guys.
- nicoburns 6y ago
  > In the real world, it turns out that code you didn't write can also have bugs or not behave as you expect it to, so the less of that there is, the better. jQuery's not a very good example of this though. It's one of the most widely used, and hence most tested and least buggy pieces of software out there. Nowadays the web APIs are pretty solid, but back in the IE6/7/8 days the jQuery API was a lot less buggy than using the built in APIs directly.
- donapieppo 6y ago
  > In the real world, it turns out that code you didn't write can also have bugs or not behave as you expect it to To me this seems a comment that only stands for one-developer projects.

> Hidden complexity you don't control is the most expensive kind I think. That's called encapsulation. :) Seriously, encapsulating complexity is the foundation of most programming paradigms.

franklyt 6y ago

Actually, it's called abstraction, as a technical point.

jamiesonbecker 6y ago
Good point. This is what I was referring to: https://en.wikipedia.org/wiki/Encapsulation_(computer_programming) https://en.wikipedia.org/wiki/Encapsulation_(computer_progra...

userbinator 6y ago

In the real world, it turns out that code you didn't write can also have bugs or not behave as you expect it to, so the less of that there is, the better. Encapsulation/abstraction should really be a tool of last resort. From experience, it doesn't actually help reduce complexity if overused, but just makes it hidden and more likely to surprise you when you're debugging.

jamiesonbecker 6y ago
> In the real world... From experience... Does jQuery (est. 2006) have more bugs in it than your code?
scubbo 6y ago
Have fun implementing everything from scratch in assembly.
quattrofan 6y ago
As has been seen many times recently third party libraries are a major attack vector for the bad guys.
nicoburns 6y ago
> In the real world, it turns out that code you didn't write can also have bugs or not behave as you expect it to, so the less of that there is, the better. jQuery's not a very good example of this though. It's one of the most widely used, and hence most tested and least buggy pieces of software out there. Nowadays the web APIs are pretty solid, but back in the IE6/7/8 days the jQuery API was a lot less buggy than using the built in APIs directly.
donapieppo 6y ago
> In the real world, it turns out that code you didn't write can also have bugs or not behave as you expect it to To me this seems a comment that only stands for one-developer projects.