• bentcheesee@lemmy.zip
    31·
    7 hours ago

    Incredibly misleading and/or stupid graphs are so funny to me. Because you ship out the most updates, doesn’t mean it’s the best, it means youre fixing and/or generating more bugs and issues.

    Yeah, I updated my minecraft mod 20 times in a week, it doesn’t mean it’s a stellar mod, it’s less than mediocre at best. It was primarily fixing bugs and a crash. Meanwhile the Create mod updates about once every three weeks or so on average, but that’s because they properly playtest and bugfix and patch and do all that before they send out an actual update.

    • Skullgrid@lemmy.world
      3·
      7 hours ago

      This is why there are a bunch of improvished people adding nonsense updates to git repositories, padding out their resume out of desperation.

      It’s hard to blame them trying to climb their way out of poverty, but it does harm the people trying to do work.

    • ShaggySnacks@lemmy.myserv.oneEnglish
      4·
      7 hours ago

      I think Muskie is hallunicating. Lieing implies that he knows the truth. Muskie actually believes in his own fever dreams.

  • bitjunkie@lemmy.world
    64·
    12 hours ago

    “My codebase is way better because it has 300x as many lines of code” - that fucking moron, probably

  • humanspiral@lemmy.ca
    2·
    6 hours ago

    I thought Musk was in a ketamine hole when announcing lawsuit against Apple and OpenAI. Waking up briefly to add this legal argument is not proof of not still being in hole.

  • wulrus@lemmy.world
    3·
    7 hours ago

    That statement would make a lot more sense with a benchmark graph based on standardised tasks.

  • yarr@feddit.nlEnglish
    30·
    12 hours ago

    I think it’s because grok ships the most bugs, so they have to ship the most patches.

  • GissaMittJobb@lemmy.ml
    80·
    17 hours ago

    On the contrary, the rate of mobile app updates being high is more of a red flag of an app development team not having the situation under control, being forced to panic-ship fixes.

    • cub Gucci@lemmy.today
      2·
      7 hours ago

      Why? I genuinely think that daily delivery in my field (b2b specialized software) would be a very good practice. Why in mobile apps it’s not the truth?

      • GissaMittJobb@lemmy.ml
        3·
        7 hours ago

        It’s a bit different with mass market mobile applications because of the supply chain constraints - most notably the Apple reviewing process. Your next app release may for whatever reason they feel like unexpectedly take an additional week, so do ensure that your QA is in order before releasing.

        Another significant factor is the lack of control you have over the software once released - any bugs you ship may potentially be out there for a long, long time.

        Web applications don’t have these constraints and can as such be deployed an infinite amount of times per day. The same goes for backend services, deploy to your hearts content.

        This basically means that most larger mobile applications have adopted approximately weekly release cadences, and that we’ve had to get very good at using feature flagging to control our software in the wild, and avoid large impact of shipped bugs.

  • Rose@slrpnk.net
    107·
    20 hours ago

    Oh wow, Elon figured out how we’ll finally get AGI. The key thing is to publish an automatic mobile client update every single hour of the day! That was the secret productivity metric that every single other company was missing. Thanks, big brain business boy!