News for hackers. Stuff that matters.
Re:IPad 2 Official Specs by christoph on Wednesday March 02, 2011 @02:20PM (#2280793)
It truly amazes me that a company can not only design, manufacture and develop software like this in near 100% secrecy, but that they can also have their website completely updated instantly after the keynote with beautiful graphics and videos. How they do it and keep it so under wraps astounds me.
Re:IPad 2 Official Specs by TomOfTTB on Wednesday March 02, 2011 @02:22PM (#2280804)
Simple. They...

1. Take steps that make it easier to identify leakers (like embedding secret numbers into promotional photos so they can tell who leaked them if they get published)

and 2. They pursue anyone who dares leak information with the ferocity of a rabid dog.

No real mystery here.

Re:IPad 2 Official Specs by cletus on Wednesday March 02, 2011 @02:28PM (#2280835)
While I don't disagree with your observations, I think it would be remiss to exclude the fact that many Apple employees are incredibly loyal and believe in the company.
Re:IPad 2 Official Specs by kaptain on Wednesday March 02, 2011 @04:26PM (#2281406)
When I started working for Apple (about 5 years ago now) it was my dream job (I had serious fanboitis). The new hires got a security orientation which was your basic "We spend lots of money protecting things; don't do anything lame."

But the reality of working makes the magic unicorn dust wear off. I saw a bunch of prototypes and I knew a bunch of information that nobody else 'knew' but lots of outsiders suspected. I became more interested in my work than selling other people this idea that I had these secrets that I could pass onto others. (We were also told to 'eat our own dog-food' which makes me highly suspicious of every Software Update to this day. I always wait a couple weeks before installing anything new.)

That's an important part of the equation. If your employees are more interested in leaking information than working, maybe you're doing something wrong. (Just to clarify, I still consider Apple a great place to work; I left because I wanted to do something different, not because I felt that it was a poor place to work.)

[Edited for grammar]

Re:IPad 2 Official Specs by megablast on Wednesday March 02, 2011 @07:45PM (#2282170)
Surely if you were encouraged to 'eat your own dog food', that would mean people inside apple would be testing stuff themselves, so would mean eventual public releases would be better?
Re:IPad 2 Official Specs by kaptain on Thursday March 03, 2011 @12:46AM (#2282983)
You might think so. It would be hard to test this empirically since I would need an alternate universe where people inside apple did not test unreleased software on themselves before releasing. But seeing the process that goes into deciding what fixes go in and what fixes don't has educated me to NOT update unless I have a real need to. I saw lots of examples where a fix for something broke something else that was seemingly unrelated. Or that a feature that I liked depended on a bug that was going to be fixed. That's why I wait on Software Updates. And if I don't need the Update, I don't install it.

The problem with 'eating your own dog food' is that it is dog food, so it's really hard to eat. To comply with this edict, I would set up a separate machine and install the latest build and play around with it for about 15 minutes and spend a half hour (or more) filing bugs. Thus, I wasn't really eating my own dog food...

Installing new builds turned out to be a big time-sink. It took time for the build to install and then you had to go through the paces of setting the machine up. You also had to do a clean install because of incompatibilities with previous releases.

After all of this, you started testing. Then you started finding bugs, and since I was in engineering, I tried to make sure the bug was reproducible and even tried to track down which component was responsible (which is a mess if you're dealing with overlapping stacks of software). THEN, you had to crawl through the maze of reported bugs to see if there was something already reported that was close... Hopefully they've made the bug reporting system better since I was there (but I doubt it… the system I used had been in place for a long time).

On top of that, I needed to get actual work done. There was no way that I was truly going to use a ever changing system of dubious quality to do work. I tried, and it was too difficult (although I knew of some folks that were faithful and did so).

'Eating your own dog-food' is an ok idea. It's not clear to me that it was the best idea for this particular situation. As a general practice, it seems that if your particular product scope is small enough, this would be a good idea. If it's larger, hiring a set of dedicated test engineers would be awesome. (The ironic thing is that Apple had those too!)

Re:IPad 2 Official Specs by TomOfTTB on Wednesday March 02, 2011 @02:33PM (#2280865)
True but every company has mostly loyal employees (imho). The trick is keeping the dishonest ones in-line and the best way to do that is through fear. Apple makes it clear they'll go nuclear on anyone who leaks information and the dishonest ones realize it probably isn't worth the risk.
Re:IPad 2 Official Specs by cletus on Wednesday March 02, 2011 @02:49PM (#2280954)
I disagree. In a company with 10s of thousands of employees it still only takes 1 to leak something. Loyalty is (IMHO) far more important than those other factors (although they too contribute).

Consider a more open example: Google. Internally Google is more open than I believe Apple to be (I have experience with the former, none with the latter other than what I've read).

You may think that a lot of stuff leaks from Google based just on TC stories and so forth and while there are things I'm sure we could manage better, when I joined I was (and still am) amazed at what doesn't leak.

Google doesn't have the same militant, even draconian, approaches to secrecy that Apple does. What they have in common is that most people in both companies (IMHO) are very loyal.

Re:IPad 2 Official Specs by dedward on Wednesday March 02, 2011 @07:27PM (#2282119)
Right - because the ones that dind't - see previous comment :)
Re:IPad 2 Official Specs by mechanical_fish on Wednesday March 02, 2011 @02:27PM (#2280834)
3. They do not employ very large teams, and those small teams are very dedicated.

Apparently they didn't just read Brooks and Peopleware, they also seem to act upon them.

Re:IPad 2 Official Specs by solutionyogi on Wednesday March 02, 2011 @02:24PM (#2280812)
I completely agree. Their website roll out team kicks ass! They should publish how they manage the 'browser caching' issue, whenever I go to Apple.com after/during keynote, I get the latest page without doing hard refresh.
Re:IPad 2 Official Specs by sghael on Wednesday March 02, 2011 @02:53PM (#2280973)
I don't disagree they they must have their act together to support such big online launches. But for cache busting, isn't it just a simply matter of renaming resources and having your framework + deploy scripts manage the rest for you?

most sites use assets with additional query parameters added to keep them fresh (i.e. file?1234566778.js). Apple looks like they are adding some parameters into the filenames themselves.

It probably also involves cache-control settings as mentioned, but I think file renaming is the more reliable method of cache busting.

Re:IPad 2 Official Specs by cheald on Wednesday March 02, 2011 @02:27PM (#2280831)

    Cache-Control:max-age=221
That would do it.
Re:IPad 2 Official Specs by solutionyogi on Wednesday March 02, 2011 @02:49PM (#2280955)
I think you are over simplying. Look at http://www.mnot.net/cache_docs/ for the nuances involved.
Re:IPad 2 Official Specs by cheald on Wednesday March 02, 2011 @05:00PM (#2281550)
I'm really not. max-age and the Expires header, properly set, will control caching at just about every possible step. If you refresh apple.com several times, you'll notice the max-age cycles down with each refresh, and the Expires header stays the same. They're obviously set up to cause the page to have a short maximum lifetime in both public and private caches, and in the case of a launch, it's not that hard to make sure that the old copy of the page expires at 11 AM PST or whenever you want your announcement to go live.

Announce product, push deploy button on website, people hit website and browser requests a new copy of the page because its current copy expired at 10:59:59, and presto, it all magically works.

Re:IPad 2 Official Specs by sghael on Wednesday March 02, 2011 @06:52PM (#2282011)
But that only solves for the case of predictable events. If you want to remain agile, and do deployments on an as-needed basis, then you need to cache bust with file naming or query parameters as I mention in other msg. Again, I'm pretty sure this is the preferred method of most web teams, and also appears to be what Apple is doing (atleast with a subset of their assets).
Re:IPad 2 Official Specs by cheald on Wednesday March 02, 2011 @11:23PM (#2282810)
Assets, yes. Pages, no. Query strings for cachebusting CSS/images is pretty standard.
Re:IPad 2 Official Specs by smackfu on Wednesday March 02, 2011 @03:57PM (#2281269)
I seem to recall the last set of updates before this speech didn't work perfectly. People were seeing the results of mixed stylesheets and had to do forced refreshes to clear it.
Re:IPad 2 Official Specs by mike463 on Wednesday March 02, 2011 @06:12PM (#2281865)
They must use pointers to do it. :)