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
It 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.
deleted by creator
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!
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.
“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?
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”
deleted by creator
