Started at a new employer few days ago. It all started with:

'To become familiar with our tech stack and projects we've assigned some tickets to you, 'some' of these are tickets others weren't able to finish'.

The tickets (12):

Status: stuck
Added: 4 months ago
Notes: 12 (mostly negative)
Assigned and unassigned to different people 8 times

Devs: Hey, what should we do?

A:
provide our SDKs for download as easily as possible so that any potential customer can try it out and see how much better we are compared to our competitors?

Or…
B:
Should we lock our SDKs behind a login where the customer needs to create an account and enter the most amount of private information possible, just in case, then also require to create some security access tokens that he needs to configure in his app to have access to our service via the sdk and also hide all of the documentation behind a login which requires some permission based roles to access and also make the sdks closed source so that it’s a pain in the ass to debug and understand?

Marketing people:
B! Definitely B! Make sure to piss off and annoy our customers as much as humanly possible!

I currently have 5168 node_modules folders on my computer.
Not 5168 folders inside node_modules, but 5168 actual node_modules folders.

That's all. That's the rant.

Oh man, today just gets better and better...

Manager: * Creates ticket, which has a link to a shared pdf, with each page being a link to another ticket in our JIRA with unrelated bugs of what we are currently working on. *

fullStackClown: I'm closing this ticket and putting this feedback in the original ticket that I assigned to you to review days ago.

Manager: Rages like a little baby and removes my access to said shared pdf.

fullStackClown: Welp, looks like I'm done for the day! Cheers!

Based on a true story:

Me: Woah, I can't believe you wrote a test for such an edge case, you really take TDD seriously

... 1 minute later

Me: Woah, I can't believe this is the only test for the whole project

So far video game bosses only

Our dev server runs php 7.4

Our production servers run php 7.2

WTF is the point a
of auto-generated documentation. Some dude litterally thought it was a good idea to read the code and write the exact same shit differently. WTF IS THE POINT!?

Documentation takes work, sorry, stop being lazy.

So my three year old is at the size where lifting him up while he is kicking will result him hitting my balls. Really didn't need this today..

No, a 33 Page README is not the better choice.

Not for reading.
Not for writing.

Compared to a /Documentation/ folder
+ good overviews / links

Motherfucking YES!!!
I passed my final exam for my trade degree. Now I'm officially qualified as an IT-Administrator.

!rant Went shooting for the first time over the weekend. Was so proud of my grouping that I hung my target on the door to the garage on the side that faces the garage so if anyone breaks into my garage they have to see it before getting into the house. 😂

Reading Medium articles usually leaves me with more doubts than answers.

Wouldn't it be so funny if nobody replied to this weekly rant

Interviewer: Tell us about yourself.
Me: I was born at a very young age...

Totally going to say this when I interview next.

I got approved for my new apartment 🥳🥳🥳

Ok so our director decided to try out google work space
Plugs in our organizations domain and emails etc
trial then expires
we now cant access our emails
cant login
cant do shit

I finally finished reading the goddamn book. 🥵

So we started using React with Polaris and Supabase and Vite and guess which one doesnt have very good documentation, all of then. Kill me like a command window task

that really killed me today when i sat in the office

how good can you rant with your colleagues? i don't think i would survive long without this kind of therapy xD