Troubleshooting checklist:
- DNS
- Fuck if I know
It’s always DNS
A haiku about DNS
It’s not DNS There’s no way it’s DNS It was DNS
Or as I’ve discovered recently while troubleshooting local infrastructure, the ARP table. Essentially the DNS of IP addressing
Restarting a server or booting a new instance has been my solution for years.
Honestly I get more angry when it’s my own site because then I have to fix it :P
On the contrary I get less angry when it’s my own site because I usually have at least some idea of what could have gone wrong
deleted by creator
Website down? Watch me travel into another one of the many
universeinstances of themultiversefediverse.People: “Please get this thing to work, my work/life depends on it!”
Me: “There are people whose work/life depend on my jank code/website?”Their life depends on it until it’s lunchtime. Then it doesn’t matter anymore. But woe to you if it’s not fixed when they’re back!
“Don’t these guys have a test suite⁈”
It’s me. Hi. I’m the problem, it’s me.
Is that a fancy word for prod?
Frontend developer: Listen I make pretty websites. This is a backend problem
Backend developer: the buttons disappear only on smaller screens - looks like a frontend problem.
If you work somewhere that actually makes money it’s very much like the first.
Can confirm. Sauce: Posting from my instance, it was down yesterday.
So I wanna a report on performance.
Sir this is one endpoint with no batch capabilities of which I have no access to change. There is no “performance”
I started to be more understanding of that after becoming a developer.
