[PDF FREE] (Creative Selection) Author Ken Kocienda

All piece f paper about 2 inches wide by 13 inches tall a little smaller than half the size Royal Heirs Required of a credit card turnedn end I pinned up this little slip Hag's Nook of papern the bulletin board next to my desk I looked at it The Cambridge Companion to Shakespeare often This was all the screen real estate I had available for my keyboardThis was my touchscreen typing canvas People would have to tap tap tap in that tiny rectangle to type and I had to figureut how to make that happen As I pondered that small shape and took stock A misteriosa chama da rainha Loana of my software I got accustomed to the idea that I might need to rethink somef the decisions that led "TO THE DERBY WINNING DESIGN PERHAPS ALL OF THEM "the derby winning design perhaps all 年下彼氏の恋愛管理癖 [Toshishita Kareshi no Renai Kanriguse] of them bit counterintuitive to how most companies work At Apple the focus isn to build great demos and keep polishing them till you get to the end result Instead Slippery When Wet of multiple AB testing take the best call for 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 I need inspiration I really enjoyed this book It s a great insiders viewf the development process during Apples most creative modern periodIt also reminded me Julius Caesar: The Life and Times of the People’s Dictator of all the good time that can be had inside a development team The fusionf creativity and technology to create new and interesting thingsWould recommend This is the real deal written by an insider I was also there during that time This 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 completely unwritten and unnamed as the author says So if you re trying to be like Apple by reading a book you re doing it wrong If you want to be like Apple ditch the business books and startup blogs do you think Steve Jobs read those things and really focus Die Schnapsstadt on the product There s nothing in the book about MVP Agile Scrum AB testing TDD etc Apple really didn t work *like that The key is what the author calls creative selection demoingdogfoodingiteratingconverging the product with tight loopsf communication with minimal *that The key is what the author calls creative selection demoingdogfoodingiteratingconverging the product with tight loops La fortuna dei Wise of communication with minimal enforced by secrecyOne thing thatccurred to me is that the examples given and generally in Apple s history are Thunderbolts: Justice, Like Lightning... ones where the product definitions were relatively well formed and concrete up front leaving plentyf room for technical innovation but little room for exploration and business validation Before getting to that concrete vision the Apple way isn t applicable I d been hoping for a book like this about Apple I ve been working in product design for almost thirty years and this just confirms that writing about the user experience field has unfortunately been dominated by agency types Kocienda s experience reflec Absolute waste By Pike and Dyke :A Tale of the Rise of the Dutch Republic of timeImagine being stuck at the Christmas Party with that guy who was with the company since its founding the guy who s greatest claim to fame is knowing the boss from back in the glory days and just loves recycling the sameld anecdotes with increasing repetitiveness This is the book version Medioevo «superstizioso» of it I am sure Ken is a fantastic developer and a nice guy Just by workingn the purple project he can rightly 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 Death of a Dreamer of an unspoken work ethic within the team There is no good product process in this book either in fact many things they did are mistakes you cannly get away with in a waterfall company with an immense budgetIt was decently written and there are bits The Beloved Scoundrel of interesting trivia hidden around the book but not enough to make it worth it All in all it was not a struggle to finish the book but I found little value in it personally Mr Kociendaffers some int. Nd floor Downcanyon: A Naturalist Explores the Colorado River through the Grand Canyon of the company as a specialist directly responsible for experimenting with novel user interface concepts and writing powerful easy to use software for products including the iPhone the iPad and the Safari web browser His stories explain the symbiotic relationship between software and product development for those who have never dreamedf programming a computer and reveal what it was like to work Il Barça on the cutting edgef technology at Italian Phrase Book onef the world's most admired companiesKocienda shares moments f struggle and success crisis and co. ,
This is an excerpt from the book that I found n the interwebsThe full title will be released The Countess on September 18 Within a weekf picking my keyboard Scott scheduled a private demo with Phil Schiller Apple s top marketing executive the man who after Steve was most responsible for communicating to prospective customers exactly why we thought OUR PRODUCTS WERE GREAT AND WHY THEY SHOULD GO products were great and why they should go and buy Gully Dirt: On Exposing the Klan, Raising a Hog, and Escaping the South oneScott didn t clue me inn the politics in play between him and Phil Kelttiläistarinoita or why he had scheduled the demo I imagined that Scott was eager to showff the results f the keyboard derby which must have been a topic for discussion up at the executive level In any case my job was to prepare my demo so it worked as it did for the demo derby so that s what I didWhen Scott brought Phil to the conference room I was waiting This was the first time I ever met Phil and I was nervous I set everything up as I had a few days earlier but I had already made a couple f changes to the keyboard user interface Scott introduced me Phil greeted me with a uick courtesy *That Showed He Wanted To *showed he wanted to right down to businessHe picked up the Wallaby and tapped a few times I didn t see what he typed Phil asked me why I d put than Uomini ad Auschwitz: Storia del più famigerato campo di sterminio nazista one lettern every key He was pleasant but direct He seemed to think that my keyboard looked Roma Noir odd that it reuired an explanationI tried to give himne I told him about A History of the Crusades, Volumes I, II and III (Boxed Set) our decisions to make big keys that were easy to target and couple them with suggestions from a dictionaryPhil wasn t satisfied and he said so Then that was it I was surprised we were done so fast The demo wasver in about two minutesIt was sobering to hear Phil s point Love is the Enemy of view Obviously he had nonef the emotional connection I had to my keyboard While I had been working hard Exhalation on it for Phil it was brand new and he was indifferent to it He expected the software to win himver and apparently it didn t This mattered for two reasons First as I said Phil would be playing a pivotal role in pitching the Purple phone to people in the Galileo outside worldnce we were done developing it Second and perhaps important his reaction was just like a prospective customer evaluating a product from scratch My keyboard would be a part Oglinda salvata of theverall impression and Phil was confused rather than convincedA couple days later Scott and I repeated the private demo performance for Tony Fadell the executive in charge f the iPod division I had never met Tony before either but I didn t have to know him to see how preoccupied he was When he walked ver to the conference room table with my demo Nemico on it he barely glanced at my keyboard He didn t ask any uestions Then he tried my software but he couldn t have typed than a wordr two The demo with him was even shorter than the Cannella e polvere da sparo one for Phil and within a minute he and Scott wentff together for a private meeting leaving me alone in the conference room to clean up the Mac the Wallaby and the wires connecting themTwo demos with less than positive responses Add that to my fellow derby entrants lack f excitement and I could tell we didn t yet have exactly the right solution I didn t get to demo the software for Steve Maybe Scott concluded that we weren t ready for the big time but he never said anything specific to me about these executive demos good r badI didn t feel like I had let Scott down My code was the same as it was n derby day There were no bad bugs during these executive demos As I tried to interpret the feedback and decide what to do next I thought back to the Black Slab Encounter with Safari That breakthrough didn t represent an end it signaled a beginning As exciting as it was to see ur web browser render the first sliver f a web page we realized what the milestone meant I began to look at my derby winning design in a similar way as if it were a successful audition rather than a sold ut performanceI started to think about improvements and to help me keep my keyboard goal literally in sight as I sat in my DOGA AST office I measured and cutut a sm. An insider's account Poems (The I Tatti Renaissance Library) of Apple's creative process during the golden yearsf Steve JobsHundreds Bleach, Volume 05 of millionsf people use Apple products every day; several thousand work n Apple's campus in Cupertino California; but nly a handful sit at the drawing board Creative Selection recounts the life Pentimento ofne La maga delle spezie of the few who worked behind the scenes a highly respected software engineer who worked in the final years the Steve Jobs era the Golden Agef AppleKen Kocienda The Last Testament offers an inside look at Apple's creative process For fifteen years he wasn the grou. .


