Oh you actually use the stack? I’m surprised you don’t just put all the tickets in a heap. I can give you some pointers on how to do that if you’d like.
I find that when a user continually makes a stink to get their ticket dealt with first, I gently try to correct them, and when that inevitably doesn’t sink in, and they call during a critical issue, I tell them quite firmly that things are down and nobody at x site can work, so your printer will have to wait. Log a ticket and I’ll address it when I’m done Brenda.
… They usually back off when you make it clear to them that they’re not the most important thing you’re dealing with at any given moment.
Can we call this out on terminal text editors too? Some just color lines based on their content, and frequently comments end up being blue on black and it’s impossible to read.
This comment describes the options for the next parameter in this config file, but I have no idea what it says, so I guess I’m fucked?
Chaotic evil is “creates ticket, but intentionally words the problem poorly before logging off, leaving the junior help desk worker to fend for himself, giving you the solution to a different problem that isn’t relevant in your case”
Really, there’s a vast number of ways for IT support to be evil or chaotic. I wonder if there was ever a viral fiction series in the early internet about it…
Well until you are deep into trait/future/generic territory. Because then you’ll go in big fuck (full type being in a separate file) not being correct somewhere in this shit.
Don’t get me wrong, I love rust. But those area really need some love
Still much better than C++ templates, and I say that as someone who used to genuinely love C++ template metaprogramming. Admittedly Rust traits+generics are far more limited than C++ templates, but very often I find that to be a positive. The list of things that I feel traits+generics are missing is small and rapidly shrinking.
Well, it is theoretically possible for code to cause a compiler to segfault. As for how, well that's a different matter. You'll need deep knowledge of the compiler, or else the assuredness that it can't possibly happen. Because then it will.
Oh God the horrors. The only part of these errors I ever remembered was “basic_string” everything else was the syntactic gibberish you wonderfully demonstrated.
Always remember, the silicon valley ethos of “break things” wasn’t about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.