dandi8

That’s not creepy or weird, that’s horrifying.

Except “mass” is not useful by itself. It’s not a chair factory where more people equals faster delivery, just like 9 women won’t deliver a baby in a month. I wish companies understood this.

I think the answer to this is lack of adoption.

Ok, but the comment thread is about people preferring Bluesky to Mastodon, hence my confusion.

Isn’t the format literally just Twitter?

Are you complaining that older versions of Java don’t have the features of newer versions of Java…?

For me, as primarily a backend dev, the argument was that it’s a framework, unlike React, so you get an everything-in-one solution which is quite easy to setup and use.

Given that Google still hasn’t killed this one yet, it’s also a mature platform with plenty of articles online on how to use it.

IIRC the license was also better than React’s, at least last time I checked.

Not sure on what the landscape looks like today, but when I was making the choice, the internet didn’t seem to consider other solutions to be competitive with either React or Angular.

Over my dead body.

FYI there’s a fully playable unofficial port for Jak 1 and 2, and they’re working on the 3rd one: https://opengoal.dev/

Pegasus?

I’m fairly sure the crouch jump is part of the Half-Life 1 tutorial level.

Isn’t the entire point of federation to be able to do what you’re describing?

First part of the article sounds like what I’d expect.

The second part makes me wonder if this research was sponsored by some company which provides “Prompt Engineering” training.

Hopefully this will enrage the users enough to go and actually vote against Trump.

Does this really make it any less worthy of criticism, though…?

Interesting! Out of curiosity, what is the source? Is there a breakdown per role?

It’s no more a risk than throwing more developers at it when they’re not needed.

“Too many devs“ can, and often is, a significant bottleneck in and of itself. The codebase may simply not be big enough to fit more.

Besides, I still don’t see what all those additional engineers would actually be doing. “Responding to incidents” presupposes a large number of incidents. In other words, the assumption is that the application will be buggy, or insecure enough, that 30 engineers will not be enough to apply the duct tape. I stand by the claim that an application adhering to modern standards and practices will not have as many bugs or security breaches, and therefore 30 engineers sounds like a completely reasonable amount.

I have no idea why you’re even bringing up OT. We’re not talking about PLCs or scientific equipment here, we’re talking about glorified web apps.

Web apps that need to be secure and highly available, for sure, but web apps all the same. It’s mainly just a messenger app, after all.

So cool that you got to work with teams of devs that where able to do that.

Just because, as I assume from this quote, you weren’t able to work with teams like that, does not mean that there are no teams like that, or that Telegram doesn’t operate that way. Following modern practices, complex projects can be successfully done by relatively small teams. Yes, a lot of projects are not run that way, but that just means that it’s all the more a valid point of pride for Telegram.

I have never, in my decade as a software dev, seen a role dedicated to “making sure unit tests stay functional, meet standards and fixing them”. That is the developer’s job, and the job of the code review.

The tests must be up to standards and functional before the functionality they’re testing gets merged into main. Otherwise, yes, you may actually need hundreds of engineers just to keep your application somewhat functional.

Finally, 30 engineers can be a vast breadth of knowledge.

Even if you have a full-time role for continuously auditing the infrastructure (which I would say is the responsibility of either a security officer or a devops engineer), you still didn’t show how that needs a 15-person team, and an otherwise-untouched infrastructure should just keep on working (barring sabotage), unless someone really messed something up.

If CI builds or deployments keep randomly failing at your place, that’s not an inescapable reality, that’s just a symptom of bad software development practices.