But the real advantage these companies have is not so much who they hire, but rather how they enable their people to work together to solve hard problems and create extraordinary products.As legendary Silicon Valley coach--and coach to the founders of several of today's leading tech companies--Bill Campbell said, "Leadership is about recognizing that there's a greatness in everyone, and your job is to create an environment where that greatness can emerge."The goal of EMPOWERED is to provide you, as a leader of product management, product design, or engineering, with everything you'll need to create just such an environment.As partners at The Silicon Valley Product Group, Marty Cagan and Chris Jones have long worked to reveal the best practices of the most consistently innovative companies in the world. A natural companion to the bestseller INSPIRED, EMPOWERED tackles head-on the reason why most companies fail to truly leverage the potential of their people to innovate: product leadership.The book covers:what it means to be an empowered product team, and how this is different from the "feature teams" used by most companies to build technology products recruiting and coaching the members of product teams, first to competence, and then to reach their potential creating an inspiring product vision along with an insights-driven product strategy translating that strategy into action by empowering teams with specific objectives--problems to solve--rather than features to build redefining the relationship of the product teams to the rest of the company detailing the changes necessary to effectively and successfully transform your organization to truly empowered product teams EMPOWERED puts decades of lessons learned from the best leaders of the top technology companies in your hand as a guide. It shows you how to become the leader your team and company needs to not only survive but thrive.

    In the late 1990s, it provided an optimistic model for public

    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”

    Aging computer systems present complex technical challenges for organizations both large and small, and Kill It with Fire provides sound strategies for spearheading modernization efforts.Kill It with Fire examines aging computer systems, the evolution of technology over time, and how organizations can modernize, maintain, and future-proof their current systems.In playful and engaging prose, Marianne Bellotti uses real-world case studies to illustrate the technical challenges of modernizing complex legacy systems, as well as the organizational challenges of time-intensive maintenance efforts. The book explains how to evaluate existing architecture, create upgrade plans, and handle communication structures. Team exercises and historical analyses of complex computer systems make this a valuable resource for those in both older and newer companies, and will help readers restore or create systems built to evolve as time goes on.

    Despite his overbearing nature, Shade delights in her new role as wife and mother. When her husband suddenly dies years later, she uncovers secrets from his past—secrets so profound they derail the lives of both her and her daughter. After tragedy strikes, thirty-six-year-old Shade gains custody of her young grandson, Tyler, and moves to a small Michigan beach town where she becomes the owner of a successful bakery and café. Shade meets and falls in love with Tyler’s baseball coach, but their love for one another is doomed. Shade’s internal struggle to honor her vow to God, while denying her own desires, throws her on a path of painful redemption.

    He recruits the beautiful, resourceful Evie, but they slowly get in over their heads as they begin to suspect the proprietor of a highly prominent, far-right website. The man, already one of the most influential in Washington D.C., is about to become all-powerful: he’s just been given incriminating dirt on the President of the United States. Frankie and Evie now find themselves in a cat and mouse battle with the future of the country at stake.

    

    The biggest change comes in the growing prominence and acceptance of Agile Programming. Software Testing—A Craftsman’s Approach, Third Edition extends the combination of theory and practicality of the first two editions to include agile programming development and discusses the serious effect this emerging area is having on software testing. Extend your Knowledge of Emerging Technologies The third edition of the widely adopted text and reference book is comprised of six parts. It begins by providing the mathematical background in discrete mathematics and linear graph theory that is used in subsequent sections. The book continues to describe specification-based (functional) and code-based (structural) test development techniques, while extending this theoretical approach to less understood levels of integration and system testing. The author further develops this discussion to include object-oriented software. A completely new section relates all of the previously discussed concepts to the agile software development movement and highlights issues such as how agile and XP development environments are radically changing the role of software testers by making testing integral at every phase of the development process. Thoroughly revised and updated, Software Testing—A Craftsman’s Approach , Third Edition is sure to become a standard reference for those who need to stay up-to-date on the most recent technologies in software testing. Carrying on the tradition of previous editions, it will continue to serve as a valuable reference for software testers, developers, and engineers. Table Of Contents: PART I: A MATHEMATICAL CONTEXT A Perspective on Testing Basic Definitions Test Cases Insights from a Venn Diagram Identifying Test Cases Error and Fault Taxonomies Levels of Testing Examples Generalized Pseud

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com

    Spurred by her personal experience and extensive exploration of brain-based learning, author Marilee Sprenger explains how brain science--what we know about how the brain works--can be applied to social-emotional learning. Specifically, she addresses how to- Build strong, caring relationships with students to give them a sense of belonging. - Teach and model empathy, so students feel understood and can better understand others. - Awaken students' self-awareness, including the ability to name their own emotions, have accurate self-perceptions, and display self-confidence and self-efficacy. - Help students manage their behavior through impulse control, stress management, and other positive skills. - Improve students' social awareness and interaction with others. - Teach students how to handle relationships, including with people whose backgrounds differ from their own. - Guide students in making responsible decisions.Offering clear, easy-to-understand explanations of brain activity and dozens of specific strategies for all grade levels, Social-Emotional Learning and the Brain is an essential guide to creating supportive classroom environments and improving outcomes for all our students.

    The Agile and Scrum software development method allows creation of the game–changing software you need to grow your business - in 30 days or less. Projects that use it are three times more successful than those that don′t, and the productivity gain versus traditional "waterfall" methods has been over 100 percent on many projects.For the business manager, the entrepreneur, or IT manager, Software in 30 Days explains how this unorthodox process works, how to get started, and how to succeed. Learn powerful concepts such as the "art of the possible," "bottom–up intelligence," and why it′s good to fail early. With simple but profound shifts in thinking, you will be able to control risk, manage projects, and deliver your best work possible, faster and cheaper than ever before.

    The whirlwind of job applications, interviews, follow-up, resume building, and networking is just the beginning. What happens after you've landed the job, settled in, and begun to make a difference-where do you go from here? What if you feel stuck in what you thought would be your dream profession? New York Times bestselling author Mika Brzezinski and producer Daniela Pierre-Bravo provide an essential manual for those crucial next steps. Earn It! is a practical career guidebook that not only helps you get your foot in the door; it also shows you how to negotiate a raise, advocate for more responsibility, and figure out whether you're in the career that's right for you. A blueprint for your future success, Earn It! features insightful and inspiring interviews with leaders in media, fashion, and business, recruiters, HR, execs, and kickass young female entrepreneurs like Danielle Weisberg and Carly Zakin of theSkimm, Vimeo CEO Anjali Sud, and Jane Park, founder of the cosmetic subscription company Julep

    Concurrency and parallelism are the keys, and Seven Concurrency Models in Seven Weeks equips you for this new world. See how emerging technologies such as actors and functional programming address issues with traditional threads and locks development. Learn how to exploit the parallelism in your computer's GPU and leverage clusters of machines with MapReduce and Stream Processing. And do it all with the confidence that comes from using tools that help you write crystal clear, high-quality code. This book will show you how to exploit different parallel architectures to improve your code's performance, scalability, and resilience. Learn about the perils of traditional threads and locks programming and how to overcome them through careful design and by working with the standard library. See how actors enable software running on geographically distributed computers to collaborate, handle failure, and create systems that stay up 24/7/365. Understand why shared mutable state is the enemy of robust concurrent code, and see how functional programming together with technologies such as Software Transactional Memory (STM) and automatic parallelism help you tame it. You'll learn about the untapped potential within every GPU and how GPGPU software can unleash it. You'll see how to use MapReduce to harness massive clusters to solve previously intractible problems, and how, in concert with Stream Processing, big data can be tamed. With an understanding of the strengths and weaknesses of each of the different models and hardware architectures, you'll be empowered to tackle any problem with confidence.What You Need: The example code can be compiled and executed on *nix, OS X, or Windows. Instructions on how to download the supporting build systems are given in each chapter.

    You will be able to look over the shoulder of major coding and design experts to see problems through their eyes.This is not simply another design patterns book, or another software engineering treatise on the right and wrong way to do things. The authors think aloud as they work through their project's architecture, the tradeoffs made in its construction, and when it was important to break rules. Beautiful Code is an opportunity for master coders to tell their story. All author royalties will be donated to Amnesty International.

    But which claims are verifiable, and which are merely wishful thinking? In this book, leading thinkers such as Steve McConnell, Barry Boehm, and Barbara Kitchenham offer essays that uncover the truth and unmask myths commonly held among the software development community. Their insights may surprise you.Are some programmers really ten times more productive than others?Does writing tests first help you develop better code faster?Can code metrics predict the number of bugs in a piece of software?Do design patterns actually make better software?What effect does personality have on pair programming?What matters more: how far apart people are geographically, or how far apart they are in the org chart?Contributors include:Jorge Aranda Tom Ball Victor R. Basili Andrew Begel Christian Bird Barry Boehm Marcelo Cataldo Steven Clarke Jason Cohen Robert DeLine Madeline Diep Hakan Erdogmus Michael Godfrey Mark Guzdial Jo E. Hannay Ahmed E. Hassan Israel Herraiz Kim Sebastian Herzig Cory Kapser Barbara Kitchenham Andrew Ko Lucas Layman Steve McConnell Tim Menzies Gail Murphy Nachi Nagappan Thomas J. Ostrand Dewayne Perry Marian Petre Lutz Prechelt Rahul Premraj Forrest Shull Beth Simon Diomidis Spinellis Neil Thomas Walter Tichy Burak Turhan Elaine J. Weyuker Michele A. Whitecraft Laurie Williams Wendy M. Williams Andreas Zeller Thomas Zimmermann