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: …

Interviewer: Hello I’m calling for your phone interview now

Dev: You’re about an hour early calling but I can accommodate

Interviewer: Well it’s more convenient for me to do it now

Dev: …Alrighty then.

Interviewer: So I am from HR 😇*pause for effect*

Dev: …

Interviewer: Um, typically candidates start the interview by thanking me for consideration for this role.

Dev: Your job description was very vague so I don’t really know what I would be thanking you for.

Interviewer: 😡. It’s me that’ll be determining whether or not to pass you on to The Management.

Dev: …The Management?

Interviewer: Yes 🤗.

Dev: I’m no longer interested *click*.

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

Dev: Why did you suddenly start adding random whitespace to the end of all of the files in your PRs?

Manager: IT’S NOT RANDOM!

Dev: ?

Manager: That’s a way I came up with for tracking my contributions. Every time I edit a file I add a line of whitespace at the bottom so it’s clear to everyone how much and how often I’ve contributed to the team. Although I haven’t been doing it this entire time so I had to make up for this by adding more to files that I *know* I’ve touched a bunch before. Just think! Especially with how big my PRs are compared to everyone else the tally of my contributions is going to get huge!

Dev: …

> 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.

It was only a while ago that I realized that “firm” was not quite “hard”, but also not “soft”, hence “firmware”, it's in between hardware and software.

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: ...

Military grade encryption: md5
Enterprise grade encryption: Base64

Interviewer: Hello my name is Alyssa from Sheeple and my pronouns are she/her

Dev: Oh yeah I saw that in your email

Interviewer: Ok well I am just letting you know they are still the same

Dev: Thanks for that.

Interviewer: What are your pronouns?

Dev: div/span

Interviewer: Sorry?

Dev: he/him

Interviewer: Oh…ok. Let me know if that changes.

Dev: I promise you it won’t

Interviewer: Well you never know!

Dev: …

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

The intern again. FUUUUUUUUUUUUUCK!!!!!!!!!!!

She's now done the Laravel course my manager bought her, so now she feels she's ready to tackle a real world project. Hahahaha.

Okay, I have a project set up: Replicate a simple existing website that only has a basic header, some picture thumbnails and a footer element using Laravel. I've already installed Statamic and everything she needs as dev dependencies and made a step-by-step README.md file for her to get the site running locally on her machine. I told her to replicate the home page HTML.

She didn't read the readme file after I've told her multiple times in the past to do so. She tries to run the Laravel application without running composer update and all the other commands I listed in the readme file, and doesn't read the fucking console errors she's getting. She cloned the project into another Laravel project and her files are a fucking mess.

I am sick and fucking tired of telling my manager that she is not suited for this industry, she's just costing the company money and wasting my fucking time. I have been unable to focus for the past month and a half because of her.

She can't even fucking Google the console errors she's getting, just hopping on MS Teams asking me to help without even trying to solve it on her own.

I want to cry. Fuck this company and its stupid CULTure.

Week 278: Most rage-inducing work experience — I’ve got a list saved! At least from the current circle of hell. I might post a few more under this tag later…

TicketA: Do this in locations a-e.
TicketB: Do this in locations e-h.
TicketC: Do this in locations i-k.
Root: There’s actually a-x, but okay. They’re all done.
Product: You didn’t address location e in ticket B! We can’t trust you to do your tickets right. Did you even test this?
Root: Did you check TicketA? It’s in TicketA.
Product guy: It was called out in TicketB! How did you miss it?!
Product guy: (Refuses to respond or speak to me, quite literally ever again.)
Product guy to everyone in private: Don’t trust Root. Don’t give her any tickets.
Product manager to boss: Root doesn’t complete her tickets! We can’t trust her. Don’t give her our tickets.
Product manager to TC: We can’t trust Root. Don’t give her our tickets.
TC: Nobody can trust you! Not even the execs! You need to rebuild your reputation.

