> Josh Shaffer, whose team’s work was part of the iOS 11 leak last fall. Is leaking the reason it was rushed out the door? If not, I can't imagine why he's upset about it.
Yeah, how does it affect him at all? He worked on a great product and the leak didn't make it worse. Most likely just Apple trying to add a personal element to dissuade leakers, by also accusing them of hurting friends/colleagues.
You show up to work each day. You've been working a lot lately, but you're really excited about the thing you're working on. You're looking forward to when it's ready and ships. But it's not time yet. It's not ready. You want the world to see it when you're ready to really show them something. Not just the idea of a thing, but the actual thing. When they can see it, touch it, understand it and breathe it. When they can really appreciate what you've been doing.
You've been working on this thing for awhile. You know there's still a long slog ahead. But you think—hey, one day soon, we'll get to talk about this thing.
Then one morning, you get into the office and you see some blog is talking about your project. They have a bunch of the details wrong, but it's definitely the project you're working on. And they're saying it's coming out in the next update.
Your work never has the chance to speak for itself. Someone decided to speak for your work instead. Just so they could feel important. It wasn't even their work to speak for. It was yours, and you and others had already been making decisions on how you wanted to talk about it, what things you wanted to show and where and how you wanted the work to speak for itself.
Wouldn't you be annoyed about it?
Wouldn't you be disappointed that someone leaked your work when later when you do finally announce it people don't let your work speak for itself, but just compare your work to whatever their minds imagined, made up and idealized about what you might be working on, doing or building?