3 ms·
I _generally_ agree with the above, aside from: > code reviews catching hard to understand code ... always allowing time to update dependencies and compiler ve
by bobnamob 2y ago
I _generally_ agree with the above, aside from:
> code reviews catching hard to understand code ... always allowing time to update dependencies and compiler versions
In my experience these two practices are always the first to get dropped or de-prioritised when "business needs" come knocking.
Unfortunately, I've never seen a C++ project that's managed to keep the template wizards and language lawyers away for more than a couple of years (specifically, once the original authors are gone, all bets are off). Could just be my limited and now out of date exposure, I've been out of the C++ game (happily) for a good few years now
- jahnu 2y agoYou are not wrong on average. Last four years I'm lucky enough to just work with one friend and we are following best practices that would put many a big corp to shame. Prior to that I worked at a smallish company with 80 devs or so, 5 or 6 doing c++ and we also did a good job and management let us and encouraged us to do the right things. Before that... yep... like you my experience was enforced shortcuts all over the place from a management who didn't have technical understanding and didn't let the professionals they hired make professional decisions which caused much more pain down the road. Almost like a debt you have to repay with interest... but technical!