When you have 2+ separately scaling services (not HTTP) that need to communicate which each other, what do you do?

I'm leaning on putting Redis in the middle since it's mostly seeding data once per login, but I'm curious about opinions/alternative solutions (one creates a session the other reads the info)

People always complain about node_modules, at least it works most of the time, unlike god-damn python AI packages. I can't install https://github.com/shashikg/... because for some inane reason it requires a LLVM wrapper that in turn wants to compile LLVM manually. Not just manually YOU, the filthy dev that wants to use this holy library, must go and compile it yourself. And don't you forget to apply the holy patches.

God the code in AI projects always sucks - last time I looked at voice gen it required me to figure out what the fuck it was doing and go hunt down the libraries manually and still have to vendor in half the library because they used a library that had a minor migration but was 2 major versions behind or similar issue.

Why do science bros write such shit code that always wants to reach into things completely unnecessarily. Just write your shit properly.

Is this why they always have docker image...

Seeing a commit come past that includes an env variable for the backend named so that it will also get sent to the frontend (PUBLIC_*)...

Someone broke boost and modules, at least I managed to make a workaround but come on

Does anyone else ever drink too strong coffee in one go because they're tired only to get a headache and still feel 10 years younger

Anyone here ever add hardcoded sentry environment names, no I don't mean hardcoded names, limit the allowed ones? (e.g. not "dev" but "Dev")

Am I the silly one that realized that this is probably not a good way of handling it and created a PR to remove the check?

That moment when you can re-use code you wrote years ago, and it still just works

Anyone in NL have any good suggestions for finding job? Currently, I'm working at a software house doing fullstack (node + python) + mobile (android + react-native 🤮), generally one of the 2 categories per project. I do have ~10 years of experience. Currently, I'm all the way at the German border, I'm up for moving, especially if it gets me near people I can actually talk tech to (even to another country, but I only know Dutch and English fluently).

I do get offers on LinkedIn with one semi-success, but it came with several strings attached (e.g. can't find a new job with in 80 km kind of stuff).
Game dev has always been a hobby-wanna-go-pro thing for me, so I want those to be excluded from any type of “you made this in your free time, well, it's ours now” contracts.

Part of me wants to go into the game's industry because that's what I've always wanted (it just didn't exist back where I lived outside of gambling/shitty mobile games). I'm crazy enough to like C++ but with the current toxic culture in the game's industry, I wish to avoid it at the same time (+ just being exhausted all the time makes me think I wouldn't be able to keep up in the beginning).

Which makes me think I should rather go for “saving for the future” but the passion I had to just sit and programming seems to have 404ed🥲

My mind has been Ouroborosing on which way to go unfortunately as well

I moved back a couple of years ago largely unplanned timing wise, for a couple of reasons (safety and family mostly, the whole reason/process would take a while to explain). Which means I couldn't start to get things organised until now, including re-doing my driving license since I'm not allowed to convert it since I missed out on the 30% ruling (and my “old” country's license isn't good enough).

How long before game UI/HUDs will be implemented using HTML/electron/some other shiny web tech to make cross-platform easier? As cursed as it is, it really it's one of the few “complete” packages when it comes to dealing with UI that I'm aware of

Need to work on GitHub CI action that wraps a terraform deploy (previous teams deploy setup that they would run from inside a docker compose setup locally). Working directly on main and get moaned at (definitely consider the moan reasonable) when it was originally being duct taped together. It's scrappy and doesn't have all the repo rules that other repos have set up, but it's stable, and I need to move onto “actual” requirements.

Several months later, I'm still the only “active” maintainer (it's been stable since then and hasn't needed any changes).

Have to do a hotfix experiment after adding support for a new bucket, put the changes in a PR and merge (since it has to be on main, and I'm the only one who maintains it, and if it's truly deploy change related that is the only thing that changed)

Come back to the PRs at the end of the day after discovering it's just a change to django storage, and it turns out a colleague who is tangentially related to the project dropped a comment. He's complaining about the lack of a description, the lack of a ticket and “skipping” the review process.

I, too, would have liked all that, but the damn code needs to be merged so I can check that it was that MFer. Sorry, I expected you to be able to deal with a “vague” 10 contiguous lines of iam config values, ignore the immediately following PR that reverts this revert and the preceding one adds a bucket. Sorry, that the title saying that this is a revert isn't enough of a description for you. Sorry that the other dev that told me about it didn't create a ticket. Sorry that I didn't immediately do overtime to update all the PRs and magically conjure up someone who is available to review them. But hey now that's evening and I have time to get back to going through the PRs again I can see your indignant comment which I wasn't notified about since the PR is fucking closed.

Now that I have had time to go through and see your comment, message you to let you know that commenting on a closed PR is screaming into the void and updated the PRs I can get back to what I was supposed to do today. Which is dealing with streaming data into S3. Hope you had a good day in your Clojure tower with your hired PR person (yes a person to review his PRs).

Not having to deal with your comment would have saved me an hour+.

Getting real tired of the “act like product” when it comes to fixing bugs/any polishing that isn't exploding in prod and even then. Sometimes I really wish I could refuse people from messaging me to fix an issue and can only communicate by tickets 🙄 to avoid these problems. They've been told to create a ticket and assign it to me when there is an issue, and even then, I tend to fix the issue before they get to it. I can't wait until next friday…

Anyway /rant keep up the good work in keeping quality up :D

Why do PMs always think that comments/commit messages > the actual code?

If I need to know why it's coded that way, I need to check the code.

I get you want to know what's going on, but seriously, don't make me rewrite the code in English. You already know the ticket it's for and have the summary as the PR message (especially for code that the character changes can be counted on 1 hand)

PM tells me to merge (large feature) work that's heavily under WIP.

In that is a performance optimisation he instructed (with an aggressive DM) me to stop looking at even though it's a concern for larger clients that I had to fix before as it's "unnecessary" - thought whatever I'll leave the code as is then

I tell him him the PR is not ready yet, there is still a lot of clean up to and tests to write

Just do it

A ~week later "wow you write really selfish code like look at this"

Shows a wrapper class from the optimisation with 2 properties and getters and setters (and override some of super's properties). I explain to him why it's there, "that should have been a comment". I tell him I write detailed comments as part of my refinment process which he wanted me to stop.

This is after he tried to merge a release branch into main while sneaking in some "corrections" and I pointed out it breaks Dev.