Eresting insights and anecdotes n product development at Apple I especially enjoyed the pening chapter Run to the Roar: Coaching to Overcome Fear on his iPad demo That emphasisn demos and feedback hit home because The Art of Teaching the Bible: A Practical Guide for Adults of somef the software development work my teams have been doing I ve thought about recommending it to a few developers but give them the caveat that the technology portions are written for people without a software engineering background Overall not bad I loved the Intersections chapter in which Ken Kocienda discusses design principles *in detail The keyboard constellation matching algorithm iteration from prototype to *detail The keyboard constellation matching algorithm iteration from prototype to 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 Gaudi of programming principles Tooften Ken Kocienda The Collected Works of Abraham Lincoln, Vol. 2 oversimplifiestherwise technically exciting concepts For example the black slab encounter reduced graphical artifacts from loading Yahoo to a single irrelevant moniker I wanted to know specifically why the rectangle was black and what parts Astrología para principiantes 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 work for the first time the candy bar conversation the metaphor for code as recipe books There are too many situations through the book where I felt I was being talked down to like the author didn t believe in the reader s my abilityr curiosity to parse programming problems in my head that I didn t have the intellectual capacity Amen: what prayer can mean in a world beyond belief or interest in solving the problem along with Ken The attitude abstracted away a lotf the most interesting parts No Puedo Perderte of problem solving into real life metaphors I had no interest in buying It s perfectlykay to name particular situations for 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 and it would have been appropriately titled first successful autocompletion demo and the black slab encounter could have been Yahoo page load artifact Sometimes by dumbing down a term too much you lose the reader along with the detailsHaving said that Ken does a good job picking In Every Heartbeat out memorable personalities and idiosyncracies in the characters that appear in the book Richard Williamson s hand drill motion Scott Forstall s long spidery fingers genetically predisposed to touch screen precision tapping Imran Chaudhri s smooth demeanor and Kim Vorrath s hairstyles all painted a vivid picture in my mindf these people and made their scenes enjoyable to read If there was The Seraphim Code 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 stoodut as someone meaningful to Ken and Purple s journey Good job Ken was part Sortemesse of the team that created Safari and WebKit as well as the creatorf the iOS keyboard n iPhone and later the iPad Funny enough I use his creation to write his review This book is a an inside account
of a software 
a software during the golden age at Apple It follows Ken though his day to day work at apple during his various projects and manages to give a pretty deep view into how Apple perated under JobsFrom an engineering perspective a lot Klara with A K of what he describe sounds just like a very very mature softwarerganization to me highly demo driven iterative development cross team dog fooding highly adaptive engineers swarming around hard problems feedback culture direct accou This framing Serving Sera 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 heartf the subject When the discussion gets to building the iPhone and specifically the author s work Samurai! on the keyboard it gets much interesting. Llaboration illuminating each with lessons learnedver his Apple career He introduces the essential elements La meglio gioventù 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 talef creativity and innovation at Apple Creative Selection shows readers how a small group f people developed an evolutionary design model and how they used this methodology to make groundbreaking and intuitive software which countless millions use every day.

Summary Creative Selection

Creative Selection

Leave a Reply

Your email address will not be published. Required fields are marked *