Fuck Cypress. It’s a fucking goddamn pile of diseased garbage. Its design decisions actively fight against you, its methods don’t work, it’s unreliable as fuck, and it intentionally keeps stale state so your tests fuck with one another — and that even fucks up its own interface so nothing fucking works.

It’s like stepping into the shower and expecting clean water, but instead it’s just some obese guy with diarrhea shitting in your hair, and then getting all indignant that you’re upset about it.

If you consider using Cypress for something, find another project.

I mean, what’s not to trust? I’m sure it’s virtually secure and private.

Mommy Microsoft really wants all your data in Windows 11.
The Facebook of operating systems.

Recruiter: So you’re in Canada?

Dev: One sec let me check

*Points webcam out window at ongoing blizzard*

Dev: Yup, that looks like Canada to me

Recruiter: Ok I am just confirming

Dev: Me too

Military grade encryption: md5
Enterprise grade encryption: Base64

I was recently hired as a lead devops to a giant shit show. The CTO said he needs someone to do things correctly instead of quickly. This is a conversation I just had this morning

HR: We want you to interview a potential new DevOps engineer
ME: okay, when?
HR: Tomorrow
ME: I won't be able to create interview tests and materials for tomorrow. How's next week
HR: This hire is urgent! It has to be tomorrow
ME: Then you'll have to do the interview without me
HR: We need you to interview them because we've had a few bad hires in the past that we don't want to repeat
ME: The best way to filter out bad hires is with technical tests, which will take time to develop. I can be ready by next week.
HR: We can't give you a weeks notice for each hire, we are in urgent need for more devops.
ME: ...

> Find cool repo on GitHub
> Works very well
> Respectable weekly downloads
> …Hasn’t been updated in a year
> …Owner from Shanghai, China
> …Hasn’t pushed to any repo in over a year
> Last profile update: Feeling sick 🤒
> …
>😔
> Rest in peace friend, thanks kindly for the time you’ve saved me.

Interviewer: Do you know what Kubernetes is?

Dev: Yeah, that’s the greek god of spending money in the cloud.

Interviewer: Actually Kubernetes is an orchestration tool. Have you not been on a project that uses it yet?

Dev: …

In pair programming session with intern. She deletes something she shouldn't have.

Me: No, wait, don't delete that, undo.
Intern: ...
Intern: What is undo? How do I do that?
Me: ...
Me: *cringes internally*
Me: Uhm.
Me: Go to Edit > Undo, or press Ctrl+Z

I think I understand what is wrong, this poor individual has extremely rudimentary computer literacy skills worse than my 77-year old stepdad's and someone in management decided to give her a Junior Software Engineering position (actually paid internship) which is doing more harm than good.

Just scored my personal red flag bingo in new project:
- engineers who work there for 20+ years
- their own in house build tool
- "we have Jira so it means we are agile"
- "we have Jenkins so it means we do Ci/cd"
- git adoption is "in progress"

🎉 As of today, I can proudly count myself among the members of the "Killed Prod on A Friday Afternoon" club. 🎉

3 hours of interview end up asking me

“Are you Chinese”
“Why don’t you look and sound Chinese”
“We only hire Chinese speaking candidate”

After told them that I withdraw my application as they only hire “Chinese speaking candidate” , they started to yell “you not professional , you waste time , I will ban you for life, you quick quick go away.”

So I ended up telling people not to join that company.

Ah yes. Fuck you

Dev: So how do you want this feature fixed?

Manager: It should work how it worked before.

Dev: I'm new to this feature, I don't know how it worked before or what is broken about it.

Manager: Well just make it work like it worked before.

Dev: I DONT KNOW HOW IT WORKED BEFORE THAT IS WHY I AM ASKING YOU. PLEASE TELL ME SO I CAN DO MY JOB.

Manager: Just how it worked before!

Dev: ...

Manager: ...

Dev: fuck you

My bosses, bosses, boss asked to call me up unexpectedly:
BBBoss:" Just wanted to say we are really happy with your performance, especially in these tough circumstances, ... "
Me thinking: "Ah, great I am getting laid off."
BBBoss: " ... which is why we decided to give you and extra 1000$ in you next paycheck."
Me: "??? ... for real."
BBBoss: "yes, thank you for your hard work."
Me: "I am still employed?"
BBBoss (laughs) :"Yes, we are happy to have you."

Fuck you, I Quit

Dev: What do you think of the new version of the app?

Client: It’s great! We just have a couple notes of feedback we are working on compiling. We should have those to you by next week.

*Next week*

Client: We need another week to compile all of this feed back we are generating

*Another week goes by*

Client: Still working on it, it’s going to be a really thorough review when you get it though. No stone will be left unturned!

*2 weeks later*

Client: Here it is!

