Comment by californical

9 hours ago

If I own a restaurant and buy bread from a supplier — BreadHub.

And 99% of the bread that I get is good but 1% of the loaves, they forgot to add flour. Consistently, for years, they always have loaves missing a key ingredient that I still end up paying for.

I can be pretty sure that BreadHub have a pretty major internal issue, and should probably be questioning their competence, regardless of their “scale”, and without any knowledge of the “problems they’re solving”

I’m not saying users don’t have a right to be pissed or aren’t justified in looking at other options.

I’m saying that GH is operating at a huge scale with (probably) lots of technical debt and a forced migration to new infrastructure.

I would be (and am) highly critical of leadership. I’m not going to make strong assertions about ICs without knowing their context. I’ve worked at a company with a sterling reputation for engineering excellence where brilliant ICs were kneecapped by poor leadership.

I think a lot of us, at one point or another in our careers, have worked with potato leadership that can be short-sighted or political. It isn’t a comment on the engineers.

  • I mean, the leadership brought it on themselves. For a few years they encouraged sloperating Copilot. Before that, they were encouraging Github Actions usage.

    Now the scale problems they're facing is because of those 2 actions of theirs. They didn't have to encourage such growth to turn a profit, and they still don't have to provide gratis services to slopware bots providing 0 value for society.

I don't think this is an apt analogy. The bread makeup is still there, as far as I'm aware, no users have lost any data or are missing "key" ingredients.

An outage is more like a shipping issue with the supplier, if it's owned wholly by them.

  • Are you saying the dough is fine but 1% of the batch wasn't cooked? Or rather, that 1% of batches isn't cooked, taking your entire downstream activity down until a new batch arrives?