Changes in 37f8a98: Updated rules.md

				rules.md
			
          @@ -1,29 +1,32 @@

          -<!-- TITLE: The 9 angry commandments -->

          -<!-- SUBTITLE: Production is war and war is hell -->

          +<!-- TITLE: 10 sysadmin commandments -->

          +<!-- SUBTITLE: Because production is war. And war is hell -->

          -# 1 Love thy defaults.

          +# 1 Thou shalt love thy defaults.

           Rainbows and emoji ZSH prompt? On servers? Fuck no. Your Ansible pull request has been *terminated*.

           Do less to ~~do more~~ stop dicking about.

           # 2 Thou shalt use the infrastructure.

           We both know you couldn't implement Paxos if your miserable life depended on it.

          -Stop writing ridiculous code you won't understand in a week's time and put that shit in zookeeper, or a database, or DNS or whatever.

          +Stop writing ridiculous code you won't understand in a week's time and put that shit in zookeeper, or a database, or DNS, or whatever.

           # 3 Thou shalt use the OS.

           If it'll fit in one line of grep | sed | awk, then do that. If you need more power, break out split and xargs -P. Use flock. Use cron. Use logrotate.

          -Ditch your nonsense multi-threaded Ruby abomination and[Taco Bell](http://widgetsandshit.com/teddziuba/2010/10/taco-bell-programming.html) that shit immediately.

          +Your slow, fragile, multi-threaded Ruby abomination are an affront to decency. [Taco Bell](http://widgetsandshit.com/teddziuba/2010/10/taco-bell-programming.html) that shit.

           # 4 Thou shalt always check last mod times.

           Are you sure that's the right file?

           Fuck me, are you even on the right host?

           # 5 Thou shalt not blame DNS.

           Despite what the Interwebs told you, it's not DNS.

          -Use dig. nslookup is for very small children and Senior NodeJS Developers. Yes, this wiki is a Node app. Yes, we are all *unclean*.

          +Stop using nslookup immediately. Use getent. Use dig.

           # 6 Thou shalt respect the sanctity of stdout.

          -If your app has nothing to say, it should shut the fuck up.

          -Logs do not belong on stdout. Ever.

          +If your app has nothing to say, it should shut the fuck up. Logs do not belong on stdout. Ever.

          +The Unix way is the righteous way.

           # 7 Thou shalt automate everything.

           Are you being paid by the keystroke or something?

           This isn't a union gig. Get that mind-numbing carpal-tunnel-inflaming shiteshow into Ansible. Now.

           # 8 Thou shalt only use UTC.

           Those VMs could be on the fucking moon for all I know.

           Don't make me convert your guess-the-timezone-not-quite-ISO timestamps during a outage. Not again.

          -# 9 Those who email screenshots of PuTTY sessions shall be destroyed.

          +# 9 Thou shalt cover thine ass

          +Record everything. Confirm decisions by email. Keep timelines during outages.

          +Paper trails are your saviour.

          +# 10 Those who email screenshots of PuTTY sessions shall be destroyed.

           What the *actual fuck* is wrong with you?

          \ No newline at end of file

...	...	@@ -1,29 +1,32 @@
1		-<!-- TITLE: The 9 angry commandments -->
2		-<!-- SUBTITLE: Production is war and war is hell -->
	1	+<!-- TITLE: 10 sysadmin commandments -->
	2	+<!-- SUBTITLE: Because production is war. And war is hell -->
3	3
4		-# 1 Love thy defaults.
	4	+# 1 Thou shalt love thy defaults.
5	5	Rainbows and emoji ZSH prompt? On servers? Fuck no. Your Ansible pull request has been terminated.
6	6	Do less to ~~do more~~ stop dicking about.
7	7	# 2 Thou shalt use the infrastructure.
8	8	We both know you couldn't implement Paxos if your miserable life depended on it.
9		-Stop writing ridiculous code you won't understand in a week's time and put that shit in zookeeper, or a database, or DNS or whatever.
	9	+Stop writing ridiculous code you won't understand in a week's time and put that shit in zookeeper, or a database, or DNS, or whatever.
10	10	# 3 Thou shalt use the OS.
11	11	If it'll fit in one line of grep \| sed \| awk, then do that. If you need more power, break out split and xargs -P. Use flock. Use cron. Use logrotate.
12		-Ditch your nonsense multi-threaded Ruby abomination and[Taco Bell](http://widgetsandshit.com/teddziuba/2010/10/taco-bell-programming.html) that shit immediately.
	12	+Your slow, fragile, multi-threaded Ruby abomination are an affront to decency. [Taco Bell](http://widgetsandshit.com/teddziuba/2010/10/taco-bell-programming.html) that shit.
13	13	# 4 Thou shalt always check last mod times.
14	14	Are you sure that's the right file?
15	15	Fuck me, are you even on the right host?
16	16	# 5 Thou shalt not blame DNS.
17	17	Despite what the Interwebs told you, it's not DNS.
18		-Use dig. nslookup is for very small children and Senior NodeJS Developers. Yes, this wiki is a Node app. Yes, we are all unclean.
	18	+Stop using nslookup immediately. Use getent. Use dig.
19	19	# 6 Thou shalt respect the sanctity of stdout.
20		-If your app has nothing to say, it should shut the fuck up.
21		-Logs do not belong on stdout. Ever.
	20	+If your app has nothing to say, it should shut the fuck up. Logs do not belong on stdout. Ever.
	21	+The Unix way is the righteous way.
22	22	# 7 Thou shalt automate everything.
23	23	Are you being paid by the keystroke or something?
24	24	This isn't a union gig. Get that mind-numbing carpal-tunnel-inflaming shiteshow into Ansible. Now.
25	25	# 8 Thou shalt only use UTC.
26	26	Those VMs could be on the fucking moon for all I know.
27	27	Don't make me convert your guess-the-timezone-not-quite-ISO timestamps during a outage. Not again.
28		-# 9 Those who email screenshots of PuTTY sessions shall be destroyed.
	28	+# 9 Thou shalt cover thine ass
	29	+Record everything. Confirm decisions by email. Keep timelines during outages.
	30	+Paper trails are your saviour.
	31	+# 10 Those who email screenshots of PuTTY sessions shall be destroyed.
29	32	What the actual fuck is wrong with you?
...	...	\ No newline at end of file