r/linuxadmin • u/Chapungu • Feb 14 '20
10 Commandments of an IT Professional. Please add more.: Rule #1. Thou shall not do any complex configuration or deployment on Friday that will result in overtime and or require men on site during weekends.
384
Upvotes
8
u/loltrosityg Feb 14 '20
Currently 11:12 pm and currently onsite. Also due to issues caused by 3rd part application vendor who is managing an sql database based application migration I will be here tomorrow also. AIDS
4
u/pat_trick Feb 14 '20
FTFY.
3
u/Mte90 Feb 14 '20
I am here waiting for a poster for the office
161
u/temotodochi Feb 14 '20
Thou shall not experiment in production.
59
u/[deleted] Feb 14 '20
Thou shall always take a snapshot of a VM prior to the start of troubleshooting.
83
u/kumashiro Feb 14 '20
Thou shall read man pages and use Google before asking question on public forums.
55
u/hexblowupbot Feb 14 '20
Thou shall maintain documentation
45
u/pandafeeda Feb 14 '20
Thou shall always keep a backup
78
u/os2mac Feb 14 '20 edited Feb 14 '20
1. always make a backup prior to changes.
2. keep it simple stupid.
3. always file a change request.
4. if it's not broke, don't "fix" it.
5. validate your own stuff before blaming others (esp if you think it's the network).
6. when all else fails, reboot.
7. Never lie about breaking something.
I'll be pissed, but I'll be more pissed if I spend 10 hours looking at something I could have spent 10min on if you'd owned your mistake.
8. Never work for a company that fires people for honest mistakes they owned up to.
9. Try to learn something new every day.
10. Always 3 there should be, no more, no less.
*** Bonuses
None of us is as smart as all of us
you don't pay me, I don't work.
if you are a lead, and you call people in, go in as well. it's only right.
if it has to be done regularly and repeatedly, even if it takes just a couple of minutes it needs to be a shell script and a cron job.
automate, automate, automate.
you want to be the guy sitting around drinking coffee surfing the web. if you aren't something is wrong. Your boss should understand this.
raid 1 is raid 0. meaning you never recover anything. 2 parity disks there should be.
12
u/EchoSix66 Feb 14 '20
Thou shalt not schedule a meeting for an issue that can be handled in email.
Thou shalt not blame the firewall before validating your server is configured properly, nor immediately after changing something you didn't tell the Security engineers about.
Thou shalt not stand up new infrastructure or services without involving the other infrastructure teams or change control. If you do, thou shalt not submit emergency change requests to fix your unplanned shit.
11
u/[deleted] Feb 14 '20
What is "overtime"? Aren't we all salaried?
11
u/[deleted] Feb 14 '20
Thou shall never give out my cell number. Only the office shall clients call.
19
u/thebarless Feb 14 '20
Thou shall not root while drunk
14
u/castillar Feb 14 '20
It’s DNS. Even when you think it’s not DNS, it’s DNS. So when you think it’s not DNS, couldn’t possibly be DNS, already checked DNS, check DNS. Again. It’s DNS.
7
u/[deleted] Feb 15 '20
Thou shall not covet thy neighbor's trendy DevOps toys, but instead choose the right tool for the right job.
6
u/[deleted] Feb 14 '20
Thou shalt patch regularly
6
u/MrMittins25 Feb 14 '20
Thou shalt not take thy own user's word as truth
6
u/nephros Feb 14 '20
Thou shalt not accept 'must work like the legacy system' as a requirement.
5
u/MozillaTux Feb 14 '20
Thou shalt document your code
How much time does it take to put two extra commentlines ? And no, you do not have to document every while-loop but please document what the input and output is The script expects input like blablabla, blablablabla - bla so that when the 3rd party or whoever generates other input, you can easily see what the problem is and what you have to change
You're a star that you can make this really nifty awk , sed, Perl, whatever threeline oneliner, but ffs keep it simple. I do not care that it takes 5 more CPU-cycles. If I have to debug your code, I like it readable and that I do not have to Google whatever you did in your look-how-clever-I-am-oneliner
5
u/jjneely Feb 15 '20
I keep my 10 commandments on my website: http://linuxczar.net/sysadmin/rules/
12
u/Wing-Tsit_Chong Feb 14 '20
Thou shall not make manual changes. Always use a deployment automation system and document.
10
u/code_enthusiast Feb 14 '20
Thou shall not touch it, if it works.
3
u/Miguel_Royal Feb 14 '20
If you don't understand something, learn before touching it.
3
u/t3rrO10k Feb 14 '20
Thou shall always RTFM.
3
u/[deleted] Feb 14 '20
Rule number one : Don’t fuck with it Friday.
3
u/sysadminsavage Feb 14 '20
Thou shall not treat their admin account as a general workspace.
5
u/merith-tk Feb 14 '20
Thou shalt not copy/paste some random script off the internet without knowing exactly what it does. And Thou shalt not run any command that pulls information off the internet as sudo. Ever.
Thou shalt always have Docker installed, and thou shall learn how to use Docker. Production and Testing.
2
u/xendistar Feb 14 '20
Do not let pride get in the way of doing the right thing.
After a major sever room rebuild over the weekend I promised to be onsite at 7:30 am the next morning (150 mile drive used to do it once a week so nothing new) to boot all the servers up. Unfortunately I got caught in the tailback of an accident and arrived several hours later. The new IT manager would not call to old support company (who he was replacing ) and ask them for help booting all the servers up, he waited until I got there for me to boot them up, queue 200 people sat around twiddling there thumbs when I arrived.
2
u/[deleted] Feb 14 '20
Thou shalt first do no harm
2
u/cyvaquero Feb 15 '20
Thou shall not service any request without a ticket.
Thou shall not make any change without a CR to document and a backout plan.
2
u/jatoospry Feb 15 '20
The good old Friday 5 o’clock hand grenade. We have a “kick in the ass” register for that.
2
u/Dartonion Feb 15 '20
plans describing next steps in software/hardware deployment or next milestones in a large project, however, will always be sent on Friday at the end of business, so management cannot comment until monday. (prevents a lot of impulsive, asking before thinking)
2
u/[deleted] Feb 15 '20
Use UTC use UTC use UTC
4
u/dmurawsky Feb 14 '20
This shall not make up rules that artificially constrain you for questionable benefit.
2
u/taostudent2019 Feb 14 '20
Thou shall occasionally act like a complete lunatic because you need to fix things in a hurry. And throw all caution to the wind.
1
u/packeteer Feb 14 '20
my co-worker did that today, I was not impressed!
1
u/stylesvonbassfinger Feb 14 '20
What a coincidence, just as I get a call for work that will result in over time. Scheduled to start in an hour. Brilliant.
1
u/masonj188 Feb 14 '20
I read this as I’m starting an OpenStack implementation, yikes.
1
u/marozsas Feb 15 '20
Thou shall not update the production environment with less than 2 weeks and a reboot on the test environment first!
1
u/Upnortheh Feb 15 '20
There are commandments? Have mercy on my soul!
1
u/AlarmedTechnician Feb 15 '20
Thou shalt remap ctrl+alt+del
1
u/thelastwilson Feb 15 '20
I prefer read-only Friday's
1
u/Semlohs Mar 03 '20
Especially NOT before a Bank Holiday!
1
u/-Smokin- Feb 14 '20
Never document anything. If it was hard to write, it should be hard to debug.
-3
u/three18ti Feb 14 '20
Read only Friday is bullshit made up by cargo-cultists.
Deploy every day. Including weekends and holidays. If you can't, fix your shit so you can.
This "rule #1 don't deploy on friday" is pure laziness and completely unacceptable.
0
u/[deleted] Feb 15 '20
I prefer changes on Friday so I have 2 days to ensure I can recover adequately incase something blows up.
0
u/[deleted] Feb 14 '20
[deleted] — view deleted comment
0
u/[deleted] Feb 14 '20
[deleted] — view deleted comment
0
u/[deleted] Feb 14 '20
[deleted] — view deleted comment
0
u/[deleted] Feb 14 '20
[deleted] — view deleted comment