Happy Easter!

A colleague changes the location of a test helper file imported in a bunch of tests. Doesn’t bother to check where that file is imported (except where he’s specifically using it himself).

As a result good dozen tests fail later on. The culprit doesn’t realize. And the rest of us have no clue why.

Multiple people are asked to look into why the tests are failing.

"Ok, who’s working on what?
We’ll create a shared document to track who’s working on what test."

Document is created, people get assigned.

"Hold on, looks like it’s just a faulty import." "Oh yeah same here." "Yeah for me as well."

"Ok we could simply appoint one person to fix all the imports."

"Well I’ve already gone ahead and opened a pull request to fix the test I was appointed to."

"Ah ok, well who can take care of the rest?"

"Wait I also opened a PR."

"Ok so I guess we can each open a PR?" "No we can just have a single branch we can all push to".

"Sure, who’s branch are we using"

"You can use the branch of my PR"

"Guys let me handle this, it’s ridiculous for us to all be doing this separately."

"You’re right, go ahead".

——

The culprit? A senior dev.

What would have literally taken a minute to do (or even no time at all with proper use of the IDE) turned into hours of wasted time. People getting interrupted, having to drop what they were doing to fix the consequences of this guy’s laziness (seriously don’t know what else to call it).
Ok maybe our reaction could have been more efficient, but we never should’ve even gotten to that point in the first place.

This is how it works in my company:
-> Spend entire day in meetings - don’t get anything done.
-> Start working at 6pm if you want to get anything done.

Those who have gotten promotions are the ones that have bought into this system.
I guess I won’t be getting a promotion any time soon

I don’t get people who introduce their messages with TLDR.
Dude if it’s too long, then make it shorter! Or simply don’t start with TLDR if your content needs to be lengthy

I spend my days in front of a screen working on a product that will be used by other people working in front of a screen, themselves working for other people working in front of a screen

end of rant

In my previous job, they made me feel like they were lucky to have me. In my current job they try make me feel like I’m lucky to work for them.
I certainly preferred the precious position where I felt valued for what I brought to the company.

If I have any advice to give, it’s the following: if your current employer appreciates your work and treats you well, you should stay there a long as possible.

Also I’m wondering if my current employer purposefully makes its employees lose their confidence so they don’t go job hunting as they may feel they’re not good enough anymore to apply elsewhere.

I’m thinking of jumping ship but damn have I lost confidence over the past months…

JavaScript is to programming languages what English is to natural languages.
You heard me!

Interestingly enough, the worst JavaScript code I’ve ever had to deal with was written by back-enders coming from a Java background. The app was unusable and it took me a few weeks to put it back on track.
So is JS the culprit, or is it the elite backend community that fails to even try to make good use of it? 🤡

Many "purists" love to piss on JavaScript and web development. And to an extent I can understand ostream’s frustration with these people.
It’s easy to criticize because yes: many web projects are indeed shit.

But I’d like to argue that the reason why so many of these projects are crappy is because of bad management:
- unrealistic deadlines
- no clear testing strategy
- or no testing at all because of deadlines
- no time allotted to catch up on technical debt
- etc.

This type of management is far more commonplace in web projects because things need to get delivered quickly and if they’re delivered with bugs, it’s no big deal as lives aren’t at stake.

I doubt this type of management is tolerated in projects where you’re working on software for welding machines (for example), where the stakes are that "you’re expected not to kill anyone" (to quote demolishun)

So in these types of projects, management can’t tolerate anything much below perfection and thus has to adapt by setting realistic deadlines that take into account the need for quality processes and thorough testing.

If this type of management was more common in web development, I can guarantee that web applications would be much more reliable and of better quality.
I can also guarantee that poorly managed non-web projects as outlined above would be just shitty as many web products.

My point being that’s it’s really DUMB to criticize fellow devs that work with web technologies on the basis that the state of websites/web apps is a mess. It just so happens that JS is the language of the web and that the web is where things are expected to be delivered quickly (and dirty … but we can fix it later mentality)
Stop acting like you’re the elite. I have no doubt you’re super smart and great at what you do. So be smart all the way and stop criticizing us poor webdevs that have to live with the sad state of affairs. ❤️

devRant has become such a dump. At this point I’m wondering when dfox and trogus are finally going to decide to pull the plug

You don’t have a choice

How can someone be applauded like a hero for fixing a bug when he’s the one who caused it in the first place?
Gosh Bill, thanks for saving the day! The least the guy could do is acknowledge he fixed something HE broke. But that’s wishful thinking on my part, isn’t it…

Anytime I see content including this emoji 🚀, I just want to close whatever page or post it’s a part of right away

My company is (supposedly) all about collaborative work, pair programming, getting on calls and cRaCKinG tHinGs ToGEtheR. Also (and rightfully so) we’re not supposed to approve any PRs if tests weren’t created/updated.
Of course that applies to all but the old timers in the company who simply act like lone cowboys. They fall off the face of the earth for two-three days then reappear with monster PRs full of untested code.

Leave it up to the plebe then to try to make sense of the mess they’ve created, to challenge them with the fact that the PRs are lacking tests (only to be met with excuses about not having anymore time to spend on the subject).
Reprimand the plebe for not reviewing PRs thoroughly enough. Leave it up to them to fix the resulting bugs.

I’ve lost all trust in our managers, tech leads, lead devs and their guidelines and rules that only apply to others but rarely to themselves. These people that then have the audacity to criticize the tech team in it’s entirety for not being rigorous enough in its processes.
Fuck them all