Attached: A word document with a single line of text “can’t nobody log in” next to a picture of the login screen with a red circle drawn around the login button

Client: Can you hurry up and action our feedback? We want to go live next week

Dev: …

Manager: THE SERVER IS DOWN THE SERVER IS DOWN!!!!

Dev: Ok I’ll look into it

*5 mins later

Dev: Wow these are really strange logs, it’s like config values are being changed all over the place while I’m looking at it

Manager: Well I figured while you were looking into it I’d go i to the server settings and change everything I could find in order to try and get the server back up again. Two sets of hands are better than one, Is it up yet???

Dev: …No.

Manager: I THOUGT YOU SAID YOU’D LOOK INTO THIS. I NEED ANSWERS NOW. WHAT IS TAKING SO LONG?!?!?

Dev: …

I'm going to install linux...

English is weird.
Take the double oo for example.
There are so many different pronunciations for it and there seems to be no rules whatsoever.

mood
wood
blood
door

All different

The real reason that i started using split keyboards

Dropbox TLS 1.0 & 1.1 is deprecated
Dev: we need to upgrade our projects
Manager: we don't have time for that. can you call to their helpdesk, so we can keep using our projects w/o upgrading?
Dev: ....
Manager: call them!
Dev: ...

Relationship Status: just tried to reach for my dog's paw and he pulled it away so I pretended I was reaching for the remote.

Oh you're a frontend guy? Good, we need one of those.

Oh you're a backend guy too? Good, we need one of those.

Oh you're a security guy too? Good, we need one of those.

Oh you're a devops guy too? Good, we need one of those.

Oh you're a QA guy too? Good, we need one of those.

Oh you're an SEO guy too? Good, we need one of those.

"Well, sorry to say fullStackCraft, but we found your cloud architecture skills just a little too lacking for this position. We really need someone who can do frontend, backend, security audits, QA assessments, SEO, AND build scaling cloud architecture. Oh and while you're at it, can you turn fucking water into gold? We need that at our company too. You didn't get the position, but it'd be great if you could refer us to someone who is very advanced in fucking alchemy. Thanks!"

Absolutely toxic the way software people are treated I swear. The money may be the only good thing that is left.

Manager: This code you wrote violates the single responsibility principle!!

Dev: How so?

Manager: You have one function that you call in *MULTIPLE* places. That’s too much responsibility for one function! Functions should only have one responsibility!! Creeping the scope of a function beyond that is a TERRIBLE way to write code!

Dev: But why spin up multiple functions that all perform the same thing?

Manager: Well if a function has a bug in it and you use that function multiple places then that bug exists everywhere you use that function. If a function only has one responsibility then if it has a bug that bug will only exist in the single place it is called! You really should think first before asking questions like that.

Dev: …

The most disappointing (not so sure about upsetting) rejection was from none other than Google.

I was ecstatic when Google respond to my application by inviting me to an interview. If I recall rightly I had two pre-interview screenings, two technical interviews, and about four interviews with people. The people were great and the HR person I was dealing with was open that the feedback was all good.

And then the rejection came! I called the HR guy and asked what happened. He said there’s a central group somewhere who approve all hiring and they decided I hadn’t worked for a “big enough” company in the past.

Yet - my potential colleagues and manager thought I could do the job, I passed the Google-scale technical tests … and then some faceless person somewhere says “meh” and that’s that.

It’s not like they didn’t have my resume that whole time, or the opportunity to ask any questions they wanted !

So that sucked.

I HATE this kind of popups

"Hey, Root, someone screwed up and now all of our prod servers are running this useless query constantly. I know I already changed your priorities six times in the past three weeks, but: Go fix it! This is higher priority! We already took some guesses at how and supplied the necessary code changes in the ticket, so this shouldn't take you long. Remember, HIGH PRIORITY!"

1. I have no idea how to reproduce it.
2. They have no idea how to reproduce it.
3. The server log doesn't include queries.
4. The application log doesn't include queries.
5. The tooling intercepts and strips out some log entries the legendary devs considered useless. (Tangent: It also now requires a tool to read the logs because log entries are now long json blobs instead of plain text.)
6. The codebase uses different loggers like everywhere, uses a custom logger by default, and often overwrites that custom logger with the default logger some levels in. gg
7. The fixes shown in the ticket are pretty lame. (I've fixed these already, and added one they missed.)
8. I'm sick and tired and burned out and just can't bring myself to care. I'm only doing this so i don't get fired.
9. Why not have the person who screwed this up fix it? Did they quit? I mean, I wouldn't blame them.

Why must everything this company does be so infuriatingly complicated?

try {
…..
} catch {
// this would never happen
}

and then it happened

fucking always print something when you catch exceptions

Start working on ticket
Looks at code
WTF is the shit?
Open devRant to rant
1.5 hours later
what was I doing?