ысвмимтиьтивыфсвма

What kind of sysadmin are you?

Find out who you really are: a Searcher, a Rollbacker
or a Keeper of Scripts.

1 / 9

1. What company sizes have you mostly worked at?

Mostly small - duct tape setups, but cozy

Small and medium - one admin, 100 tasks

Medium and large - where processes exist and no one messages you at 3am

Been everywhere - from garages to corporates

Big corps - hierarchies, approvals and tickets

2 / 9

2. What’s your bad IT habit?

I try to help everyone, even when I’m drowning myself

I don’t ask for help or delegate, I suffer in silence

I carry half the prod on my back because “if not me, then who?"

I write “fixed” in commits, even if I just changed an indent

Meetings, chats, standups, alerts - but where are the actual tasks?

3 / 9

3. What should a sysadmin always have on hand?

Terminal and improvisation

Scripts, templates and your own knowledge base

Git, changelogs and snapshots

Slack, Discord and Stack Overflow

Wiki, Confluence and technical docs

4 / 9

4. How do you fix config errors?

Look up solutions in docs and forums

Ask the community first

Roll back to the last working version

Trial and error

I’ve got templates - just fill in the blanks

5 / 9

5. You need to set up a new service. What will you definitely NOT do?

Configure it without rollback options

Work alone - I’ll check in with the team first

Reinvent the wheel - I already have a working setup

Skip reading the documentation

Look for other people’s solutions - I’ll figure it out myself.

6 / 9

6. What does your typical admin shift look like?

Lost in the chaos of a massive workload

Breaking stuff before lunch, fixing it after

Typing from morning till midnight

Writing reports and chatting with teammates

Chillin’ in the chair playing World of Tanks

7 / 9

7. You need to restart a server, but reboot is frozen and there’s no physical access. What do you do?

Dig through my old notes - I’ve had this happen before and I know the workaround

Read up on this kind of freeze - surely someone documented it

Check where the trouble started and restore the last known good config

Start juggling whatever’s left - maybe something will work

Blast a message in chats and forums - someone must’ve seen this.

8 / 9

8. Just saw “everything’s down” in the chat - and immediately heard this playing in my head...

Kanye West – Stronger

AC/DC – Highway to Hell

Britney Spears– Oops!... I Did It Again

The Doors – The End

Linkin Park – In the End

9 / 9

9. Beyond the cooling zone, a small utility room opens up. In the corner, covered in dust, an old printer whirs to life — a relic of the past. It growls and spits out a yellow sheet of paper: `“SLA: Uptime ≤ 66.6%”`

Scan the document and upload it to the ticketing system: “let L2 handle it”

Sign the SLA to appease the forces of the data center

Put the sheet back into the printer and press Ctrl+P — now it prints hundreds of copies

Laugh: “Competitors have it worse”

ысвмимтиьтивыфсвма

9. Beyond the cooling zone, a small utility room opens up. In the corner, covered in dust, an old printer whirs to life — a relic of the past. It growls and spits out a yellow sheet of paper: “SLA: Uptime ≤ 66.6%”

9. Beyond the cooling zone, a small utility room opens up. In the corner, covered in dust, an old printer whirs to life — a relic of the past. It growls and spits out a yellow sheet of paper: `“SLA: Uptime ≤ 66.6%”`