Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I really fucking loathe StackExchange. Some poor soul had the nerve (THE NERVE!) to ask a question about something they didn't understand (HOW DARE THEY!):
"What is the difference between a ping and a get request? The goal is to see if the site is up."
And par for the course over at smarmy-fucking-smug-pedant-land, in less than three hours, the question was closed: "[C]losed as not a real question... It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form.
Allow me to indulge in some pedantic, "well actually" fuckery of my own...
Well actually, that actually is a 'real' question, because it's, you know, a fucking question. There's a question mark in there and everything! The person is asking what the difference is between two different things, and we can tell it's actually two different things because the person uses two different fucking nouns. And not only is this person asking to know what the difference is between these two different things, they even give us a use-case for why they're asking the question: they're pretty sure that they think they might know there's at least two different ways to check that their website is up, they just want to know what the difference is between those two methods -- hence the two different fucking nouns. It's almost like they're trying to give us some contextual information about why they're asking so that even if there is some vagueness to their question -- which is bound to happen IF YOU KNOW YOU DON'T KNOW EVERYTHING ABOUT THE SUBJECT, WHICH IS PROBABLY WHY YOU'RE FUCKING ASKING -- then a reasonable, decent, helpful person who is making a good-faith effort to be helpful can infer from that context enough information that clarifies the question enough to remove any vagueness or ambiguity and thus provide a helpful answer. AND THAT'S WHAT FUCKING HAPPENED!
And what just fucking galls me to no end... the question was answered (SUCCINTLY, INFORMATIVELY, SIMPLY, AND CORRECTLY!) and even marked as accepted in less than fifteen minutes after being asked.
And that didn't stop some smug fuck from being an asshole and closing the question because "fucking scrub noobfags need to git gud."
https://serverfault.com/questions/...
If MySpace was a place for friends,
then StackExchange is the place for insufferably elitist smug cunts.4 -
Recruiter of the day: "Hi [...] I think you will be very interested in <random startup name>. You will work on Digital Projects."
Oh, really?!? I thought I would wrote code on paper!3 -
I’m becoming really frustrated working with my current project. It’s like someone’s dog ate the requirements and all stakeholders are on a different page on what’s needed/wanted. I’m fishing for the info I need and try to decipher the vagueness I get. I know I could just call a meeting and try to get us all on the same page there - but I’ve been in a few meetings with this specific lot of people, and I know it’s just going to end up in much more confusion...3
-
The amount of repetition and vagueness in this unsollicited recruiter job invite is insane: "Current Technology Sector Consultant". I've had 10's of invites from these recruiters on Linkedin, blocked all of them and they just keep coming back despite my Linkedin preference being set to let recruiters know "that I'm NOT open to opportunities"
If you ever get an offer from VMR consultants / J People consider these reviews carefully: https://glassdoor.co.uk/Reviews/....
I'm naming the company because it seriously deserves to be exposed for its bad practices towards both their potential and current employees.
3 -
It's not often that I yell, or even write in all caps. And it would be very nice to be able to write in red, all caps, bold text but there's something that I would really like to say, or rather yell, to || at my systems development teacher (and a bunch of other people), and it's this:
STOP BEING SO FUCKING VAGUE ABOUT SHIT THAT YOU SHOULDN'T BE VAGUE ABOUT SHIT. I'm really really really really really really tired of listening to "probably" and "maybe" and "there's a chance that" about shit where those words shouldn't be applicable. I don't really wanna hear about what the C# compiler probably does (with like 2 different suggestions) and I don't wanna hear about what laws there might be in place and possibly and probably and oh god just stop -
Yo what the actual hell is up with the lack of Azure AD B2C documentation, the error codes are pretty ass too! Had a similar problem many users faced & on stackoverflow everyone had different solutions. My solution wasn't the accepted one and it has 2 upvotes ....2 UPVOTES!!1
Top Tags
Weekly Rant
View