⚠️🚨 PRO TIP 🚨⚠️

ZOOM IN ON TERMINALS + STAGE MANAGER = LITTLE SIDEBAR PREVIEW OF TERMINAL PROGRESS

For the love of buggery, stop watching bloody videos on your bloody phone with the bloody volume turned up.

I was thinking about something, just starting to get in the zone, when suddenly that tinny little speaker opened up a portal into the howling chaos of the underworld.

It sounds like cats fucking in an empty grain silo.

For the next half an hour, there is no room in my head for anything apart from the diabolical echoes of that bollock-wrenchingly hideous noise.

Today my cat, my oldest girlfriend, passed away. She chose to be in the sun for her passing. I'm happy she had a good life in the end with all the space she needed. She did not suffer. It was sudden and just a cardiac arrest.

May she hunt many more mice and little birds in the afterlife.

User: "I emailed my spreadsheet to a colleague. Why can't I see their updates in mine?"

Please just kill me now.

Born to "Dues Vult" forced "As per my last email"

everything microsoft makes is SHIT
for example, windows, and the fact that they bought out minecraft and ruined it with their bullshit "child friendly" feature
vscode's liveshare is ACTUALLY MAKING ME LOSE MY DAMN MIND TRYING TO WORK WITH SOMEONE
just now i was writing code and i realized, it wasn't even updating the file at all, it was just pretending to save changes, while on the hoster's end, nothing changed. at all
i had to rejoin the session 500 times, tell the host to restart, and it was generally a whole nightmare
nothing i typed in applied to the other end, and there were already 50+ errors from nothing in the php file i was working on
and it was erroring out at the most RANDOM spots, where nothing is wrong at all with the code, it was picking up something invalid, but NOT SHOWING ME WHAT WAS WRONG
i rejoined and saw a shit ton of test, an if that i never saw before i rejoined
in general why does everything microsoft make have to be so bad, and unreliable
smh microsoft u can do better

Our project manager is a past-retirement-age consultant who prefers to communicate the old-fashioned way, which is to physically pop in to my office asking questions about stuff that isn't even urgent and could easily be dealt with in jira or by e-mail FFS. Way to go disrupting a dev, break my flow and deprive me of my joy of working! He even says it himself: "May I disturb?" My answer is "No, but now that you already did, spit it out!" He's a nice and funny guy, I give him that. But I don't like this particular behaviour of his. I've complained to him directly and also to my boss, but to no avail. This is where devRant comes in, to let the steam out. Anyway, if I have it my way, we will definitely *not* be hiring the same consultant for our next project.

UX quiz:
a) trim whitespace characters from credit card or bank account input
b) refuse transaction, show error message: "no spaces are allowed in the card number"

Why are people from Norway so good at editing files in Linux?
Their ancestors are vi-kings.

man just please include the using statements in your examples, because i don't know what namespaces i need to use in your dumbass examples

I’m getting really tired of all these junior-turn-senior devs who can’t write simple code asking ChatGPT to solve everything for them.

I’m having to untangle everything from bizarre organization/flow to obvious gotchas / missed edge cases to ridiculously long math chains (that could be 1/10th the length), or — and I feel so dirty for this — resorting to asking ChatGPT wtf it was thinking when it obviously wrote some of these monstrosities. Which it gets wrong much of the time.

“ALL HAIL CHATGPT!” Proclaims the head of Engineering. “IT’S OUR PRODUCTIVITY SAVIOR! LEVERAGING AI WILL LET US OUTPERFORM THE ENTIRE INDUSTRY!”

Jesus fucking christ.

So here I work with this colleague that , at first , had a reasonable résumé. Whatever.

Time goed by and he is just doing tickets, clicking left and right, the usual grind of a shitty monitoring system which I am working intensely on deprecating that shit. Anyhoo

The last few days it became apparent that his resume was basically a hot air cake and he knows basically nothing intrinsically.
As I have stated before in previous rants, "everyone was a noob once"... But this guy...

He wants to do "something with Ansible"... "Ok what do you want to do?" , I asked (and I regret to have asked).
He basically wants to write new files on targets. Easy enough, I show him how he could do it with playbooks, inventory and role just for demonstrating the entire chain.

This guy chanes everything up, thereby breaking host group assignment, he launchea it on ALL machines...

Luckily it's a harmless file, so dodged a bullet there.

But the real wtf ia that he did it with the root account for our systems, without understanding the difference between "authentication" and "authorization"...

I am now explaining him what the difference is and how he can be able to check it. I give him the commands literally! ( sudo -l -U <user>)

