• Fandangalo@lemmy.world
        link
        fedilink
        arrow-up
        38
        ·
        27 days ago

        Here’s 2 faults:

        1. Most people push a build once a week, because making a stable build usually has an engineer combining people’s work, and sometimes there’s conflicts in the merge.
        2. If you have a lot of bugs, you may need to patch more frequently.

        Either way, it’s a bad look. Doing stable daily pushes is good in development, not in a live environment like this.

    • idiomaddict@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      26 days ago

      I’m nowhere close to tech and this is obviously a bad sign. Imagine an apartment complex trying to get new tenants by advertising that they have plumbers and exterminators do work twice a day at various units.

  • i_stole_ur_taco@lemmy.ca
    link
    fedilink
    arrow-up
    88
    ·
    27 days ago

    Yeah and my company has the best dev team because we resolve all the critical incidents we cause by shipping buggy code.

    Some of these other loser companies don’t even have incidents!

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

  • CaptDust@sh.itjust.works
    link
    fedilink
    arrow-up
    73
    ·
    27 days ago

    Lol equating your busted as fuck code that needs constant patching with growth. Gonna keep that around for my own metrics. Yeah boss this is the 9th hotfix to prod this week! Think where we’ll be next month, things are going awesome!

  • GissaMittJobb@lemmy.ml
    link
    fedilink
    arrow-up
    65
    ·
    26 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.

  • pyre@lemmy.world
    link
    fedilink
    arrow-up
    56
    ·
    27 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

  • bitjunkie@lemmy.world
    link
    fedilink
    arrow-up
    55
    ·
    26 days ago

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

  • jellyfishhunter@lemmy.world
    cake
    link
    fedilink
    arrow-up
    37
    ·
    27 days ago

    I have to admit though, getting two app updates per day through the Apple review process is an achievement. (He probably paid them.)

      • kautau@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        27 days ago

        Any update that hits the App Store and increments a version number goes through the Apple review process.

        Certain updates can be done on the fly with custom or third party solutions like https://ionic.io/docs/appflow/deploy/intro

        But this graph doesn’t make it clear if these updates are new binary app deployments or on the fly updates

        • xtr0n@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          26 days ago

          Yeah, I haven’t done it in like 8 months so I think I was conflating Code Push with App Store updates. I do think that apps get treated differently based on the priority of the company and there is some judgement used in the scope of changes. Like I wouldn’t be surprised if Grok is never subject to the random review delays just cuz no one wants to deal with Elon throwing a tantrum

          • kautau@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            26 days ago

            Yeah I’m the lead mobile engineer at my company. We release bigger updates once a month and smaller hotfixes generally weekly or biweekly. For smaller updates we get approval in around 6 hours. They also have a way to expedite reviews in which case we’ve gotten like 30 minute turnaround on reviews (though that’s like boy that cried wolf, only use it if you need to push something really urgent)

    • Skullgrid@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      26 days 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.

  • hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    22
    ·
    edit-2
    27 days ago

    Why would you need to update the app? It should all run on their servers. This is indicative of poor and buggy app design.