Our github->slack subscription breaks every few months, they never acknowledged it before. At this point we have a doc with the list of repos and settings, whenever someone notices that things are awfully quiet we just go through it and resubscribe.
I've been running GitLab internally on k8s for 6 years, it handles code, CI, security scans, build artifacts, helm charts, etc. It runs a nightly backup to a GCS bucket.
Monthly upgrades are painless. Once a year the major versions (18 to 19, for example) bump external dependencies and we need about an hour on it.
I've been using GitHub for other projects and for the life of me I can't see a single area where its better. Actions is worse without versioned and self documenting components, there's no concept of a project hierarchy or inherited permissions, even simple things like setting up deploy keys are more annoying than they need to be.
I can't speak for GitLab.com - I've never used it.
I saw this show up in RSS feed on Slack before here. Interesting, posted a message about it.
Not 2 minutes later, a coworker sent a message saying they got a message: their repository messages couldn't be sent, because the user is no longer authorized. The coworker was worried that they might be fired.
Alas, this economy is a terrible time for one business's fuckups to cause worry about people being fired. That's a lot of stress, man!
If only it were measurable in dollars, then we could sue Microsoft for damages. Maybe then Microsoft might stop producing slop. Ahh, wait. Who am I kidding? No, of course that won't cause Microsoft to stop producing slop.
When will the industry acknowledge that unreviewed vibe coding is not acceptable? The term itself is an offense to common sense. It should not have been given any legitimacy.
I blame the one who coined it -- for having created an entire career based on vibes, namely vibe driving, vibe neural networking, and finally vibe coding -- none of them work.
21 comments
[ 4.3 ms ] story [ 43.3 ms ] threadUtter degradation.
Our github->slack subscription breaks every few months, they never acknowledged it before. At this point we have a doc with the list of repos and settings, whenever someone notices that things are awfully quiet we just go through it and resubscribe.
Monthly upgrades are painless. Once a year the major versions (18 to 19, for example) bump external dependencies and we need about an hour on it.
I've been using GitHub for other projects and for the life of me I can't see a single area where its better. Actions is worse without versioned and self documenting components, there's no concept of a project hierarchy or inherited permissions, even simple things like setting up deploy keys are more annoying than they need to be.
I can't speak for GitLab.com - I've never used it.
Not 2 minutes later, a coworker sent a message saying they got a message: their repository messages couldn't be sent, because the user is no longer authorized. The coworker was worried that they might be fired.
Alas, this economy is a terrible time for one business's fuckups to cause worry about people being fired. That's a lot of stress, man!
If only it were measurable in dollars, then we could sue Microsoft for damages. Maybe then Microsoft might stop producing slop. Ahh, wait. Who am I kidding? No, of course that won't cause Microsoft to stop producing slop.
Github is making engineers more productive by turning off distracting fake work tools
I blame the one who coined it -- for having created an entire career based on vibes, namely vibe driving, vibe neural networking, and finally vibe coding -- none of them work.
GitHub's reputation has been long overcooked and you are better off self-hosting and you would have better up time than GitHub.
[0] https://news.ycombinator.com/item?id=48293202
Everything has an expiration date it seems. I assumed I just missed a reminder email or message.