Snek is back up https://molodetz.online/web.html

Isn't it awesome when someone's "bugfix" causes new bugs which prompt "bugfixes" for the bugfixes in the same merge request?

Urgh, I can't get going on Mondays. Even in a calm environment and with a really nice project I can't get focused on my task.
What's wrong with me?

The mods are sleeping now. Let's party!

New Job new me.

Looks like it's pure chaos. Randomly turning on aws features until things work. Lots of money down the drain.

Oh well. It's a job.

Ths is a rant:

My client codebase is a mess:
- Node version is not set, but it is "told to set it up at X version". They don't want to set it fixed because, and I quote, "it is too much of a nuisance.

- Backend has not a single fucking log, beside the mandatory error in the catch of each controller, and it states "error": error.

- Backend again: why the fuck you want typescript if all the fucking codebase uses 'any'. But the orm is sequelized and it is typed... by zod classes that are only there to check the body on the endpoints.

- Frontend is a gargantuan piece of shit with one.big state with all fucking stucl there cause someone started to do that and they just keep the snowball... touching one of the utterly big and bloated compoments its in itself an act of faith. The thing is so clusterfuck that we have some api calls duplicated like 3 or 5 times...

I feel like my dev brain is being rotten each day a bit more...

DirectX users are psychos.

There is always something, innit? Some "data scientist" in waaaaaay over his head complained to my teammate that the piece of code she wrote was faulty in some overly weird edge case that only occurred to him, but was never actually seen in practice. But the jerk complained in a very, very annoying and entitled and pushy way.
He brought my girl almost to tears.
Now, im not exactly the most delicate in my manners, but One. Doesn't. Mess. With. My. Team.
I just sent an email to his manager that from this day forward, every single piece of code anyone on his entire team requests will be tested to the entirety of the possible inputs. They had asked for some delay measurement tool. I've locked my cluster for... nineteen hours now, just computing the complete list of test parameters. 3.1Gb of parquet files with possible input combinations. Or about 1200 USD coming out of their budget *just to _test_ this one fucking function*. And about a week delays for the tests to complete.
And a chip on my shoulder.

P.S. the data science team manager is actually nice and all, and he is also at the end of his patience with his jerk of a teammate. Someone is getting a bloody poor quarterly review.

How many devs are also really into creating music?

Oh man, I kinda start to regret changing this job. Currently I'm employed at as a contractor through a third firm but I work pretty much full time. The initial deal between the client & the consultancy firm is that I would start there after 1 year

cons:
- My previous wage was more optimized and I now earn a €25 more per month after taxes despite earning €600 more before taxes. I did not see the calculations after taxes before starting.
- It seems since I started after July, I don't get the end of year bonus (thus making less money after taxes in 2025 despite switching jobs)
- My colleagues at the new job are friendly but they barely talk even during lunch. And if they do, it's about Pokémon trading cards
- One day work-from-home instead of 3 (I thought it would be great change since my social life is quite bad lol)
- Company kinda glorified that I could learn a lot from a very senior developer but after 4 months, I still haven't had the chance to work with him and there seems to be no plan. As of today, I was always the most senior FE dev in every workplace.*
- No agile development (I thought this was a plus in the start but kinda miss it)
- No project manager or product owner
- Unreleastic deadlines with a visible backlash when failed
- No project specifications to combat unclear expectations and when creating one, it suffers from feature creep.
- Senior dev is a "yes, we will do that by the deadline"-man
- No shops in walking distance
- Shorter lunch breaks
- People can easily see my screen so can't really do reddit
- smaller dev-team: 3 vs 11 (HR said 10 people in the IT-department, it is true but I did understand it as 7-8 devs at least but nope)
- More time tracking
- Technically a 1 year probation period so the legal protection would reset again after I swap jobs officially (like if I get fired next year, I don't have to be paid off for an extra few weeks)
- No testing department
- Was lied to about being able to do some backend work (they said 75% FE, 25% BE work, now 90% FE - 10% design)
- Was lied about the existence of the technical specifications of a project (one was very well, the one with the deadline does not exist, one more was simply not needed)
- more office noise
- no relax room (even when the one at my previous job was only used once a month)
- bus factor of 1

pros:
+ At least the workplace is a 10min drive instead of 25-55 min previously
+ Less meetings
+ free fruit & unhealthy snacks in the office (refilled Tuesday but gone by Friday)
+ AI is not being glorified
+ more privacy concerned (even when this dataset needs less privacy regulations)
+ Working charging ports for EV
+ fresh code base
+ The big boss is chill
+ design freedom
+ Less people are getting fired
+ Less responsibility so far but that will change
+ We stop one hour earlier on Fridays (technically still paid for now)
+ Actually work I could do here (if it is not blocked by the lack of existence of the backend)

Same shit, different company:
- Lack of clear communication with the other developer. (previous company, it was great to work with a few remote developers but sucky to work with an other remote dev, now there is a lack of communication with a dev that sitting across of me)
- No documentation
- No project specifications
- Both companies feel a bit immature
- Both projects are a bit uninteresting
- Still a feeling of not being satisfied with the job

If I go fulltime at the client:
- I would lose 6 extra holiday days (26 vs 32) since the work contract would swap from 40 hours to 39 and thus I would lose 'overtime day' per 2 months.
- The salary would become slightly less optimized
- They don't have to pay the consultancy fee that I do not see so I can ask for a big raise & have more leverage as the only FE dev.

I know I did ignore some red flags since I really wanted a job switch. I thought the lack of agile would be compensated by existence of technical documentation and clearer requirements.

\* not fully true but any senior FE dev either sucked at communication (for example; I had PRs open for 9 months unreviewed) or got fired after 2 months. I had one senior dev that didn't really teach me anything but did learn indirectly from him.

Might delete the rant later

Countless times, the managerial leeches tried to get rid of us labourers. They tried with WYSIWYG. They tried with No-code bullshit. Now they're trying with IA.

Over and over again, they will fail. And if only they could realize before crashing the world economy AGAIN, that would be fucking great

OMG, the macOS 26 version of Contacts. I swear the Xcode team wrote it. It is a completely new GUI that is a hot mess of over-colored pixels that swim around with an interface that makes you want to spank the developer's mother.

The graphical update is slower than shit between cards because OMG, it's all about looks and who cares about performance.

Clicking between contacts results in the buttons doing this shaky-shimmer thing that looks more like someone shaking their dick at the end of a good piss.

(ha, now you will think of that every time it does that stupid shimmer thing on your Mac)

I've finally been rejected today for a job that I applied to roughly 10 months ago.

---

I wonder if the backend will be pushed to the git repo today by the senior dev or if it will be possible to run locally.

Seen it done wrong so many times makes me wonder what it may look like if done right. What are your thoughts on "micro-services" and maybe specifically "AWS Lambdas"?

I said it many times, I'll say it again: this advent of AI is the beginning of the IT seniors' golden age

HR positions are being replaced by AI [I know it for a fact]

Junior positions are getting replaced by ai in LT as well now.

I wonder.. Where will they get sr devs after 5-7 years from now, if noone new can get into the field any more 😁 ofc rehire from others.. But how will you attract them? With high salaries ofc :) I foresee a salary growth in IT in the next 5 years :)

