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