Political Science eBooks Download Read Free Political

EBOOK / PDF Creative Selection

Creative SelectionOf paper on the bulletin board next to my desk I looked at it often This was all the screen real estate I had available or my keyboardThis was my touchscreen typing canvas People would have to tap tap tap in that tiny rectangle to type and I had to igure out how to make that happen As I pondered that small shape and took stock of my software I got accustomed to the idea that I might need to rethink some of the decisions that led to the derby winning design perhaps all of them 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 or the user and run with it I loved the inside stories and this is a book I will keep going back to in the uture if I need inspiration I really enjoyed this book It s a great insiders view of the development process during Apples most creative modern periodIt also reminded me of all the good time that can be had inside a development team The At Sixes and Sevens fusion of 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 reallyocus 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 loops of communication with minimal teams enforced by secrecyOne thing that occurred to me is that the examples given and generally in Apple s history are ones where the product definitions were relatively well The Care and Feeding of a Pet Black Hole formed and concrete upront leaving plenty of room The Last Honest Man: Mordecai Richler: An Oral Biography for technical innovation but little roomor exploration and business validation Before getting to that concrete vision the Apple way isn t applicable I d been hoping The Catholic Home for a book like this about Apple I ve been working in product designor almost thirty years and this just confirms that writing about the user experience ield has unfortunately been dominated by agency types Kocienda s experience reflects what it s actually like to design a product No empathy maps or user journeys just a lot of hard work trying to define and solve problems Recommended Absolute Of TimeImagine Being Stuck The of timeImagine being stuck at the Party with that guy who was with the company since its ounding the guy who s greatest claim to 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 Too Many Puppies! fantastic developer and a nice guy Just by working on the purple project he can rightlyeel 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 made up of an unspoken work within the team There is no good product process in this book either in The Wanderers fact 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 toinish the book but I The Last Dickens found little value in it personally Mr Kocienda offers some interesting insights and anecdotes on product development at Apple I especially enjoyed the opening chapter on his iPad demo That emphasis on demos andeedback hit home because of some of the software development work my teams have been doing I ve thought about recommending it to a Standing for Something: 10 Neglected Virtues That Will Heal Our Hearts and Homes few developers but give them the caveat that the technology portions are writtenor people without a software engineering background. 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. Overall not bad I loved the Intersections chapter in which Ken Kocienda discusses design principles in detail The constellation matching algorithm iteration rom prototype to which Ken Kocienda discusses design principles in The keyboard constellation matching algorithm iteration rom 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 of programming principles Too often Ken Kocienda oversimplifies otherwise technically exciting concepts For example the black slab encounter reduced graphical artifacts rom 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 giggly demo all demos could be called giggly programmers enjoy seeing their code work or the Diamantmysteriet first time the candy bar conversation the metaphoror code as recipe books There are too many situations through the book where I elt I was being talked down to like the author didn t 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 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 s 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 orgot what giggly demo referred to and it would have been appropriately titled irst 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 out memorable personalities and idiosyncracies in the characters that appear in the book Richard Williamson s hand drill motion Scott Forstall s long spidery Torrent of Portyngale: Re-Edited from the Unique Ms. in the Chetham Library, Manchester (Classic Reprint) 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 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 Ken was part of the team that created Safari and WebKit as well as the creator of the iOS keyboard on 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 engineer during the golden age at Apple Itollows Ken though his day to day work at apple during his various projects and manages to give a pretty deep view into how Apple operated under JobsFrom an engineering perspective a lot of what he describe sounds just like a very very mature software organization to me highly demo driven iterative development cross team dog The Pocket Mommy fooding highly adaptive engineers swarming around hard problemseedback culture direct accountability or the outcome small teams no open loor offices engineering deeply integrated with top level management hierarchy but with an emphasis on As If Being 12 3/4 Isnt Bad Enough, My Mother Is Running for President! fast decision makingBut you have to take into account that the book starts around 2000 so almost 20 years ago That s by todays internet standards the Stone Age Most companies were thinking completely different about software at that time eg waterfall incremental development separated peopleor reuirements engineering software development uality assurance and so onIt also As If Being 12 3/4 Isn't Bad Enough, My Mother Is Running for President! fuels a sentiment of mine the really good companies don t waste time debating Agile Lean TDD DevOps andriends They simply do it because it s part of their DNAThe little sad note was in the epilogue when he talked about how this culture ultimately depended on Jobs and Stickman Odyssey, Book 2: The Wrath of Zozimos fell apart when he died Againuels a sentiment of mine The higher in the hierarchy a person is the bigger the potential influence on culture positive and negativeI removed one star because some of the interludes The Last of the Tribe felt a bit out of tune with the rest Iound them distracting than emphasizing This raming of this book is a lit. 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 The Book of Air 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. Tle 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 This is an excerpt rom the book that I ound on the interwebsThe ull title will be released on September 18 Within a week of picking my keyboard Scott scheduled a private demo with Phil Schiller Apple s top marketing executive the man who after Steve was most responsible or communicating to prospective customers exactly why we thought our

