How not to be a better programmer
Over at r/programming is this post on "How to be a better programmer". It's mostly garbage.Don't repeat yourself (reuse code)
Trying to reuse code is near the top of reasons why big projects fail. The problem is that while the needs of multiple users of a module may sound similar, they are often different in profound ways that cannot be reconciled. Trying to make the same bit of code serve divergent needs is often more complex and buggy than multiple modules written from the ground up for each specific need.
Yes, we adhere to code cleanliness principles (modularity, cohesion) that makes reuse easier. Yes, we should reuse code when the needs match close enough. But that doesn't mean we should bend over backwards trying to shove a square peg through a round hole, and the principle that all pegs/holes are the same.
Give variables/methods clear names
Programmers hate to read other code because the variable names are unclear. Hence the advice to use "clear names" that aren't confusing.
But of course, programmers already think they are being clear. No programmer thinks to themselves "I'm going to be deliberately obtuse here so that other programmers won't understand". Therefore, Continue reading





No overlays, no MPLS: Aryaka took a DIY approach to SD-WAN.