Edit: seems like they fixed it, it works for me
this post was submitted on 05 Jun 2025
616 points (99.4% liked)
Programmer Humor
25139 readers
1361 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Reliance on external services to build and test code is absolutely braindead design
Not going to lie, that is hilarious. And forget red flags, you have a whole squadron of semaphores right there.
Like I said, braindead
Sometimes our internal CI tools break and I can't build either. I think GitHub actions syntax is actually valid in forgejo as well so I don't really think it's a problem.
It's not like internal build servers are 100% reliable, scaleable and cheap though. Personally I've found cloud based build tools to be just a better experience as a dev.
Jesus Christ, can you not even conceive of the idea of building on your own machine?
I'm talking about in a professional environment. You basically need a team to manage them and have a backlog of updates and fixes and requests from multiple dev teams. If you offload that to something cloud based that pretty much evaporates, apart from providing some shared workflows. And it's just generally a better experience as a dev team, at least in my experience it has been.
Well yeah strictly you don't, but the idea of having a single machine under someone's desk as a build server managed by one person where you have multiple dev teams fills me with horror! If that one person is off and the build server is down you're potentially dead in the water for a long time. Fine for small businesses that only have a handful of devs but problematic where you've multiple teams.
Yup, exactly this. Why waste resources internally when you can free up your own resources to do more productive work. There's also going to be some kind of SLA on an enterprise plan where you can get compensation if there's a service outage that lasts a long time. Can't really do that if it's self managed.
In a professional environment, I've never had remote-only build systems, with the exception of release signing of locked-down compiler licensing. Otherwise, there's always been a local option.
Edit: is my personal experience wrong somehow?
No, that's actually genius.
How else are you supposed to get random paid break-time, which the boss can't stop you from even if a crunch is going on?