Root: Asks coworker a simple question.
Root: Asks again.
Root: nudges them.
Root: Asks again.
Coworker: I’ll respond before tomorrow. (And doesn’t.)
Root: Asks again.
Root: Fine. I’ll figure it out in my own.
TC: Stop making it sound like you don’t have any support from the team!

Root: Asks four people about <feature> they all built.
Everyone: idk
Root: Okay, I’ll figure it out on my own.
TC: Stop making it sound like you don’t have any support from the team!

Root: Mentions multiple meetings to discuss ticket with <Person>.
TC: You called <Person> stupid and useless in front of the whole team! Go apologize!

Root: Tells TC something. Asks a simple question.
Root: Tells TC the same thing. Asks again.
TC: (No response for days.)
TC: Tells me the exact same thing publicly like it’s a revelation and I’m stupid for not knowing.
TC: You don’t communicate well!

Root: Asks who the end user of my ticket is.
Root: Asks Boss.
Root: Asks TC.
Root: Fine, I’ll build it for both.
Root: Asks again in PR.
TC: Derides; doesn’t answer.
Root: Asks again, clearly, with explanation.
TC: Copypastes the derision, still doesn’t answer.
Root: Asks boss.
Boss: Doesn’t answer.
Boss: You need to work on your communication skills.

Root: Mentions asking question about blocker to <Person> and not hearing back. Mentions following up later.
<Person>: Gets offended. Refuses to respond for weeks thereafter.

Root: Hey boss, there’s a ticket for a minor prod issue. Is that higher priority than my current ticket?
Root: Hey, should I switch tickets?
Root: Hey?
Root: … Okay, I’ll just keep on my current one.
Boss: You need to work on your priorities.

Everyone: (Endless circlejerking and drama and tattling)

hey there, long time no rant.
remember that manipulative, sociopathic angry manchild turdface PM, the kind that gives you a never ending rant inspiration? the one that got immortalized in like 90% of my rants?

well... it's time for the final update.
i decided to leave the team some months ago. my boss reacted very cool and supportive and suggested topics i could work on instead. when i told my colleague, he decided to leave the team at the same day. we both also complained at HR and added some papertrails about PM's shenanigans.
shortly after, another guy from the team quit and left the company, and i know that it was 100% because of this PM.
so, there were 2 devs left from originally 6 in PM's team.
some other people in the environment of this PM quit, one of his subordinates and someone from a greater project in which the PM's project was embedded.
after some internal investigations and discussions, the PM's team was completely kicked out of this greater project, since after ~ a year, this team was neither able to deliver anything useful nor to define what it actually was what they wanted to provide. instead, they actively blocked the project, solution finding and cooperation between teams. and this is quite very much PM's fault.

the final move came this month when PM got fired. i think, management finally realized that he is a total fraud who has no clue about the whole matter (neither what devices we build nor about software development). or management. or leadership. and that all he can do is produce hot air and bullshit people for some time to make them believe he knows something.
not sure how long he'll still be around, but i'm happy when i don't have to see his face ever again. i'm just sorry for the next company he'll be moving to...

Today, I dropped my 5900x while cleaning the computer. It's dead. pins got bent and one pin got loose.

I feel like crying... please send prayers and thoughts.

R.I.P AMD Ryzen 9 5900X 5900x 12 Cores 24 Threads 70 MB Cache 3.7 GHz up to 4.8 GHz. You will be missed.

Dev: This could be sooooo easily optimized...

Me: Uhm. Don't think so. What's your idea?

Dev: Just use threads.

Me: Nope. Problem requires 3 shared resources per process step, it won't be faster by threading. Shared resource will only lead to locking contention, decreasing performance.

Dev: I don't think that will happen. Can you PROOF to ME that this will happen?

Me: It was your suggestion, so you should proof me wrong. Nice try, but no thanks.

Dev: Yeah, but it's too slow and it should run faster.