Manages to fucking open up each sudoer file in vim , mistype or whatever he did in an attempt to leave vim... Breaks sudo...

Now he tries to spin it in such a way that I have steered him to break things.

"Dude you just fucking failed a copy/paste and you did absolutely fuckall without understanding what you are doing, then splurge out accusations because you did it wrong!"

FML

It's 10:30 at night, you have had two large glasses of wine, and its time to "play the shit outa minecraft!"...

Lets create a library.

Lets use that library in a project.

Lets wrap the library call in a wrapper functione to remove duplicate code.

Lets add an overloaded wrapper call that wraps the wrapper call that calls the library to partially undo the duplicate code removal.

Lets add another overloaded wrapper call that wraps the wrapper call that wraps the wrapper call that calls the library to partially undo the duplicate code removal.

How I love it. Not.

Sometimes redundancy makes sense, especially when it are two lines which make it obvious whats going on vs a single line that leads to a fuckton of overloaded wrapper functions.

Sheeesh.

Today in "code monkeys deserve divine punishment".

Another funny thing is creating a Helper class for Junit 5 tests, making it instantiable and adding to it all kinds of shit like testcontainer creation, applications instantiation, mocks, ....

... Then " crying " why the tests are so slow.

Yeah. Logic. Isolation of concerns, each test should be a stand alone complex.

But that would lead to redundancy... Oh no.

Better to create a global state god object.

Some devs... Really amaze me, especially when they argument in ways that makes one really wonder whether they are serious or just brain dead.

i have not been able to get a single error message to show up for hours. not one console log or warning.

i’m ok.

……

mmmmmmmmMMMMM
AAAAAAAAAAAAUUGHJHGHHGCGGVBVVGFUCKIGNFUCKPIECEOFSHITAFGJHFD

This is a story of suffering and despair.

I'm working on a build system for our firmware. Nothing major, just a cmake script to build everything and give me an elf file.

I'm fairly new to cmake at that point, and so it's not abundantly clear to me how the `addDirectory` command works.

Now those of you with experience in cmake will say:
"Hold on there champ, this is not a cmake command, the real thing is add_subdirectory()"

Well, that is not what chatGPT told me. I still trusted the fucking thing at this point, it explained that it was in fact a command, and that it added all subsequent source files from a given folder. When I asked it to provide me with sources, it gave me a dead link in a cmake dot com subdomain.

I spent FUCKING HOURS trying to understand why I couldn't find that shitty command, I looked through that shitty page they call documentation through and through, I fucking checked previous and nightly versions, the command was nowhere to be found.

Until I found an old as time post in stackOverflow...
Someone had made a macro with that name, that did what GPT had described...

On the positive side, I know cmake now. I also don't use this fucking deep Learning piece of shit. Unless you write simple JS or blinking LEDs with Arduino it codes like a Junior, high on every kind of glue on the market.

"The Perils and Triumphs of Debugging: A Developer's Odyssey"

You know you're in for an adventurous coding session when you decide to dive headfirst into debugging. It's like setting sail on the tumultuous seas of code, not quite sure if you'll end up on the shores of success or stranded on the island of endless errors.

As a developer, I often find myself in this perilous predicament, armed with my trusty text editor and a cup of coffee, ready to conquer the bugs lurking in the shadows. The first line of code looks innocent enough, but little did I know that it was the calm before the storm.

The journey begins with that one cryptic error message that might as well be written in an ancient, forgotten language. It's a puzzle, a riddle, and a test of patience all rolled into one. You read it, re-read it, and then call over your colleague, hoping they possess the magical incantation to decipher it. Alas, they're just as clueless.

With each debugging attempt, you explore uncharted territories of your codebase, and every line feels like a step into the abyss. You question your life choices and wonder why you didn't become a chef instead. But then, as you unravel one issue, two more pop up like hydra heads. The sense of despair is palpable.

But, my fellow developers, there's a silver lining in this chaotic journey. The moment when you finally squash that bug is an unparalleled triumph. It's the victory music after a challenging boss fight, the "Eureka!" moment that echoes through the office, and the affirmation that, yes, you can tame this unruly beast we call code.

So, the next time you find yourself knee-deep in debugging hell, remember that you're not alone. We've all been there, and we've all emerged stronger, wiser, and maybe just a little crazier. Debugging is our odyssey, and every error is a dragon to be slain. Embrace the chaos, and may your code be ever bug-free!

