leading ai company
-
"Look how productive I am!"
"Changes in this release: general improvements"
-
Because the rate is more a sign of how often problems are found, rather than how many better new things you are applying.
And has nothing at all to do with the AI part of the app getting better.
-
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
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)
-
i wish this was fake https://twitter.com/elonmusk/status/1958854561579638960 oh my fucking god
wow its getting dumber faster than the other companies what an achievement
-
i wish this was fake https://twitter.com/elonmusk/status/1958854561579638960 oh my fucking god
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
-
And has nothing at all to do with the AI part of the app getting better.
Yes, that was my point.
-
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.
Two weeks is also such a random and unimpressive statistic.
-
Two weeks is also such a random and unimpressive statistic.
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
