Marco Arment

You can have things take three years to come to fruition and still release on a yearly schedule.

It's just a question of being smart about picking what's in and what's not.

Apple's problem is not the annual schedule.

Apple's problem is their inability to correctly pick stuff that will fit in a year.

That's always been their problem.

And that is, you know, that's most organizations problem.

Like, I don't know how many times I've had this exact discussion in my jobby jobs about like, deadlines and schedules and what can fit and resources available or whatever.

Like, it's like Casey was saying, it's a trade off.

It's like, we have this many people, we have this much money, we have this much time, we have these people and who have these skills, like it's not, you know, everyone's not just fungible, right?

You have this set of people and this set of skills and this set of resources and this time or whatever.

What can you fit?

Can you get X by this date?

Can you get Y by that date?

If you have to have something out by this date, what can you fit in?

Don't be ambitious and say, we're going to be done by this date and we're going to have all the stuff.

You know, like you're not going to have all the stuff.

So you have to start to cut things.

And Apple has been really, really bad.

And I feel like worse over the past several years at figuring out

what can we actually fit into an annual release?