@mookie it's missing at least one rule :

-1 : beware off by one errors

@mookie

Some pertinent points in relation to this at the corporate where I am employed and why I don't want to do it anymore:

5. The problem is that you have poor hiring decisions and their inexperience shows in the "freshly minted graduates" writing garbage

10. These are used to reprimand developers and/or gaslight them

12. Asking for help unleashes a lecture "why are you doing it that way, instead of our way? Where's your documentation, what are you doing during the day here?" and then puts you in a pair-programming setup.

15. Say that to my manager, see how fast you'll get written up or put on a PIP

@mookie

Ich bin der Geist, der stets verneint.

0. You will regret that simplistic design when the real world calls.
1. Nobody takes pride in what they write.
2. Everything is "good enough", there is nothing excellent.
3. Nothing gets made to fit, everything has to come from some "proven framework".
4. The wiki is filled with half-assed bullet points except the bullets are Markdown headings of various sizes.
5. Nothing ever gets fixed properly, only wrapped and worked around.
...

@mookie Microsoft and Redhat disobey this on a monstrous scale.

To be better than them at coding is in this way is to be above water.

Another words, -1 or worse for their methods. 0+ for anything better.

Those two corporations are heinous when it comes to complexity and obscurity.
"Systemd" after all...

dbus too, etc...

And in microsoft's case particularly, "Windows"

Windows btw, is a good name for it, except they don't mention why.

Your OS can be seen from afar by them.

"Windows"

:P