Empfehlungen basierend auf "DK Essential Managers: Interviewing Skills"

Most startups fail. But many of those failures are preventable. The Lean Startup is a new approach being adopted across the globe, changing the way companies are built and new products are launched.Eric Ries defines a startup as an organization dedicated to creating something new under conditions of extreme uncertainty. This is just as true for one person in a garage or a group of seasoned professionals in a Fortune 500 boardroom. What they have in common is a mission to penetrate that fog of uncertainty to discover a successful path to a sustainable business.The Lean Startup approach fosters companies that are both more capital efficient and that leverage human creativity more effectively. Inspired by lessons from lean manufacturing, it relies on “validated learning,” rapid scientific experimentation, as well as a number of counter-intuitive practices that shorten product development cycles, measure actual progress without resorting to vanity metrics, and learn what customers really want. It enables a company to shift directions with agility, altering plans inch by inch, minute by minute.Rather than wasting time creating elaborate business plans, The Lean Startup offers entrepreneurs—in companies of all sizes—a way to test their vision continuously, to adapt and adjust before it’s too late. Ries provides a scientific approach to creating and managing successful startups in a age when companies need to innovate more than ever.

Most managers fail. Some 70% of employees say they are dissatisfied with their line manager. A shocking 50% are labelled as incompetent, a disappointment or a wrong hire by their co-workers. But, what do we expect when over half new managers are given no training when they are promoted? Becoming a manager isn't a progression; it's an entirely new job. Penguin Expert Series: Managing People is a manual for managers who want to succeed in their new job, motivate and direct their teams and establish a working culture where everyone wants to do their best work. The book condenses Simon Birkenhead's decades of experience working as a team leader. He reveals; what makes a good manager, highlights common pitfalls to avoid, presents his tried and tested 'four-lever framework.' With strategies to activate motivation in your team, set goals and expectations, provide feedback and coaching to building a high-performance culture, and plenty of examples from across industries, this is everything first-time managers need to succeed and be the boss that everyone wants to work for.

The foremost authority on innovation and growth presents a path-breaking book every company needs to transform innovation from a game of chance to one in which they develop products and services customers not only want to buy, but are willing to pay premium prices for. How do companies know how to grow? How can they create products that they are sure customers want to buy? Can innovation be more than a game of hit and miss? Harvard Business School professor Clayton Christensen has the answer. A generation ago, Christensen revolutionized business with his groundbreaking theory of disruptive innovation. Now, he goes further, offering powerful new insights. After years of research, Christensen has come to one critical conclusion: our long held maxim—that understanding the customer is the crux of innovation—is wrong. Customers don’t buy products or services; they "hire" them to do a job. Understanding customers does not drive innovation success, he argues. Understanding customer jobs does. The "Jobs to Be Done" approach can be seen in some of the world’s most respected companies and fast-growing startups, including Amazon, Intuit, Uber, Airbnb, and Chobani yogurt, to name just a few. But this book is not about celebrating these successes—it’s about predicting new ones. Christensen contends that by understanding what causes customers to "hire" a product or service, any business can improve its innovation track record, creating products that customers not only want to hire, but that they’ll pay premium prices to bring into their lives. Jobs theory offers new hope for growth to companies frustrated by their hit and miss efforts. This book carefully lays down Christensen’s provocative framework, providing a comprehensive explanation of the theory and why it is predictive, how to use it in the real world—and, most importantly, how not to squander the insights it provides.

This book explains the keys to successful investment and the pitfalls that can destroy capital or ruin a career. Utilizing passages from his memos to illustrate his ideas, Marks teaches by example, detailing the development of an investment philosophy that fully acknowledges the complexities of investing and the perils of the financial world. Brilliantly applying insight to today's volatile markets, Marks offers a volume that is part memoir, part creed, with a number of broad takeaways.

"A rousing manifesto of mastery in a connected world." –GoogleThe Industrial Age has taught us how to break problems into parts, but not how to build parts into solutions. We’re baffled when we’re confronted with complex challenges like recession, political gridlock, climate change, childhood obesity, pollution, and failing schools. We see them as separate ills, each requiring a separate remedy—if we can imagine a remedy at all.Why are so many jobs disappearing? Why are a few people getting rich while the rest of us struggle? How can we pay for the costs of healthcare? Why can’t our trusted institutions behave ethically? What’s the cause of governmental gridlock? How can we afford to educate our children? How do we stop damaging the ecosystem? Why do we create ugliness?Author Marty Neumeier suggests that these problems are merely symptoms of a much larger problem–our inability to deal with interconnected, non-linear, and amorphous challenges. It’s not that our problems are too difficult, he argues, but that our skills are too basic. Success in the post-industrial era demands that we move our thinking from the static, the linear, and the step-by-step to the dynamic, the holistic, and the all-at-once.In this sweeping vision for personal mastery in a post-industrial era, Neumeier presents five metaskills–feeling, seeing, dreaming, making, and learning–that can help you reach your true potential. They’ll keep you two or three steps ahead of the machines, the algorithms, and the outsourcing forces of the “robot curve”. They’ll also bring you greater creativity, higher purpose, and a deeper sense of fulfillment.Metaskills is more than a manifesto. It’s a compass for visionary leaders, policymakers, educators, and planners. It’s a creative framework for designers, engineers, scientists, and artists. It’s a picture of the future that allows people from a wide range of disciplines, industries, and professions to envision new ways to create value together. Perhaps more important, it’s a long-overdue examination of what it means to be human in the 21st century.

Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer–but only if you work at it. What kind of work will you be doing? You’ll be reading code–lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code–of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