I wanna fuck a certain dev with a rusty pipe that was smeared in ghost pepper chilis... hopefully they get tetanus, inflammation and an allergy shock all at once, dying a cripple painful death.

Afterwards I spike them in front of the company with the wonderful laminated piece of paper:

"The difference between being right and being dead is where that pipe took place".

Fucking numbnut discusses every meeting like they know it all - and don't you dare critique Mr High and Almighty, cause then they will discuss as long as it takes without mercy.

HR wasn't mused as Mr Almighty filed a complaint cause I kicked them out of a meeting.

Now I've got Mr Almighty and Red tape and additional meetings.

-.-

wtf YouTube

I just burped out loud on a live call with about 30 people and I thought my mic was muted.

Man, my product owner is so fucking annoying. I am 50/50 between two projects when really it feels like I'm 100/100 - and the PO of one of the projects always requests that I join daily stand ups and give updates.

CUNT.

I don't always have updates because I'm working with another team. Why are you trying to micromanage me you fuck face. Also, you know when you get those PO's that are totally useless and don't actually bring any real value to the project except in the capacity of being a slimey charismatic weasel? Yah, that's this person.

people so damn concerned with what language you have or haven't used

i've been doing this for 10 years, give me the damn language or framework and i'll learn it and be productive in few weeks

sheesh

Other devs who say 'Jithub'

Gotta question. making my own deodorant. What scents would make y’all wanna fuck?

Devops (By Azure) is so stupid.... (I won';t even start of YAML, it will be a 10pages rant).

me : Ok I have 5 projects, each has it's own Azure conexxion for deploy.
Me : Can I do just ONE shared connexion ?
Devops : Yes. You need to click 150 buttons and it's done !
Me : Ok. /* doing actions */
Me : Ok ready !
Me : Project 1 do your release pipeline !
project 1 : Sure, just wait 5 minutes.
5 minutes later
Project 1 : All good.
Me :Ok now sharing test ! Project 2 : do your pipeline !Project 2 : Sure ! It's strated !
Me : Ok I'll go take a beer
... 1 hour later..
Me : project 2 ? PROJECT 2??!!!
Me : fine... going into logs.
Message : You must accept the shared conexion from Project 1 before pipeline can run
Me : WTF ? I literally just SHARED it to project 2,3,4,5 !!!

Why that idiot check ?!

One thing is sure, I hate devops more than I hate JavaScript.

Trying to refactor legacy code can be a real adventure. It's like exploring an ancient ruin, except instead of hidden treasures, you're uncovering cryptic code and dead ends. But the real plot twist comes when you realize there are no unit tests to guide you. It's like trying to navigate a maze blindfolded - you never know when you're going to hit a dead end and end up with a headache! 🤯

This nice little webpage shows the different dependencies of a npm package as a graph.

Gatsby seems like an implementation due for disaster.
https://npm.anvaka.com//...

a question for y'all:

just out of interest I would like to know:

are you *mainly* working on legacy stuff that is - without a question - just too old? everyone in your corp knows it needs rework but "EfFoRt JuSt ToO hiGh"? Where at the same time, most of dev time goes into maintenance and bug fixes instead of feature implementation.

If yes, do you fear that you're losing relevance on the market by not keeping up to date? What are your feelings about that situation?

did you maybe even quit a job in the past because of such situations?

---

Why do I want to know that?
- Had some beer
- As a freelance dude I often see battlefields right out of hell. I csn easily go, but the dudes working 9 to 5 on that??? Hoe can you oO

One time I had this conversation with my then PM:

PM: …so in total we need like 3 extra pages; the leaders profile, event showcase and lastly a contact page.

Me: Sure, already on it.

PM: Make it simple and quick, I told the client the updates would be live in an hour.

Me: Okay.

*{5 microseconds later}*

PM: Also the page headers need to be different from the other pages.

Me: Yes, you told me that earlier.

PM: Okay, just needed to re-emphasis.

*{sad disturbing minutes later}*

PM: I don’t know if deploying on azure would be better than having the website on AWS. The pages seems slow.

Me: Yep.

PM: Or maybe we separate the asset files from the main site using a CDN.

Me: You right.

PM: The other projects on AWS seems to perform better in terms of SEO. Don’t you think?

Me: I think.

*{this dude literally just lent me a jacket and won’t allow me put it on}*

PM: So after we are done with this update we need to inform the client about the benefits of switching servers to AWS. I believe they will agree or won’t they because the event is close by?

Me: {{pointed both hands at my PC hoping they’ll get the message}}

PM: Oh you done?

Me:

Weed > clubbing