Yes yes yes with the reading! Someone who knows this better than I do felt compelled to spend their time writing this. Guess I should READ it.
Yes yes yes with the reading! Someone who knows this better than I do felt compelled to spend their time writing this. Guess I should READ it.
Thank you for sharing what it’s really like!
99% of troubleshooting is looking at a bunch of CLIs saying: - OK, so that look good - No.. wait.. What the F?! - Did this ever work? - Check the changes - something isn't right - Oh... It was me that made that change - Repeat as necessary
"Did this ever work?" The MVP of "broken" or "missing" firewall access questions
Did this ever work.... how did this ever work.. are you sure it's not working... very common phrases throughout my work days.
repeat until retirement
Ah yes the “find out who did the stupid thing” check only to find out it was yourself. Happens too often to me :(
Me: "who wrote this garbage chunk of Perl??" My boss from across the hall: "Um, YOU did!" Oh, right.
The second mystery then is “Past-Luke had to have a reason it was done this way”
For me it's "...but I don't even _know_ Perl..." 😉
My favorite are the ones where you spend six hours troubleshooting only to end up *exactly* where you started... but now it's working... and you have no idea why.
the number of times this has happened to me is insane i cannot
It's arguably more infuriating than just staying broken. People understand when you rage-shout at stuff that *isn't* working; "WHY ARE YOU WORKING?!!" takes a lot more explanation.
Spent about 6 hours debugging yesterday. No logical cause could be found for the errors I was seeing, but I finally put a print statement in the right place. No it didn't show an unexpected value. It just made the code work correctly. Comment out that print and it falls again. Today - it just works
Ah yes. The "Magic" or "More Magic" switch. catb.org/jargon/html/...
Well said! I spend most of my day in the CLI, plaintext notepad/IDEs, GUIs, ticketing systems, and chat/email. Also bridges if it's a P1. We have a separate DC HW team mandated by our contracts so I don't even touch hardware without prior authorization and a 5 hour drive.
perfect meme to describe this 😅
100%THIS! I've spent years of my life watching progress bars. Troubleshooting is making some notes and diagrams and then finding ground truth in your system. The "Real Work" is just boring nerd shit!
Preach! So true. I still love it, though
100% of troubleshooting is pure guessing and hoping it's right 😂
It happens outside of your lab experiments! 🤓
Yeah it's mostly "Shit how did I not see that earlier" and reminding yourself for the 1000th time to validate assumptions before you start. Hard to make a training montage out of that.
it looks absolutely amazing when it flies. :)
especially when its done from 10 PM to 2 AM
I really like the hair style and color you've got going on!
Everyone: "Ooh, cybersecurity at a casino; that must be interesting. I bet you see some wild stuff." Me: [looking at the logs of the third IP spraying straight rockyou.txt at us this week getting auto-blocked] "Not as much as you'd think."