Usually I do love my colleagues, but lately....

FOR FUCKS SAKE I AM NOT YOUR WALKING HUMAN GOOGLE SEARCH ENGINE SHITOVERFLOW CHATGEPETTO INSTANCE! READ YOUR FUCKING LOGS, DO A FUCKING INFORMATION LOOKUP, READ THE FUCKING MANUAL.

OH YOU HAVE A QUESTION YOU SAY? PLEASE FOR FUCK SAKE ELABORATE WITH SOMETHING MORE THEN 'Please help me with the pipeline"' WHILE YOUR ACTUAL PROBLEM IS A LACK OF KNOWLEDGE AND UNDERSTANDING OF GIT, LINUX OPERATING SYSTEMS AND AUTOMATION.

OH YOUR BRANCH IS, WHAT, 3 MONTHS BEHIND MASTER? NEVER HEARD OF A FUCKING REBASE? WHATS THAT YOU SAY??? YOU DONT KNOW WHEN TO SKIP A COMMIT??? ITS YOUR FUCKING CODEBASE! READ THE FUCKING DOCUMENTATION !!!

WHATS THAT? YOU WORK IN VSCODE AND YOU DO T K OW HOW? AGAIN READ THE FUCKING DOCUMENTATION !

Self.end(rant)

Quality rant. Updooted.

The Curse Of Compentency strike again.

// readable version

@joewilliams007 while more readable it really takes away the feeling of my FURIOUS RAGE SCREAMING away...

@NeatNerdPrime yes but i dont want to hear screams. you can whisper it with an angry phase :)

What the hell was he doing all these three months letting his branch behind by that time??

I mean... VSCode is actually quite easy to use to rebase

It sounds shite, m8. Now, I have something that will deffo help. When some tosser interrupts what you're doing, they're expecting you to drop everything because they're the most important thing in the whole wide world. And presently, that's just what you're doing. Now, here's what you do: they ask you a question, you say, "I'm working on a tight deadline just now through the end of the day. Tomorrow morning would work better." If they started protesting, DON'T SPEAK! Smile, shake your head and walk away. Develop these deflecting responses. Practice with somebody, a friend. Have them running in the background all the time, ready to be used. Never again will you be shorted by a dweeb who needs to call their parents to tell them again the difference between a checking and savings account. Good luck.

What I've found helpful in these scenarios is to say "I don't know, let's look it up together"

Act as if you don't know squat and make them describe the problem. Half of the time they figure it out along the way via rubber duck.

If not - let them use their machine (to make it stick in their muscle memory) whether it be googling, reading docs or using commands.

I've had junior devs where I did this and I found out they had weird ideas; like when they googled they wanted to find super credible sources and didn't trust "a random stack overflow post" and we had to tell them it's ok to copy paste code and try it out, the answer doesn't have to come from credited comp sci genius.

Fucking quality rant!

@magicMirror

Love the term "curse of competency". I will plagiarize it 😁

@jiraTicket wait for real. Who even cares.
I guess I was used to rando blogs and SO's when I was learning cause I'm mainly self taught.

Like I mean understand what you are yeeting into the code sure. But idc if the bloody postman wrote the code if it solves the problem.