Creative Selection recounts the life of one 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 Age of Apple.Ken Kocienda offers an inside look at Apple's creative process. For fifteen years, he was on the ground floor 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 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 companies.Kocienda shares moments of struggle and success, crisis and collaboration, 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 culture.An 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.

    With this practical book, you’ll learn how to design effective microinteractions: the small details that exist inside and around features. How can users change a setting? How do they turn on mute, or know they have a new email message?Through vivid, real-world examples from today’s devices and applications, author Dan Saffer walks you through a microinteraction’s essential parts, then shows you how to use them in a mobile app, a web widget, and an appliance. You’ll quickly discover how microinteractions can change a product from one that’s tolerated into one that’s treasured.Explore a microinteraction’s structure: triggers, rules, feedback, modes, and loopsLearn the types of triggers that initiate a microinteractionCreate simple rules that define how your microinteraction can be usedHelp users understand the rules with feedback, using graphics, sounds, and vibrationsUse modes to let users set preferences or modify a microinteractionExtend a microinteraction’s life with loops, such as “Get data every 30 seconds”

    "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic." --Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." --Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling--and building--business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." --Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." --Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." --Kyle Brown, author of Enterprise Java(TM) Programming with IBM(R) WebSphere(R) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:Getting all team members to speak the same language Connecting model and implementation more deeply Sharpening key distinctions in a model Managing the lifecycle of a domain object Writing domain code that is safe to combine in elaborate ways Making complex code obvious and predictable Formulating a domain vision statement Distilling the core of a complex domain Digging out implicit concepts needed in the model Applying analysis patterns Relating design patterns to the model Maintaining model integrity in a large system Dealing with coexisting models on the same project Organizing systems with large-scale structures Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

    You can think of this problem as a variant of the well known "telephone game", where some trivial rumor is repeated from one person to the next until it has become distorted beyond recognition and blown up out of all proportion.Unfortunately, the objects of this telephone game are generally considered cornerstone truths of the discipline, to the point that their acceptance now seems to hinder further progress.In this short ebook, we will take a look at some of those "ground truths": the claimed 10x variation in productivity between developers; the "software crisis"; the cost-of-change curve; the "cone of uncertainty"; and more. We'll hone our scholarship skills by looking up the original source for these ideas and taking a deep dive in the history of their development. We'll assess the real weight of the evidence behind these ideas.And we'll confront the scary prospect of moving the state of the art forward in a discipline that has had the ground kicked from under it.

    Through in-depth interviews and discussions, the common attributes of these elite project managers—from character and beliefs to organizational approaches—are uncovered and help to explain their achievements. Painstakingly researched, this guide offers key insights by providing multiple perspectives on the character makeup of the world’s most successful project managers.

    Some of these ideas will turn out to be stunning successes that will have a major impact on our world and our culture: The next Google, the next Polio vaccine, the next Harry Potter, the next Red Cross, the next Ford Mustang. Others will be smaller, more personal but no less meaningful, successes: A little restaurant that becomes a neighborhood favorite, a biography that does not make the best-seller list but tells an important story, a local nonprofit to care for abandoned pets. At this very same moment, another group of people is working equally hard to develop new ideas that, when launched, will fail. Some of them will fail spectacularly and publicly: like New Coke, the movie “John Carter”, or the Ford Edsel. Others will be smaller, more private, but no less painful failures: A home-based business that never takes off, a children’s book that neither publishers nor children have any interest in, a charity for a cause that too few people care enough about.If you are currently working to develop a new idea, whether on your own or as part of a team, which group are you in? Most people believe that they either are, or will be, in the first group—the group whose ideas will be successful. All they have to do is work hard and execute well. Unfortunately, we know that this cannot be the case. The law of market failure tells us that up to 90 percent of most new products, services, businesses, and initiatives will fail soon after they are launched—regardless of how promising they sound, how much we commit to them, or how well we execute them. This is a hard fact to accept. We believe that other people fail because they don’t know what they are doing. Somehow, we believe that this does not apply to us and to our idea—especially if we’ve experienced victories in the past.Filled with detailed case studies, a lesson on creating your own hard data, a strategy for market engagement, and an introduction to the concept of a pretotype (not a prototype), The Right It is a groundbreaking, entertaining, and highly practical book delivers a proven formula for turning ideas, products, services, and businesses into successful endeavors.As Alberto writes, “make sure you are building The Right It before you build It right”.

    We're expected to be authentic but not too authentic. Professional but not stiff. Friendly but not an oversharer.As organizational consultants and regular people, we know what it's like to experience uncomfortable emotions at work - everything from mild jealousy and insecurity to panic and rage. Ignoring or suppressing what you feel hurts your health and productivity but so does letting your emotions run wild.In this book we'll help you figure out which emotions to toss, which to keep to yourself, and which to express in order to be both happier and more effective. We'll share the latest research and helpful tips, and reveal the surprising reason why you'll actually be more healthier and focused if you're less passionate about your job.Drawing on what we've learned from behavioural economics, psychology and our own experiences at countless organizations, we'll show you how to bring your best self (and your whole self) to work every day.