Me: If you cannot find a better approach than the current one, it runs as fast as it can while providing correct results. That's not slow. That's just working as intended and designed.

Dev: Yeah, but it's still slow.

....

You know these conversations where you just wanna rip some people's face off, stick it in the shit hole they use to talk and toss them out of the window....

Yeah. Had those conversations today.

I like the modern entertainment industry's approach to tackling piracy.

Make shows/movies so horrible nobody wants to even pirate it.

Interviewer: Here is the interview challenge. Tell me what the expected output is. You have 5 minutes.

** 100 line class with 4 async methods that contain if/thens nested 4 layers deep that call each other and log things to the console

Dev: Ok wow this is a bit of a maze to work through but I’ll try my best.

** 1 minute later of reading through the code

Interviewer: One minute has elapsed. There is now 4 minutes remaining.

Dev: Actually could you please not interject with time updates like that while I’m reading code? It makes the challenge harder than necessary. Just letting me know when the time is up would be fine.

Interviewer: Ok.

** ~2 minutes later trying to comb through this spaghetti mess

Interviewer: What do you think are you getting close to figuring it out?

Dev: …

Reddit: Every developer eventually either goes insane or becomes a farmer.

Dev: …I hope I become a farmer

The nightmare continues.

Currently dealing with a code review from a “principal” dev (one step above senior), who is unironically called a “legendary dev” by some coworkers. It’s painfully obvious he didn’t read the code, and just started complaining and nitpicking.

It’s full of requests to do things that make absolutely no sense, and would make the code an unmaintainable mess.
• Ex: moving the logic and data collection from the module’s many callers into the module instead of just passing in the data.
• Ex: hiding api endpoint declarations by placing them in the module itself, and using magic instance variables to pass data to it. Basically: using global functions and variables instead of explicit declarations and calls.
• Ex: moving the logic to determine which api endpoint to use, for all callers, into the view.

More comments about methods being “too complex” (barely holds water) right next to comments saying “why are these separate? merge them together!”

Incredulously asking how many times I’m checking permissions and how ridiculous it all is. (The answer? Twice.)

Conflating my “permissions” param and method names with a supposedly forthcoming permissions system overhaul, and saying I shouldn’t use permissions because my code will all have to get rewritten. Even if that were true, and it’s likely not, the ticket still needs to use the current permissions. I can’t just ignore them because they might be rewritten someday.

Requests to revert some code cleanup because the reviewer thought the previous heavily-nested and uncommented versions (with code duplication) were easier to read. Unsurprisingly, he wrote them.

On the same ticket, my boss wants me to remove all styling and clientside validation, debouncing, and error messages from a form. Says “success” and “connection failed” messages are good enough. The form in question sends SMS and email using arbitrary user input for addresses. He also says it shouldn’t be denounced on the server, and doesn’t want me to bother checking permissions. Hello, spam!

Related: the legendary dev reviewer says he can’t think of a reason why we would want to disable the feature for consumers, so I should remove the consumer feature flag.

You can’t make this stuff up.

Business guy: hmmm, what do you think about getting the programmers to come to the office more often?
Me: uhhhh explain?
BG: feels like when working from home they might only give it their 90%, but in the office they'd do 100%.
Me: let's not talk about how you reached that conclusion for now. If you force them to come more often they will quit.
BG: what about the new people we want to hire?
Me: most jobs have full remote available, why would anyone pick us?
BG: hmmm. Btw next week we'll talk with some stakeholders about trying to get some outsource help. You know, for repetitive stuff that doesn't require in-house engineers.
Me: like what?
BG: you know, repetitive stuff

This is suffering. Is my only choice to tell the guy that he has no clue what he is talking about, should STFU, and let the technically capable people to handle themselves? As in, we already do but for some reason he still thinks he knows better than the people doing the god damn job? But if I do so, the salinity in his blood will bring other problems upon us.