4 ms·
> And honestly, sometimes I don't know if code is too "clever" or the reader is just too "dumb". If you ever wonder this, then it's definitely a problem with y
by sfifs 10y ago
> And honestly, sometimes I don't know if code is too "clever" or the reader is just too "dumb".
If you ever wonder this, then it's definitely a problem with your code and not the reader. Code that cannot be easily read and understood by others is worthless in any commercial setting.
- douche 10y agoIf you're too numb or stubborn to learn the tools that your programming environment provides for writing higher quality code, I have little sympathy and would suggest that such a person fond another line of work. If, for instance, someone were writing C# and insisted on hand-rolling for loops in all cases[1], because LINQ is "too hard", that's them being lazy and unwilling to invest a tiny amount of effort in learning more effective methods. [1] There are some cases where it's more performant to use a plain foreach or bare for, but unless you're in tight loops or dealing with ginormous collections, it's a premature optimization.
- clebio 10y agoOr working in game development with low latencies to achieve high frames per second.