3 ms·

Every single rule or advice in programming is good until it isn't. OOP is good until it isn't, function programming is good until it isn't, premature optimizati

Every single rule or advice in programming is good until it isn't. OOP is good until it isn't, function programming is good until it isn't, premature optimization is the root of all evil until it is the root of all good. For some reasons humans have this deep need to try and boil things down to bulleted lists which in the domain of programming are just incredibly not useful.

James-primitive 7y ago
Bulleted lists -- exactly
TravHatesMe 7y ago
I think that you have a point but I often find myself citing guidelines or rules when I am evaluating code decisions or questioning code design. Maybe it depends on your interpretation of the phrases, some sayings should be followed religiously but others applied with discretion.
akoncius 7y ago
well said. for a while I started treating everything as a soft rule, more like guideline. it gets easier then :)
- Smoosh 7y ago
  Consider them to be heuristics, not rules.
bjornjajajaja 7y ago
This is because programming is an art. It has fundamental components (objects, functions, templates, iterators, etc) like in visual design (point, line, shape, value, etc). I think engineers should read the old and the new C++ books and master that language to know the evolution of all these paradigms and how to use them. There’s so much wisdom in the “Effective C++” series and Gang of Four and “C++ Templates: The complete guide“ to name a few. Problem is in this “start up culture” to bang things out and get them working the art is left behind. Just like many other arts.
- hermitdev 7y ago
  I was part of an uncredited team interviewed by Meyers for "Effective Modern C++". Always thought ir was somewhat ironic. At the firm (declined acknowledgments because they shun media attention) we werent even using a C++11 compiler on either Linux or Windows at the time. Yet, at least two of the patterns, I recognize as being at least a partial contributor to. Myself, I lost track of C++ standards changes with C++17, and Ive not been using C++ for the last several years. I still love the power and speed, but right now I'm dping more ETL work, and Python is a better and more productive language for that.

James-primitive 7y ago

Bulleted lists -- exactly

TravHatesMe 7y ago

I think that you have a point but I often find myself citing guidelines or rules when I am evaluating code decisions or questioning code design. Maybe it depends on your interpretation of the phrases, some sayings should be followed religiously but others applied with discretion.

akoncius 7y ago

well said. for a while I started treating everything as a soft rule, more like guideline. it gets easier then :)

Smoosh 7y ago
Consider them to be heuristics, not rules.

bjornjajajaja 7y ago

This is because programming is an art. It has fundamental components (objects, functions, templates, iterators, etc) like in visual design (point, line, shape, value, etc). I think engineers should read the old and the new C++ books and master that language to know the evolution of all these paradigms and how to use them. There’s so much wisdom in the “Effective C++” series and Gang of Four and “C++ Templates: The complete guide“ to name a few. Problem is in this “start up culture” to bang things out and get them working the art is left behind. Just like many other arts.

hermitdev 7y ago
I was part of an uncredited team interviewed by Meyers for "Effective Modern C++". Always thought ir was somewhat ironic. At the firm (declined acknowledgments because they shun media attention) we werent even using a C++11 compiler on either Linux or Windows at the time. Yet, at least two of the patterns, I recognize as being at least a partial contributor to. Myself, I lost track of C++ standards changes with C++17, and Ive not been using C++ for the last several years. I still love the power and speed, but right now I'm dping more ETL work, and Python is a better and more productive language for that.