What was it like working on the original iPhone project?
quora.com
quora.com
>I wrote about 6% of the Mac OS X kernel, by lines of code, over a period of 8 years. That’s about 100,000 lines of code a year.
Does that mean he wrote 800,000 LOC in 8 years, or am I reading that wrong?
If he did write 800k LOC, I'm curious why the Kernel is so many LOC? Given OSX is based on BSD, I always assumed Apple's kernel would be small in size (LOC) and mostly just glue between BSD code that has existed for decades.
[1] https://www.quora.com/What-was-it-like-working-on-the-origin...
As for the code output, that is on the high-end of what you would expect to see but within the normal range of some highly skilled individual contributors operating within their domain expertise. Of course, this assumes they are largely left alone to do their work and aren't spending half their time in meetings, making powerpoints, etc. Back when I was plying my trade as an individual contributor, I was good for about 8,000 quality LOC per month if I was minimally interrupted, which is only a little less than the engineer in question.
So to extend on that, if his 800 kLOC is only 6% of the Kernal, does that mean Apple's kernel is around 13 million lines?
wow, I had no idea.
https://books.google.fr/books?id=K8vUkpOXhN4C&lpg=PA49&ots=O...
Linux 3.13 is 7 MLOC in drivers, 2 MLOC in arch, and only 139 KLOC in kernel, so it's probably the drivers that inflate a kernet size but I doubt the iphone needed so much drivers.
http://unix.stackexchange.com/questions/223746/why-is-the-li...
The guy is probably talking about changed lines (added, removed, changed) and might be liking to fiddle with its code style a lot.
http://www.imore.com/debug-40-nitin-ganatra-episode-ii-os-x-...
http://www.imore.com/debug-41-nitin-ganatra-episode-iii-ipho...
I find that a weird statement. If you are pulled into a team because you are a good kernel debugger, in a company where talent in that area likely isn't scarce, wouldn't they pick you because you know ARM, and wouldn't they tell you beforehand exactly what CPU you are dealing with?
There also is very little information in this (or the Quora post), most of which isn't new. How do we know this isn't something someone made up to look interesting (or to score karma on Quora, if it has such a system)?
While the things he mentioned in that post are generally unknown outside of Apple, they are basically rules of the unspoken culture on campus.
(of course, if there's a technical/commercial detail that is still not divulged this is still covered by NDA)
It also has to actually matter to Apple or the employer in question to issue a cease and desist order. I'm not sure they care if he revealed a random prototype from 16 years ago.
[0] https://www.quora.com/What-was-it-like-working-on-the-origin...
Let me reveal how... and you won't believe how simple it is. You Google it.
Once you know the codename, the whole security theatre comes to an end for the non indoctrinated because the moment you Google "<codename> apple project", you see a bunch of results from obscure websites. You click on them and shit, they are accurate leaks.
Same goes for internal utilities as well. Google "<internal utility name> apple" and you sometimes even get a link to a DMG.
So basically Apple's obsession with secrecy is nothing more than security theatre causing inefficiencies within the company.
The leaks are mostly from Chinese domains which makes me thing they happen from the manufacturing side of the business.
> Your reason for querying the authenticity of my name seem arbitrary and unfair. Discriminating against non-familiar names begs the question: non-familiar to who? Would you have questioned me had I used a fake but common English name? If you intend to attract a global community of users you will have to reconsider this approach.
And the protecting privacy bit is a huge cop-out because it's only really "protecting" them from honest actors who adhere to robots.txt. Not to mention that publishing something with your name on it is effectively making that association public; just like how you should assume that passwords committed to a public GitHub repository are no longer secure, you should exercise the same vigilance with your identity. Sure it's great that they let you change it, but someone out there probably already knows the association and wrote about it, and anyone persistent enough to use the Wayback Machine on an anonymous post will probably find out what they need anyway.
There was a big fuss about this issue and then a few weeks later everyone went on about their business, using their phone and enjoying using it without any real problems for a few years. And then they got a new iPhone because they liked the first one so much.
Sorry I can't find the original link for the story.