I'm not saying nobody can be like Steve Jobs, but Steve Jobs was an anomaly when it comes to C-Levels, and even when it comes to management in general, at least from reading things like www.folkore.org and interviews with people who worked with him.
And I'm not even talking about talent or vision or whatever, it's just about saying no to pointless features that are there for someone's ego or so that someone can get a promotion.
https://mjtsai.com/blog/2025/02/26/testimony-on-external-pur...
I’m not saying anyone will be better than Tim Cook, I’m saying he’s actively bad. Will his successor be actively bad too? Maybe, but the sooner we find out, the better.
The general publics opinion of Apple is that they are golden and untouchable, the best tech company out there. The reality is much different.
So why isn't that happening?
- Because a lot of journalists are Apple fanbois
- The press publishers don't want to sour relationships with Apple (because of advertising deals)
- Publishing bad things about Apple would infuriate the many Apple fanbois among the readers, causing a shitstorm against the medium
There is even a joke amongst Apple developers who all know that Apple’s claim of “don’t go to the press, it never helps” is a blatant lie as it’s the one thing that works.
Not "never", but it is indeed my observation that the press is much "nicer" in their reporting and much more "forgiving" to Apple than to other similar companies.
In some circles, this observation already has become a running gag when the pen pusher is again too impressed of some Apple marketing.
The advertising deals with apple are not that lucrative, iirc.
So bad reviews are avoided to ensure the media gets the early review clicks.
Yes, you may implement a solution more efficiently by not overengineering it. But at some point constant seek to reduce "complexity" so that more features fit into sprint (funny how story point measure complexity, not time, but sprint is sized in both time and SP capacity) is bound to hit feature completeness. Once you cross over that metaphorical Rubicon it's game over - quality starts to slowly go downhill.
You will not notice it immediately. That edge case that was ignored may not surface for months or years. It may take several idiosyncrasies to line up for a feature to be declared FUBAR. At some point that technical debt does bite you back, but at that point the process (tm) has already optimized away most if not all opportunities for deep refactorings fixing previous rushes to deliver.
Furthermore, Sprint Planning/Refinement are just innocuous ceremonies whose only aim is to facilitate productive discussion between a Product Owner/Manager and an Implementation team as regards delivery timelines and priority ordering thereof. Done properly, it allows a pragmatic approach to achieving a predictable software delivery cadence via mutual compromise.
If the process turns into 'fit as many features into the sprint as possible' at the expense of Performance/Stability/Functionality or Technical Debt accumulation, you're really just doing the 'fast' version of Cheap/Fast/Good Waterfall Project Management.
I never buy products when they are first released. I prefer to wait at least 3-4 months so that production has had time to tweak all the settings and weed out the funky first component deliveries. Also the software devs will have fixed the worst bugs by then.
Who is dealing in fantasies now, friend? :)
Apple's software really isn't in crisis. It's just very low quality relative to what people who've written software for a living know to be possible.
But it doesn't matter - Apple is a prestigious jobs guarantee program for rich kids first, entity that delivers value to consumers second.
It's not that they're chasing shiny things. They're cosplaying competence and they genuinely don't know it. They think they're actually competent, elite really, because they attend 'elite' schools, get good grades and go work at the 'best' places.
They have it ingrained in them that anything a poor person says can be disregarded because poor people are losers, because they're poor. They're an unintentional suicide cult. They genuinely don't know it. You can't convince them of anything because they are rich. If you complain - go see a therapist, there's something wrong with you.
You can youtube search Garys Economics. It's a poor kid who slipped into the rich kids club and defected. It's quite eye opening.
I said they need to, not that I think they will. But they have in the past. There is a reason Snow Leopard is still lauded today.
> It's just very low quality relative to what people who've written software for a living know to be possible.
No, it’s low quality relative to what Apple users came to expect. There was a time when “it just works” was an aspirational goal which permeated their decisions and you could see the results.
> Apple is a prestigious jobs guarantee program for rich kids first, entity that delivers value to consumers second.
What a bizarre conspiracy theory. No company gets to that stratospheric level of success by making hiring incompetent rich kids their primary goal.
By the way, I did catch the rant you posted before. I tried to reply to it but after writing it up and hitting reply, you had already deleted it.
You've gone ahead and made it the first goal in the context of all goals a company has (thus making it 'primary').
That's not a legal move :)
Re-reading my own post - the bit you narrowed in on is the least interesting and controversial in my mind.
We know rich parents do all sorts of things to pad their kids' resumes to get into fancy schools. We know kids game the system to get highest possible grades. We know kids grind leetcode to get the job. We know companies prioritize hiring according to school, grades, ability to pass leetcode. We know people very often prioritize their career trajectory above needs of the company. We know companies prioritize stock price over delivering value to consumers.
I just shortened into a single sentence and you've misunderstood it to mean something bizarre. Oh well.
I don't see a connection between yearly release cycles and a broken notes application. They shouldn't be doing anything that is particularly affected by such changes and the problem they are trying to solve has been mostly solved for 40+ years now.
While it certainly applies to some things, there's a different, bigger issue happening as well.
My understanding is that Apple outsources loads of software not seen as "critical". I think that's the first place for them to look.
Some of this could be resolved by open sourcing their less important apps like Files, Notes or Home which barely ever get touched, yet are full of quirks and bugs. Those apps should be public examples of good SwiftUI coding.
At many places where I've worked, the mentality is: "If that bug didn't block last year's release, then why would it block this year's release?" So it survives one release, it never gets fixed.
Those aren’t options, they’re fantasies. Like dreaming of suing out of existence a company that wronged you, or fixing the world by ruling it, or winning the lottery without playing.
Android isn’t perfect either, it’s a different set of frustrations. And why would Apple ever need to hire you for that specific task, do you really believe there aren’t engineers inside just as frustrated as we are?
The way I see it, the yearly release cycle is to blame. No one inside the company has time to do anything properly anymore. Features are announced and rushed every year, and we’re reaching the point where by the time something which was announced at a WWDC is out of beta, we’re preparing for the next one.
What these companies need to do is slow down and stop chasing every shiny thing. You know, like Apple used to do with macOS. Tim Cook needs to go.