Troubleshooting checklist:
- DNS
- Fuck if I know
53ReplyIt’s always DNS
17ReplyA haiku about DNS
It’s not DNS There’s no way it’s DNS It was DNS
8Reply
Or as I’ve discovered recently while troubleshooting local infrastructure, the ARP table. Essentially the DNS of IP addressing
6ReplyRestarting a server or booting a new instance has been my solution for years.
4Reply
Honestly I get more angry when it's my own site because then I have to fix it :P
32ReplyOn 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
15ReplyPermanently Deleted
8Reply
Permanently Deleted
22ReplyPeople: "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?" 16ReplyTheir 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!
1Reply
Frontend developer: Listen I make pretty websites. This is a backend problem
13ReplyBackend developer: the buttons disappear only on smaller screens - looks like a frontend problem.
8Reply
“Don’t these guys have a test suite⁈”
13ReplyIt's me. Hi. I'm the problem, it's me.
16Reply 24Reply
Is that a fancy word for prod?
5Reply
If you work somewhere that actually makes money it's very much like the first.
6ReplyCan confirm. Sauce: Posting from my instance, it was down yesterday.
4ReplySo 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”
3ReplyPermanently Deleted
0Reply