3 ms·
Heh, I prefer to refer to that whole comment as Bane's Rule. I have had many interesting discussions with IT managers face to face after having them read that,
by nekopa 10y ago
Heh, I prefer to refer to that whole comment as Bane's Rule. I have had many interesting discussions with IT managers face to face after having them read that, especially regarding the idea of having vendors show that their product beats out the current system.
For programmers, I think one of the key takeaways from that comment is not the clever coding, but the direct tie into business results from the coding. Not just immediate business results, but also how the system was set up for growth and improvement easily too.
- qwertyuiop924 10y agoIt's about some of core principles of software: Keep it simple, use the minimal code (if it's not there, it can't slow you down), see where speed problems are before optimizing, optimize before scaling up. It's common sense, but it's rare to actually follow it. Actually, I'm guilty of this myself. I was finishing last year's Advent of Code, and was given a problem which I tried to optimize, as I assumed the naive approach would be too slow. Then I realized I was trying to optimize Travelling Salesman, so I bit the bullet and went for the O(n!) solution. And it ran in less than a second. In interpreted scheme, no less. I felt kind of silly later.