Junior Dev: "The man told me I have to use his framework but I don't know shit about it"
Me: "hmmm, since it's something he developed, you should ask him for some documentations or some examples"
Junior Dev: "I did!! That bastard gave me an example but I can't do anything with it. It's just executables, some config file and NO sources"
Me: "well, this sounds odd to me. You're telling me he just sent you executables and not a single source ? There is no .cs file in there?"
-- 2 minutes later --
Junior Dev: "now that I see ... The sources are there ... BUT the damn bastard put them into subfolders ... And there isn't a Solution file ... How could I even ..."
And THAT was the moment my brain collapsed into a black hole, obliterating me from the existence. Or at least that was what I wished for.

Me: "ok let's have a look at this code I have to review ..."

try
{
* Some random unreadable overcomplicated shit code *
}
catch (Exception e)
{
// Useful for debug
}

😓
In which God forsaken crazy alternative universe, a "catch all" block that swallows the exception and does nothing else is even slightly close to the concept of "useful for debug"

Alleged senior dev in a company I was consulting at 👴: "interfaces? I never use those. I don't believe in interfaces"

I remember my first "Software Engineering 2" class at University. The teacher, a pompous son of a bitch that later on gave proof of his vast ignorance, greeted us with
"so ... You call yourselves programmers, right? What's the biggest program you have ever wrote? Something along the 100, maybe 200 lines of code? ..... If you've never written at least a MILLION lines of code software, you're not a software developer"
Even at that time, with my lack of experience in software development, I had that feeling in my guts telling me "writing myself a 1M lines of code software .... Brrrr that's something I hope I'll neve have to do in my life"
Turned of he was one of those dinosaurs stuck with the love for gargantuan monoliths of software like they used to do.
Just to dive you the whole picture, the course had ZERO software development and focused only on how to manage wonderful waterfall projects, how to write all types of software documentations and the final project was ... Writing a ton of documentation so boring and useless that even he didn't care to read through.
we still laugh at the episode when another group asked us to borrow one of our documents and after one day they asked "hemm ... Have you really sent this to the teacher?" "yes, why not?" ".... at page 23 someone left a comment saying 'what the fuck is this shit?'"

After a painstakingly slow conversion of a VM virtual hd, I got informed with this.
My heart skipped a beat seeing that icon.

Today a junior dev from the company I'm working at as consultant, suddenly shouted:
😤"why the hell my software behaves differently on every pc here in the office ... But it works on my machine? I'm sure there's something wrong with the OS/Framework"

🤔 let me think for a moment ...
* is it because the whole office keep developing like the ancient romans did?
* is it because that software is such a mess that requires a wizard in order to manually change all the magic configuration strings ?
* is it because every damn developer there has his particular environment and the word "container" reminds you only the show where the people bid for unclaimed shit ?
* is it because the "guru" at your company decided it was a super cool idea to wrap EVERY single external library (that just works out of the box) into some obscure static helper without even a single trace of documentation and clue of what's wrong?

🤗"I don't know... Must be a bug in the OS or framework for sure"

dev "no no no, you're overengineering it. You just need one class for that"
Me "but ... Those are different object that share a common interface. The internal logic is not the same, only their output is. You know ... That's the purpose of interfaces"
Him "no no, as i said, you don't need that. Listen, you can put ALL the fields and methods in a single class and then you can use a switch with different cases .."

Shit fuckin fuck shit damn [put whatever bad word you want here]
My phone fell on the ground and this time got hit on that specific weak spot that caused a ripple of cracks on the glass screen.

Everyone is posting jokes about GitLab recent incident and how the guys responsible for that must be feeling right now.
Shit happens, sometimes it's you accidentally deleting a branch on your repo and turning that into a major crisis, sometimes is a huge mistake that impacts not only the whole company business, but also it's clients work.

This situation reminds me of a famous quote from Thomas J. Watson (ex lBM CEO):

"Recently, I was asked if I was going to fire an employee who made a mistake that cost the company $600,000. No, I replied, I just spent $600,000 training him. Why would I want somebody to hire his experience"

Those guys at GitLab have probably learned one of the most expensive lessons in IT world and I really wish them to come up with a solution that not only fixes this case, but that helps them preventing future occurrences.

Me 🤗"Since you know the domain far better than me, can I ask you to help me understand if I managed to cover all the edge cases with these UNIT TESTS?
😒" no no no, you don't need to check for those cases, you already do that in your code"
🤗 "I'm sorry, I must have explained myself badly. I have written these UNIT TESTS exactly to ... TEST if those CHECKS in my code work and what I need is you to tell me if there are additional cases ..."
😫"but you don't need to!!! You already have that logic in your code"
😐😵☠ 🦍💊🔫🔪"you know what? I'm gonna give them a second look. Thanks"
And then I moonwalked out of the room

Worst hackaton? The one when i realized too late i was stuck with a bunch of kids bragging about being "devs" because they knew how to download an html template for wordpress 😭

I had a client that used to send emails to detail requests or report bugs on a software.
Now, believe it or not, this was the regular way:
An email with just an introduction and a Word document attached, containing very verbose descriptions (usually not in a human known language) and most importantly, screenshots.
What's so weird about this? Those pictures were captured with printscreen, printed on paper, scanned and then inserted inside the doc 😭😭
Why all this? I don't know, otherwise I wouldn't have posted it as #wk32 ☺

