A Jargon
This was never intended to be a technical book for engineers who love all the geeky details. Instead, it’s supposed to be a book for everyone who is interested in the meteoric rise of a business and technology, and of the people behind that effort.
But when these people write code and create highly technical things that lead to that result, it’s difficult to not get lost in the techy weeds every now and then. So when I’m explaining, for example, that Ficus Kirkpatrick enjoyed working on drivers at the lower levels of the system, or that Brian Swetland worked on the kernel at Danger and Android, or that the engineers at Be and PalmSource were creating a platform and APIs for software developers, it’s necessary to use terms that might ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access