Facebook be like
We put react-dom in your react so you can dom while you react and we also put react-native in your react so you can native while you react but we also put react-native-web in your react so you can dom while you native while you react

Honestly, I think this one is yet to come for me.

I've had a few bad experiences, but the worst ones are the ones where I couldn't find the time or brain to get some work done properly and therefore did bare minimum, so I basically was driven to shame because my teammates did almost everything.

Second to that, are times where I had to go through drama because teammates were absolutely incompetent or power hungry or inflexible.

Otherwise, it's "live and let die".

Note: I use "teammate" in general sense, equaling "coworker", "colleague", "the guy who's supposed to give me details or access" and "those in on the project" in this rant.

I applied to Amazon recently not really thinking about it I was just bored. Dropped my CV and I was asked to fill in why would I want to work in that position. I un-ironically put “It sounds like a lot of fun”, got rejected instantly then got an unrelated message from an Amazon recruiter from another division inviting me to apply, rejected it because it didn’t sound as fun.

I’m an honest bloke I just want to have fun.

Work smart, but not too smart.

Fuck you, I Quit

My son has started learning javascript at school, but he is complaining that all the $ signs are ugly! Yep, they're teaching the kids with jquery.

I don't know whether to laugh or cry 😱😱😱

Started a new job as a senior dev but with a framework I've never worked with and I just feel like I'm slow AF and just not qualified for the job. I'm sure it doesn't help that I'm greiving my dog that passed last Tuesday.

Send help..

The project we're currently working on:

- an angular codebase that's broken beyond recognition - nothing's working as it should

- user stories are estimated in hours, but estimations are treated as hard facts. Since the app is so broken, everything takes longer than usual and it's almost impossible to consider every potential hardship during refinements, therefore, we constantly need more time than we have estimated

- retrospectives (intentional plural here, since one time isn't enough) are used to discuss why we cannot manage to finish tickets within the estimations

- the design was made beforehand and is extremely inconsistent and inaccessible

- if you open a new ticket, you need to add a reason for why this ticket is needed - in addition to the ticket description..

- The moment you move a ticket to QA, the "Scrum Master" breathes down your neck, shoving new tickets in your face. Despite having to finish up the other two you're still working on

- multiple teams are working on the application, but - of course - communication is overrated.

I could go on, but I'm too tired..
We were supposed to help the client for a couple of months - we're close to a year now and still nowhere near done.