And so it happened.
My company installed app-operated locks in the office.
Today the internet went down during the night and nobody could get in to even get their laptops to work from home :))))
Brilliant move and there's certainly not been anybody who could have predicted that.

Turns out my colleagues don't understand how useMemo works. They would try to memoize a value and then, in the dependency array, use an object that gets rebuilt on every rerender.
Good job, guys. I wonder how many silent infinite loops we have because of that shit.

I'm fixing our wrapper for API calls. The typescript for it was nice and simple, except that halfway through it casted almost everything as `any` and then hand-typed the expected return type :)))

Took me almost two weeks to work through that wretched piece of code, I managed to get the types actually correct... but now it started to catch incorrect calls, so I have to go through quite a lot of files to fix the references. But the worst part?

Now it breaks unit tests.
Turns out, multiple frontend unit tests DID NOT MOCK API CALLS AT FUCKJNG ALL HGGHGGHHHHHH. I WONDER WHY THE TESTS WERE TAKING SO FUCKING LONG TO RUN. I AM FUCKING FROTHING AT MOUTH AND I MIGHT NEED TO BE PUT DOWN OR I WILL START BITING PEOPLE

There is a particular power move when you take someone's shit code, refactor it to make it faster, safer and more readable and then request a review from them on your PR. "See how I dunked on you, bitch. This is what superiority is about." And at the same time you can be perfectly polite with "oh you know this part of the code well, I wouldn't want to break anything there" with the "bitch" just strongly implied.

I'm working with a nice piece of code written 6 years ago by somebody who isn't in the company anymore and only the fact that they live on the other side of the continent prevents me from physically strangling them.

They must have thought that they were very smart trying to use JavaScript as a functional language. A shitload of library-specific decorators that ultimately don't do shit except for raising the cognitive load of anybody who hasn't worked with it before. Why the fuck did you use 'curry' in a function that then is never called in a functional manner? Because fuck me, go check the documentation of ramda because you obviously have too much time at work if you ask questions, just to learn fuck all.

It fascinates me how people take this steaming pile of shit that is JavaScript and then try to work against all its design assumptions to create something that is even more slimy, disgusting and smelly. It shows a radical misunderstanding of what you're even working with.

Take shit, add straw and you might have a docent construction material. Take shit, sprinkle it with chilli and try to eat it and it's just hot shit. But at least you will make everyone else try to find out why the fuck is that chilli in there because why would you expect it there. I'm a coprologist, not a cook.

Running npx google-artifactregistry-auth in three simple steps:

1. Run npx google-artifactregistry-auth
2. Interrupt the process because it will inevitably get stuck on retrieving credentials
3. Run npx google-artifactregistry-auth

Then to install packages you need just 3 simple steps!
1. Run npm i
2. Interrupt when it gets stuck on reify
3. Run npm i

My company just installed app-operated locks in all doors. Let's say that I have a hard time taking security policies now.

Code freeze is such an idiotic concept. What year do we have? Just make a goddamn release branch and do your codefreezy things there. Why the fuck would we stop the entire development just because you can't figure out git?

I swear sometimes debugging a new piece of code feels like waddling through a sewer, trying to find a clog. You are unsure where you are, everything smells, there are decades of old shit piled up by the sides and once you start tugging it turns out the entire sewer settled onto it and it's as much of a clog as it is a structural element now.

Ah yes of course

I fucking hate it when apps are not named the same way as the fucking product or company. "Connect" app. Connect fucking what? "Mobile bank". Let me try to search for it using the name of my bank. Haha, oops, I forgot I should rather go fuck myself. MusicCast. You're fucking Yamaha and if I can't find you at Y then gods help me.

til: Jiraporn is a legit Thai name and not only what overly horny project managers do.

"Front end developers" who don't understand the cascade are my favourite thing. Just use BEM dude, you don't need some fucking scoped components with dynamically evaluated CSS-in-JS.

I swear two thirds of job offers now are in insurance and banking. And if that doesn't spell "incoming crash" for you then idk. We're in for some fun times.

The best thing about having a split keyboard is that I can hold a bowl of soup in the middle

It's not "fintech", it's "trying to get around the regulations imposed on banks by pretending you're not a bank" and it's not "insuretech", it's "scam".

I love how we're living in a literal climate apocalypse and we're sitting here writing funny words that help the line go up.
In other news, the easiest jobs to get to now in frontend are gambling companies.

We are now in a full swing enshittification of the entire internet. Almost no companies are interested in providing any value, it's the phase of securing the position between those that provide value and clients - and just collecting rents. Capture enough of the market, milk the product and the client, turn the service into shit while charging progressively more until it all burns and crashes. And then, well, pass go, collect $200, rinse and repeat.

I fucking hate it that "front end developer" came to mean "data flow for react engineer". It seems most frontenders now don't understand shit about HTML and its standards, don't know anything about basic accessibility and proper content structuring.

It's even worse with the styling. Cascade? The fuck is cascade? Scope everything! And, of course, write that CSS as a JS object because how else. Fluid typography? If by fluid you mean 16px, sure. Any more advanced techniques? Lol forget you're getting rounded boxes with a shadow and you're gonna like them.

But yeah, I'm glad they're overengineering Redux again because their reactivity model is fundamentally broken. That's exactly what """frontend""" should be about.

God I miss Stack Overflow Jobs. Put tech you want to work with, put tech you don't want to work with, get relevant results. Now? Search "frontend" in LinkedIn and you're getting "sugar production quality assurance". Fuck that noise.

What the fuck is up with job ads for "software engineer" that don't list the tech stack or even the actual product you'd be working on. I get it that it's some shitty external HR companies but are they even trying?

Also half the fullstack positions that don't even list the front stack. "Looking for a backender that will also cobble together some mess for the front, we don't give a shit". And then half of professional software is virtually unusable.

I'm gonna have an interview that will include talking about php. Problem is, I haven't touched php in 5 years. What do I need to know to sound like I know what I'm talking about? "Mmm yes I really like Laravel dependency injection, it makes managing dependencies so much easier"?

What the fuck are time zones

The entire react "return of a useEffect is its cleanup" is one of the most retarded design decisions ever. Hello, you can't have async functions. Do you want to return early and still have a cleanup? Good luck, hope you like debugging. Who the fuck came up with this idea and what was it inspired by.

I got relegated to updating an old project. It takes just 35 lines to do what we can write as a single liner in the new one.

My career plans? I'm going to a psychiatrist in two weeks and I hope I will get a long term sick leave due to mental health.

Why does React have dependency arrays in all hooks if they basically always need to be filled with every single dependency? Just figure this shit out yourself, eslint can do this, why can't react?

How the fuck are lifts programmed? Two lifts in a shaft, one at level 0, the other at level 4, I call it from level -1. Which one comes? You bet your ass it's the one from lvl 4. Is it Math.random()?

I've been working with JavaScript for nearly a decade now and yet I still get fooled from time to time by the fact that 0 == false.

React's useMemo, useCallback are just sad attempts at patching up a bad reactivity model. We should seriously move on from this hot pile of garbage.