this post was submitted on 03 May 2026
1065 points (98.6% liked)

Programmer Humor

31280 readers
1635 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

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] platypode@sh.itjust.works 57 points 3 days ago* (last edited 3 days ago) (5 children)

GitHub is where a lot of companies store their source code, so many software development workflows require it to be available. For a while it had fantastic uptime, but since Microslop started shoving vibe coded updates its reliability has cratered.

[–] ozymandias117@lemmy.world 19 points 3 days ago

GitHub manages not one, but TWO nines of availability.

Sometimes both nines are even in the front!

[–] saltesc@lemmy.world 10 points 3 days ago (1 children)

It's been Windows 11'd and the regular patches of downtime are just one of several new productivity-loss features to be rolled out.

Next; ads.

...no, wait, that's already happened.

Next; sponsors.

...actually, wait, that was kind of done.

Next; a bloat UI front-end to minimise the confusing layout. Subscription to opt out.

[–] balsoft@lemmy.ml 3 points 3 days ago

Nah, next is replacing all UI with a copilot prompt that always shits on your code and guilt-trips you when you try to look up some repo instead of just asking it to vibecode it for you.

[–] quantumvoid0@lemmus.org 9 points 3 days ago (3 children)

codeberg was down a few times in the past days, but i feel like its got more uptime than github atp

[–] Skullgrid@lemmy.world 14 points 3 days ago

At least codeberg isn't a billion dollar company

[–] tgxn@lemmy.tgxn.net 9 points 3 days ago

My self hosted gitlab instance has better uptime over the last 12 months than a billion-dollar SAAS product 🤣

[–] tempest@lemmy.ca 4 points 3 days ago* (last edited 3 days ago)

It's reliability was already not super great before the vibe coding hit.

It's mostly caused by them trying to migrate complicated legacy systems to azure. This type of work is already fraught with danger.

The vibe code just supercharges an already risky endeavor. The LLM code could be perfectly correct but the more dynamic a complicated system the more difficult it becomes to judge side effects of any one change.

The speed of change also means that experts in particular areas of the code base may find their mental model of the system to be out of date and incorrect faster than ever before. This is course also leads to the increased chance of mistakes or unintended side effects.