dandi8

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.

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.

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

I just beat this level yesterday!

It becomes easy… Once you know what the tricks are supposed to be, which the game doesn’t tell you at all.

For me, these were the tips I needed:

1. There’s a dedicated button for burnout, which makes it super easy to do the 360
2. the slalom only counts if you do the pillars on one side of the garage BOTH WAYS
3. To do a backwards 180, drive backwards, then push one direction, then halfway through push the other direction.

Supposedly the PSX version also has a video in the options menu which shows you a dev completing the course, with button prompts on screen.

Oh, and there’s a cheat code in-game to skip this level entirely.

I’m really not overloaded, I have a very agile team and we usually don’t take more than we can manage.

But saying you can always, with 100% certainty predict what blockers may arise in the whole next week is a kind of clairvoyance I’m not sure is possible. If it was, we wouldn’t need daily standups in that second week.

And, once again, Kanban is a thing.

Please, let’s just not use “all work being done” as a metric for time off.

I mean, that’s true, but the point still stands - every first Friday of a sprint there is ALWAYS going to be work to be done.

And what if they’re doing Kanban?

The point is, Fridays off shouldn’t ever be dependent on “all work being done”.

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.

This sounds like the devs are personally, sword and shield in hand, defending the application from attacks, instead of just writing software which adheres to modern security practices, listening to the Security Officer and occasionally doing an audit.

This comment smells of outdated software development practices.

If you have separate developers for writing unit tests, and not every developer writing them as they code, something is already very wrong in your project.

Deployment and infra should also mostly be setup and forget, by which I mean general devops, like setting up CI and infrastructure-as-code. Using modern practices, which lean towards continuous deployment, releasing a feature should just be a matter of toggling a feature flag. Any dev can do this.

Finally, if your developers are ‘code monkeys’, you’re not ready for a project of this scale.

There are good reasons to dislike Telegram, but having “just” 30 engineers is not one of them. Software development is not a chair factory, more people does not equal more or better quality work as much as 9 women won’t give birth to a baby in a month.

Edit:

Galperin told TechCrunch. “‘Thirty engineers’ means that there is no one to fight legal requests, there is no infrastructure for dealing with abuse and content moderation issues.”

I don’t think fighting legal requests and content moderation is an engineer’s job. However, the article can’t seem to get it straight whether it’s 30 engineers, or 30 staff overall. In the latter case, the context changes dramatically and I don’t have the knowledge to tell if 30 staff is enough to deal with legal issues. I would imagine that Telegram would need a small army of lawyers and content moderators for that. Again, not engineers, though.