What's worst than waiting in a queue inside a mall in the middle of Christmas last minute shopping spree?
Low connectivity when the only thing I want is reading some devRant post 😱😓

Dat moment when you give the first upvote to a new ranter 🤗@Tribex

And then, looking for the source of a bug in the code .... I randomly found this:

public bool IsOperationStarted { get; set; }

public bool IsOperationStartedTrue
{
get { return IsOperationStarted == true; }
}

public bool IsOperationStartedFalse
{
get { return IsOperationStarted == false; }
}

Hmmm let me think ...🤔
Is there really a need to distinguish ? Are there any useful meetings out there?🤗

Dev1: "what was that requirement? I mean, do you remember that little yet hugely important detail ...?"
Dev2: "hmmm sort of ... Maybe it's in one of the emails, possibly 2 months ago. Let's try to find it"
Dev3: "wait, probably Dev1 was not included for some reason in that thread of emails"
Dev2: "no wait, I mean the other, the one we used to talk about those other specifications from previous meeting..."
[and the story goes on]
Now you may think "ok, this event happened once and was a misstep. Shit happens"
Actually, this is the bread and butter in this company I collaborate with. All their requirements are spread across thousands of emails, usually mixed together and possibly forked into different threads. Often people are cut out from conversation because someone forgets to "reply all", other times they're lost in time.
When I asked them "why don't you use some other tool, maybe something more organized and easily searchable, something structured..."
They replied "no no, we prefer to use email for historical reasons"
My brain just melted like chocolate under the sun

Started a new contract:
Dev: "here, take this draft document containing a rough explanation of the requirements and write this service that exchange messages with these two subsystems"
Me 😐"ok"

-- couple weeks later --

Dev: "oh btw, you should go through ALL the fields in those messages described in the 'documentation' and double check them because we use millimeters and they use meters, we measure milliseconds and they use seconds. You should handle conversions when you deal with those messages"

Me (in my mind): "fucking son of a bitch! Why didn't you tell me this little piece of information at the beginning so I could have accounted for that instead of bloating the code now with your spaghetti style, full of horrible hacks, ifs and workarounds?
Me 😐: "sure, I will"

(don't worry, in the end I managed to find a clean solution for that 😉)

Reading a couple rants from students and teachers lately, brought back to my mind a memory from the first lesson in my Software Engineering course when I was in college.
Teacher entered the room like he was the king of the world, turned around facing the students and started his intro speech:
"my name is {name} bla bla bla I will teach you software engineering bla bla bla let's point out one important thing: In your life you have written how many lines of code for a software? 10? 100? If you have NEVER written at least 1,000,000 lines of code for a program, you're not a developer. Now let's start talking about waterfall, endless specification requirements and meetings..."

Me 😐
And that was the moment I left the room moonwalking

"My code" only exists when you work alone on your precious project. Do not carry over that mindset when you work with a team or you will just ignite another endless holy war

Me reviewing some high school level exams after an Excel course.

"hmmm the next question is 'what does the symbol $ mean when found inside a FORMULA in Excel' ... Let's see what they answered..."

* "it's the symbol for DOLLARS" <-- well, he tried
* "I don't know" <-- mmh ok, he doesn't know
* "it can be either a plus or a minus" <-- mmmh maybe the interpreter will just figure out the correct one
* "it's used to keep an index fixed when you copy/drag the formula" <-- nice, someone who actually followed the lesson or at least knows how to google things when the teacher doesn't see
* "it's the symbol for POUNDS" <-- WTF!! Wait a moment: POUNDS???? Have you ever lived a single moment in this world?

Some time ago a salesman tried to sell me a super revolutionary solution. He introduced it with "today everyone will tell you that in order to save money you must move your servers and IT infrastructure on the CLOUD (big emphasis on the word) but we offer you a different approach: 'the on premise cloud'"
😶"so, you're basically telling me to replace my local machines with other local machines?"
😎"you don't see the whole picture: It's the cloud but INSIDE your company"

Am I dumb and I didn't see the obvious technology leap he was offering me?

Client: "I've started as a software developer too" *chuckling* "so I understand EXACTLY what you say... But could you just explain me what do you mean with 'legacy code' ?"
Me: :|

Dev: "I've pushed some code. Give it a code review."
Me: "ok, i'll do it"
<<fast forward>>
Me: "Sounds good to me. Only thing, I wouldn't have gone for all those renames because that was not part of the request, maybe we can discuss ...."
Dev: "I like those names and besides, it's already deployed in production"
Me: " :| .... what's the purpose of a code review when you push straight into production ?

PM: we have plenty of time to develop this app. The client is so slow in providing designs and specifications that it took them 2 months just to give me this lousy mockup where they copy/pasted UI element directly from Photoshop. Btw, i have a meeting this afternoon with them :)
ME: ok. since it's Friday, monday you will update me :)
[Fast forward the weekend]
PM: where the hell is the App ? the client told me we have less than one month to deliver it. why didn't you provide a fully functional pixel perfect prototype yet ? Why don't you communicate with me ?
ME: :|

Why do clients wait for 17:55 before asking you to fix that nuclear reaction bug or that new "little insignificant feature i can't live without" ? Seriously, what the hell is your daily job ? Because i really want to switch to it.