Life at work these days:

Manager: we’re not getting enough done
My calendar: 1/3 week filled with scheduled meetings

Manager: we need to use ChatGPT intensively. We'll go a lot faster.
Me using ChatGPT to get it to write an automation script: 2 hours wasted with no success
Me starting again from scratch to write the script: 15 minutes to achieve the desired result.

Thanks for your advice boss

Mac fucking book pro! No! Just because I brushed up against you doesn’t mean I want you to boot up! Do you think I’m that eager to turn you on? Is the usual brain dead Apple user that fucking lazy to not wanna press a button to turn his computer on? And there’s no fuckin’ way to change this behavior!? I tried changing system variables but none of the suggested tips work. And you even have Apple support people ask: "why WOULN'T you want it to boot up if you sneeze on it?" FUXKKLK

I’m rarely at the initiative of a meeting, but when I am, my approach is: what questions need to to be answered? Time spent in the meeting is answering those questions without beating around the bush. I request precise answers, no "we shoulds" or vague responses. Meeting usually ends with clear answers/resolutions written down and shared so there aren’t any "that’s not what we agreed upon"

Exploring new ways to learn how to code

!dev
This was a long time ago when I was a pizza delivery guy (summer job). One of my managers could barely handle any pressure. He would often lose it during the dinner rush. He was disorganized and never gave clear directions to his team. One night he totally blew up. He threw a large pizza shovel across the kitchen. It went crashing into the oven in a loud bang. This was in full view of customers on the other side of the counter and several of us workers, all in shock.
It was my last night there as I had handed in my resignation letter two weeks prior. Boy was I glad to get out of there

A programmer must have named this place

Anyone here use generator functions in JS? Seems like it could be useful but whenever I explore the possibility of using one, I usually end up going another route

This was a pretty bad interview process

https://devrant.com/rants/5443046/...

What’s funny is that they told me I lacked experience, but then within the following year they called me at least 5 times asking if I was available, as they were desperately looking for someone.
No thanks

How do you guys deal with looking for a new job while still working at your current job?
I’ve been having to sneak out of the office for phone interviews. Not fun…

The good ol’ days of devRant where one could get +600 upvotes for a corny joke

https://devrant.com/rants/284300/...

(I’m not jealous 😁)

PM (on slack): "we’re about to deploy to production".
Me: "ok"
… I keep on working on a task / remain available for any post deployment issues …
PM (5 minutes later on slack): "deployment broke production! We need to handle this NOW!"

My dev colleague has already called it a day, but I’m still online

Me: "ok I don’t have access to prod, can you describe what’s going on? I can’t reproduce on any other environment"

PM: …

10 minutes go by

Me: "anybody there?"

PM: …

45 minutes later, I realize PM is offline

The following day:
PM: "ok we got prod running again" (turns out it was client’s fault for not updating a config we as devs can’t access)
PM: "but we’re REALLY UPSET! You guys need to be available to intervene for any issues following deployment to production! At least one of you should be available!"

Me: "but, but…" 🫠

Here I am for three months trying to implement TypeScript in this project that was a dump when I picked it up.
And then some morons get assigned to the project and just start adding @ts-nocheck everywhere?
Like, WHAT THE ACTUAL FUCK?

And then you wonder why the project is bug-ridden??
FUCK THESE PEOPLE THAT CALL THEMSELVES JAVASCRIPT ENGINEERS!! NO WONDER JS GETS SUCH BAD PRESS WITH ALL THESE CLUELESS IDIOTS TO WHOM STATIC TYPING IS JUST AN OBSTACLE TO THEM CHURNING OUT LINE AFTER LINE OF "CODE"

Me reviewing PRs lately:
"Should I fight it now, or should I let the abscess grow?"
——
But in my distress/demotivation it’s usually: peace now, pain later

I’m pissed.
I had previously ranted about being assigned to a very messy project. I spent 3-4 months alone adding features and CLEANING things up.

Recently, there had been talks about a new major development phase on this project. But things lingered and the day before I’m to go on vacation, I get the news that this new phase starts in 2 days. Since I’m going to be on break they’re putting other guys on the project who don’t know anything about it.

Fast forward two weeks later.
I’m back from vacation.

I find out one of the guys has strong opinions about doing things certains ways… but unfortunately they are "ways" of unnecessary complexity, abstraction and verbosity.
After just a couple of weeks I’m already lost in the complexity of his code, which supports features of VERY LOW complexity. Fuck, has he ever heard of KISS? Has anybody heard of it where I work?

Now I have to spend my mental energy trying to make sense of this pile of crap rather than actually spending it getting things done.

[Half question / half rant]

Would you rather work with a laid-back, humorous colleague who produces shit code and won’t understand advice for improvement?
Or would you rather work with someone who’s more serious, even slightly boring, but who takes quality seriously and is open to advice?

Yes I’ve worked with both types. Hands down I prefer working with the latter. With the first dude I’ll have good conversations and a good laugh at his puns and jokes. But at the end of the day I’m pulling my hair trying to make sense of his code and spending a shitload of time reviewing his PRs just to make sure he’s not fucking things up even more.

Product owner (who is also the application administrator): please build feature to allow administrators to create automatic alerts to be sent to application users

Me: ok
Feature gets built, tested and deployed to production

Two months later:
PO: I've noticed in our monitoring tool that there haven't been any alerts sent out to users. What's going on??

Me: well have you created any automatic alerts?

PO: umm, no. How do we do that?

Me (inside): 🤦