dandi8

The coalition is a mix of left (Lewica), center (Donald Tusk's KO) and center-right (Polska 2050, PSL).

KO generally voted for the bill, it was PSL who voted overwhelmingly against it, which, together with PIS, made it so that the bill didn't pass.

There's good reasons to hate Tusk, and I share a lot of them, but this one isn't it. With the cards he was dealt, there wasn't much he could've done.

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

I also have the Pro version, and I like it, with caveats.

First of all, the LEDs are waaay too bright. I had to change their brightness levels in the firmware, which was not the easiest as IIRC the code for that was not the best documented.

On the flipside, making changes to the firmware, compiling and uploading it to the keyboard is quite easy.

Secondly, the Bluetooth can be a bit buggy. Not only can the keyboard randomly refuse to connect (for which the fix is a button combo to forget the connection), the two halves themselves sometimes have trouble connecting.

Thankfully, that's a rare occurrence, even if still quite annoying.

The keyboard itself, however, is still quite comfortable for my tiny hands, is very customizable in terms of what key does what, and you can connect it directly to your PC via cable.

The last one also has a caveat, though, as there's currently no way for the two halves to talk via cable (though I think some people are working on that, at least for the pro version).

I needed something good for work, and I mostly got it. I'm planning to stick with this keyboard until it dies.

Oh, and I like that you can adjust the tenting, though I always use the highest setting.

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.