• 0 Posts
  • 30 Comments
Joined 5 months ago
cake
Cake day: June 12th, 2024

help-circle




  • 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.









  • 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.






  • 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.