Refactoring is about improving the design of existing code. It is the process of changing a software system in such a way that it does not alter the external behavior of the code, yet improves its internal structure. With refactoring you can even take a bad design and rework it into a good one. This book offers a thorough discussion of the principles of refactoring, including where to spot opportunities for refactoring, and how to set up the required tests. There is also a catalog of more than 40 proven refactorings with details as to when and why to use the refactoring, step by step instructions for implementing it, and an example illustrating how it works The book is written using Java as its principle language, but the ideas are applicable to any OO language.

A startup executive and investor draws on expertise developed at the premier venture capital firm Andreessen Horowitz and as an executive at Uber to address how tech's most successful products have solved the dreaded "cold start problem"--by leveraging network effects to launch and scale toward billions of users. Although software has become easier to build, launching and scaling new products and services remains difficult. Startups face daunting challenges entering the technology ecosystem, including stiff competition, copycats, and ineffective marketing channels. Teams launching new products must consider the advantages of "the network effect," where a product or service's value increases as more users engage with it. Apple, Google, Microsoft, and other tech giants utilize network effects, and most tech products incorporate them, whether they're messaging apps, workplace collaboration tools, or marketplaces. Network effects provide a path for fledgling products to break through, attracting new users through viral growth and word of mouth. Yet most entrepreneurs lack the vocabulary and context to describe them--much less understand the fundamental principles that drive the effect. What exactly are network effects? How do teams create and build them into their products? How do products compete in a market where every player has them? Andrew Chen draws on his experience and on interviews with the CEOs and founding teams of LinkedIn, Twitch, Zoom, Dropbox, Tinder, Uber, Airbnb, and Pinterest to offer unique insights in answering these questions. Chen also provides practical frameworks and principles that can be applied across products and industries. The Cold Start Problem reveals what makes winning networks thrive, why some startups fail to successfully scale, and, most crucially, why products that create and compete using the network effect are vitally important today.

How to Write Code You're Proud of . . . Every Single Day". . . [A] timely and humble reminder of the ever-increasing complexity of our programmatic world and how we owe it to the legacy of humankind--and to ourselves--to practice ethical development. Take your time reading Clean Craftsmanship. . . . Keep this book on your go-to bookshelf. Let this book be your old friend--your Uncle Bob, your guide--as you make your way through this world with curiosity and courage."--From the Foreword by Stacia Heimgartner Viscardi, CST & Agile MentorIn Clean Craftsmanship, the legendary Robert C. Martin ("Uncle Bob") has written the principles that define the profession--and the craft--of software development. Uncle Bob brings together the disciplines, standards, and ethics you need to deliver robust, effective code and to be proud of all the software you write.Robert Martin, the best-selling author of Clean Code, provides a pragmatic, technical, and prescriptive guide to the foundational disciplines of software craftsmanship. He discusses standards, showing how the world's expectations of developers often differ from their own and helping you bring the two in sync. Bob concludes with the ethics of the programming profession, describing the fundamental promises all developers should make to their colleagues, their users, and, above all, themselves.With Uncle Bob's insights, all programmers and their managers can consistently deliver code that builds trust instead of undermining it--trust among users and throughout societies that depend on software for their survival.Moving towards the "north star" of true software craftsmanship: the state of knowing how to program wellPractical, specific guidance for applying five core disciplines: test-driven development, refactoring, simple design,collaborative programming, and acceptance testsHow developers and teams can promote productivity, quality, and courageThe true meaning of integrity and teamwork among programmers, and ten specific commitments every software professional should makeRegister your book for convenient access to the book's companion videos, updates, and/or corrections as they become available. See inside book for details.

Use cases have become a very popular requirements-gathering technique, yet many developers struggle when faced with writing them. They grasp the basic concepts, but find that writing effective use cases turns out to be more difficult than they expected. One factor contributing to this difficulty is that the community lacks objective criteria for judging the quality of use cases. This new book articulates the qualities of effective use cases by applying the proven patterns concept of development to this requirements-gathering technique. The authors present a catalog of thirty-six patterns that help the reader become proficient at judging the quality of their (and other's) patterns. These patterns represent solutions to recurring problems that application developers have faced in writing use cases. Each pattern is presented with examples that help the reader understand the benefit of the pattern, and just as importantly, the consequences of ignoring its proper use.