Isn’t that the definition of a race condition, though? In this case, the builds are racing and your success is tied to the builds happening to happen at the right times.

Or do you mean “builds 1 and 2 kick off at the same time, but build 1 fails unless build 2 is done. If you run it twice, build 2 does “no change” and you’re fine”?

Then that’s legit.

AKA - the test suites at half the companies I’ve worked. Except they use a loop with retries as well

Because as we learned in our lemmy growing pains, large-scale federation is a challenge that requires a fairly concerted effort and then doesn’t always succeed very well.

People still (rightly) have tons of complaints about lemmy failing to do things as well as reddit did. It has some huge upsides (no center ownership) but it’s a challenge. Now imagine the much-smaller userbase. I knew everyone in the topics I frequented back in my forum days because there were that few people.

That was very rare back when I used forums. But similarly, at least every month I’d have a reply to a 1-2-year-old comment I left in reddit. It happens.

It’s also not easily recognizable as an aggregator when you go to subs/communities where there are zero or nearly zero links, and it’s all threads.

They’re honestly more like a hybrid between an aggregator and an oversimplified forum. Most subs I frequented feel like Delphi did back when I grew up.

I think it’s a matter of expertise. I am stuck dealing with people who write Javascript/Typescript like it’s C# because they’re C# senior devs. It’s not world-ending until issues of speed, scale, or other “why we use best practices” raise their ugly heads. Then it is world-ending. I can only help with so many design standards when you still see everything show up in a classes-and-subclasses mindset with hard-to-catch concurrency bugs. I actually caught a developer trying to spin up a child process to wait on a socket response.

So in FinTech, I can imagine it becomes a bigger deal faster.