(Double rant day)

So I had a little problem and I thought, why not test a new AI tool on it.
The problem: git-rebase, but copy tags. Example: if you apply a commit with the tag G2, create a tag called G2' in the new commit.
The tool: Perplexity. I had heard good things about it.

TL;DR: Had to do it myself.

1st it told me to do it by hand.
"What about --exec?"
Oh yeah, call a bash script to do it.
"What would the script look like...?"
Ooh, like this, look.
"Ok, I see. Can we just put it all in the command? The script can be simplified, only one tag per commit that has any, and forget the echo statements."
Yeah definitely, here you are.
"It's still complex, the script can be simplified."
Yes, I can remove some parts. Now.

Great, so now I had a single command, that would do what I wanted, right?
Nope.
- It referenced files that didn't exist.
- It had badly escaped characters in the bash string.
- And after fixing that*, for some reason Git didn't accept it, even if it was well formatted, and the AI never told me that could happen.
* Mind you, fixing that took some time of reading documentation of git commands and options I never used, snooping around what was accessible in Git's internals during a rebase, rewriting the bash lines... like, I didn't even use any part of the AI solution.

Evidently Git's very hard even for AI lol
It's neither artificial nor intelligent, it's trash. 0 stars.
(I know Perplexity is not "an AI", it was most probably using ChatGPT. Can't bother to see how to check.)
Maybe I was using it wrong??

reading a book on emotional intelligence and it's quite dystopian that it's funny. I got the name of it from a highly sensitive person book praising it (so you'd think they would be sensitive and empathetic, and be able to perspective-take and all that jazz)... he also keeps talking about how cognitive capability doesn't mean better social skills but better social skills means better cognitive ability. lol

---

> One of the more surprising job arenas where emotional intelligence makes a competitive difference is computer programming, where the rate at which the top 10 percent exceed average performers in producing effective programs is 320 percent. And those rare superstars, in the top 1 percent of programmers, produce a boggling 1,272 percent more than the average.9
“It’s not just computing skills that set apart the stars, but teamwork,” says Spencer. “The very best are willing to stay late to help their colleagues finish a project, or to share shortcuts they discover rather than keep them to themselves. They don’t compete—they collaborate.”

---

> After hearing me give a talk on emotional intelligence, the CEO of a company—one of the ten largest in its market—told me in confidence about why, instead of grooming his chief operating officer of many years to take his place as CEO, he fired him: “He was extraordinarily talented, brilliant conceptually, a very powerful mind. He was great on the computer, knew the numbers up, down, and backward. That’s how he got to be chief operating officer.“But he was not a brilliant leader, not even particularly likable. He was often brutally acerbic. In groups he was socially awkward; he had no social graces, or even a social life. At forty-five, he had nobody he was close to, no friends. He worked all the time. He was one-dimensional; that’s why I finally let him go.
“But,” the CEO added, “if he could have done just five percent of what you’re talking about, he’d still be here.”

---

so you knew he was smart because he collaborated / taught you how he thought... and this isn't the only excerpt where the author praises overtime, commitment, etc. but then the guy gets fired for having no friends. lol

Things that we should collectively refuse to do while job searching:

- AI interviews and live coding sessions
- Working with recruiters who don't know shit about tech
- "What is your Github" (I don't use github, retard, they're microsoft. Beside, I don't have a strong portefolio because I had an actual job, you should try it).

Have you ever asked yourself: "Do I really want to be a dev?". Maybe one wants to be an artist, y'know.

https://vibe-coded.lol/