R the user and run with it I loved the inside stories and this is a book I will keep going back
To In The Future If in the uture if need inspiration Absolute waste of timeImagine being stuck at the Christmas Party with that guy who was with the company since its ounding the *Guy Who S Greatest Claim *who s greatest claim ame is knowing the boss rom back in the glory days and just loves recycling the same old anecdotes with increasing repetitiveness This is the book version of it I am sure Ken is a *fantastic developer and a nice guy Just by working on the purple project * developer and a nice guy Just by working on the purple project can rightly Flight, Vol. 7 feel satisfied that he has achieved great things in his career as a software developer But a book describing the three times he met Steve Jobs down to the last minute detail is not something that interested meIt s not about how Apple works the rules the book refers to are as admitted by the author made up of an unspoken work ethic within the team There is no good product process in this book either inact many things they did are mistakes you can only get away with in a waterfall company with an immense budgetIt was decently written and there are bits of interesting trivia hidden around the book but not enough to make it worth it All in all it was not a struggle to inish the book but I ound little value in it personally This raming of this book is a little misleading Waaaaaay too much time is spent talking about coding web browsers that have nothing to do with the heart of the subject When the discussion gets to building the iPhone and specifically the author s work on the keyboard it gets much interesting. Llaboration illuminating each with lessons learned over his Apple career He introduces the essential elements of innovation inspiration collaboration craft diligence decisiveness taste and empathy and uses these as a lens through which to understand productive work cultureAn insider's tale of creativity and innovation at Apple Creative Selection shows readers how a small group of people developed an evolutionary design model and how they used this methodology to make groundbreaking and intuitive software which countless millions use every day. Ken The attitude abstracted away a lot of the most interesting parts of
problem solving into real life metaphors I had no interest in buying It solving into real life metaphors I had no interest in buying It perfectly okay to name particular situations or easier reference later but don t use terms that have little to nothing to do with the technical problem underlying the situation after
A While I Completely Forgot What Giggly Demo Referred To while I completely Camp Rex forgot what giggly demo referred to it would have been appropriately titledirst successful autocompletion demo and the black slab encounter could have been Yahoo page
artifact Sometimes by dumbing down a term too much you lose the along with the detailsHaving said that Ken does a good job picking out memorable personalities and idiosyncracies in the characters that appear in the book Richard Williamson s hand drill motion Scott Forstall s long spidery ingers genetically predisposed to touch screen precision tapping Imran Chaudhri s smooth demeanor and Kim Vorrath s hairstyles all painted a vivid picture in my mind of these people and made their scenes enjoyable to read If there was one storytelling success in this book it would be this painting every participant in the journey as a human being with strengths weaknesses and strong motivations Each individual except maybe the candy bar guy whose significance I still don t understand stood out as someone meaningful to Ken and Purple s journey Good job A bit counterintuitive to how most companies work At Apple the ocus is on to build great demos and keep polishing them till you get to the end result Instead of multiple AB testing take the best call Touch of Enchantment fo. Ndloor of the company as a specialist directly responsible When Dads Don't Grow Up for experimenting with novel user interface concepts and writing powerful easy to use softwareor products including the iPhone the iPad and the Safari web browser His stories explain the symbiotic relationship between software and product development or those who have never dreamed of programming a computer and reveal what it was like to work on the cutting edge of technology at one of the world's most admired companiesKocienda shares moments of struggle and success crisis and co. ,
load artifact Sometimes by dumbing down a term too much you lose the
This is the real deal written by an I was also
There During That Time that time book accurately describes Apple s software engineering during the second Steve Jobs era For hardware engineering read Adam Lashinsky s Inside AppleThe vivid descriptions in the book are better than the analyses I would stress that the principles and practices described by the author were compl Overall not bad I loved the Intersections chapter in which Ken Kocienda discusses design principles in detail The keyboard constellation matching algorithm iteration rom prototype to prototype and SpringBoard touch size all provided detailed insight into Apple s design thinking and what made Purple an exciting adventure in problem solvingI didn t appreciate the dumbing down of programming principles Too often Ken Kocienda oversimplifies otherwise technically exciting concepts For example the black slab encounter reduced graphical artifacts Pee Wee Scouts treasury (Pee Wee Scouts, from loading Yahoo to a single irrelevant moniker I wanted to know specifically why the rectangle was black and what parts of Yahoo led to the browser window showing that specific artifact The giggly demo all demos could be called giggly because programmers enjoy seeing their code workor the irst time the candy bar conversation the metaphor or code as recipe books There are too many situations through the book where I elt I was being talked down toLike The Author Didnthe author didn believe in the reader s my ability or curiosity to parse programming problems in my head that I didn t have the intellectual capacity or interest in solving the problem along with. An insider's account of Apple's creative process during the golden years of Steve JobsHundreds of millions of people use Apple products every day; several thousand work on Apple's campus in Cupertino California; but only a handful sit at the drawing board Creative Selection recounts the life of one of the ew who worked behind the scenes a highly respected software engineer who worked in the High Heat final years the Steve Jobs era the Golden Age of AppleKen Kocienda offers an inside look at Apple's creative process Forifteen years he was on the grou.