• bitjunkie@lemmy.world
    link
    fedilink
    arrow-up
    68
    ·
    6 days ago

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

  • Rose@slrpnk.net
    link
    fedilink
    arrow-up
    97
    ·
    7 days 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!

  • GissaMittJobb@lemmy.ml
    link
    fedilink
    arrow-up
    76
    ·
    7 days 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
      link
      fedilink
      arrow-up
      3
      ·
      6 days 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
        link
        fedilink
        arrow-up
        7
        ·
        6 days 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.

  • bentcheesee@lemmy.zip
    link
    fedilink
    arrow-up
    43
    ·
    6 days 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.

      • Baizey@feddit.dk
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        It’s generally the length of short sprints (blocks of time where some tasks have been estimated/committed for)

        If you’re deploying a new version more frequently than that it’s usually either putting out fires & hot fixing, or someone fucked up the pipeline and now any commit will immediately be deployed straight to prod

    • Bamboodpanda@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      7 days ago

      Yeah but can you spew that nonsense at millions of people on your very own shitty platform? Gotta get on muskies level.

  • pyre@lemmy.world
    link
    fedilink
    arrow-up
    76
    ·
    7 days ago

    does it count as an “update” every time elon fucks with it to push some fresh nazi shit?

    what a meaningless measure. why don’t i update this app one byte at a time? i can say it’s massively outpacing the competition by updating 20 thousand times in the last 4 minutes while the competition updated ZERO times, which means we’re literally INFINITELY faster and by the end of the year we will have released millions of new versions.

    he’s so monumentally stupid

  • yarr@feddit.nl
    link
    fedilink
    English
    arrow-up
    30
    ·
    6 days ago

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

  • REDACTED@infosec.pub
    link
    fedilink
    English
    arrow-up
    14
    ·
    6 days ago

    Having to do the most amount of bug fixes for the app (that does not run the AI itself) is not the flex you think it is

    • goldfndr@lemmy.ml
      link
      fedilink
      arrow-up
      18
      ·
      7 days ago

      To me, it suggests the opposite – they keep breaking stuff or otherwise putting bugs into their client and Grok isn’t very helpful with fixing them.