sleiben

Thats pure gold. Thank you my friend!

Thank you

Looks really interesting, especially with the dashboards.

Just to validate an idea here: I’m using k8s (20+ services) and trying to stick to the 12factor design pattern by having all the baking/companion services, also like cron jobs deployed from within the service directory. Right now I’m using k8s cron services for cron jobs and log the steps and observe with DataDog. Using k8s cron services feels right somehow but the observability with DataDog not. So, would it make sense for me, to deploy a baking k8s web service running sidequest instead?

Same here. Especially for native app development with swift I had way better results and just sticked with Gemini-2.5-*

I’ve tried to order Oriana Fallacis The Rage and the Pride 2 years ago on Amazon (Germany). No chance to get it … felt to me like censorship back then.

I would assume their thought is, that it limits their creative spirit and in general is too technical. But they start (as 2 people teams) on figma a complete own design lib with a lot of variables and custom components which look the same like any other lib.

Worse than tobacco?

Encountered this too often in my career and had a lot of wtf moments debugging that «de-coupled» stuff others (and sometimes me) have left.

I decided to follow the «Wrong abstraction is worse than duplication» approach. Doing this for 5+ years now and did never regret it.

Sure, copy-pasta sucks but in comparison to over engineering it’s an acceptable price to pay.

100% with you here! Great arguments

edit: It also reminds me of men playing feminist and stepping (aggressively) up to protect women’s rights. I heard from my female colleagues that they hate this since it implies that women are like children and aren’t able or mature enough to speak up for themselves. So the «strong men» need now to protect them…

The «master» to «main» change was totally unnecessary and B.S. imho.

Even 15 years ago, when I started my professional journey (in Germany) there were a lot of people who were gay, trans and so on in the dev community … and nobody cared about it. We were all passioned about technologies and respected each other based on commitment/engagement/skill level. At the end most of the true full blood developers were always «special» and knew since their childhood that they were different from other children. I think that’s the reason why the embarrassment level was pretty low and people just wore the stuff they wanted, behaved like they wanted eg.

But of course that’s only my personal experience. I’m sure there are a lot of other stories out there to share.

We use the microservices architecture as a single team and don’t have any issues with this for many years. The key is to have a monorepo and stay consistent by following strict coding guidelines.

In my opinion it makes the backend way more resilient than a monolith.

Don’t kill me for this opinion please ;)

You‘re probably not the target group. It’s an open source project (in comparison to the MacOS walled garden) and I think that especially your 3rd question is disrespectful. In general your comment reads like a rant against the open source philosophy to me and is attacking/demotivating people who spend their spare time to create free software. Instead of attacking OSS creators one should give kudos and encourage them to go on. … just my 5 cents.