Products Were Great And Why 
were great and why should go Out And Buy OneScott Didn and buy oneScott didn clue me in on the politics in play between him and Phil or why he had scheduled THE DEMO I IMAGINED THAT SCOTT WAS EAGER TO demo I imagined that Scott was eager to off the results of the keyboard derby which must have been a topic The Seduction of Miranda Prosper for discussion up at the executive level In any case my job was to prepare my demo so it worked as it didor the demo derby so that s what I didWhen Scott brought Phil to the conference room I was waiting This was the The Warrior Princess of Pennyroyal Academy first time I ever met Phil and I was nervous I set everything up as I had aew days earlier but I had already made a couple of changes to the keyboard user interface Scott introduced me Phil greeted me with a uick courtesy that showed he wanted to get right down to businessHe picked up the Wallaby and tapped a ew times I didn t see what he typed Phil asked me why I d put than one letter on every key He was pleasant but direct He seemed to think that my keyboard looked odd that it reuired an explanationI tried to give him one I told him about our decisions to make big keys that were easy to target and couple them with suggestions rom a dictionaryPhil wasn t satisfied and he said so Then that was it I was surprised we were done so ast The demo was over in about two minutesIt was sobering to hear Phil s point of view Obviously he had none of the emotional connection I had to my keyboard While I had been working hard on it or Phil it was brand new and he was indifferent to it He expected the software to win him over and apparently it didn t This mattered Elizabeth I for two reasons First as I said Phil would be playing a pivotal role in pitching the Purple phone to people in the outside world once we were done developing it Second and perhaps important his reaction was just like a prospective customer evaluating a productrom scratch My keyboard would be a part of the overall impression and Phil was confused rather than convincedA couple days later Scott and I repeated the private demo performance or Tony Fadell the executive in charge of 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 over to the conference room table with my demo 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 word or two The demo with him was even shorter than the one or Phil and within a minute he and Scott went off together Theres Always a Trail / Home in the Valley 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 myellow derby entrants lack of excitement and I could tell we didn t yet have exactly the right solution I didn t get to demo the software or Steve Maybe Scott concluded that we weren t ready or the big time but he never said anything specific to me about these executive demos good or badI didn t eel like I had let Scott down My code was the same as it was on derby day There were no bad bugs during these executive demos As I tried to interpret the eedback 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 our web browser render the The Everyman Book of Nonsense Verse first sliver of 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 out performanceI started to think about improvements and to help me keep my keyboard goal literally in sight as I sat in my office I measured and cut out a small piece of paper about 2 inches wide by 13 inches tall a little smaller than half the size of a credit card turned on end I pinned up this little slip. Ndloor of the company as a specialist directly responsible or experimenting with novel user interface concepts and writing powerful easy to use software or 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. ,