Empfehlungen basierend auf "The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It"

An instant classic, this revised and updated edition of the phenomenal bestseller dispels the myths about starting your own business. Small business consultant and author Michael E. Gerber, with sharp insight gained from years of experience, points out how common assumptions, expectations, and even technical expertise can get in the way of running a successful business. Gerber walks you through the steps in the life of a business—from entrepreneurial infancy through adolescent growing pains to the mature entrepreneurial perspective: the guiding light of all businesses that succeed—and shows how to apply the lessons of franchising to any business, whether or not it is a franchise. Most importantly, Gerber draws the vital, often overlooked distinction between working on your business and working in your business. The E-Myth Revisited will help you grow your business in a productive, assured way.

“Our job as Scrum professionals is to continually improve our ability to use Scrum to deliver products and services that help customers achieve valuable outcomes. This book will help you to improve your ability to apply Scrum.” –From the Foreword by Ken Schwaber, co-author of Scrum Mastering Professional Scrum is for anyone who wants to deliver increased value by using Scrum more effectively. Leading Scrum practitioners Stephanie Ockerman and Simon Reindl draw on years of Scrum training and coaching to help you return to first principles and apply Scrum with the professionalism required to achieve its transformative potential. The authors aim to help you focus on proven Scrum approaches for improving quality, getting and using fast feedback, and becoming more adaptable, instead of “going through the motions” and settling for only modest improvements. Whether you’re a Scrum Master, Development Team member, or Product Owner, you’ll find practical advice for facing challenges with transparency and courage, overcoming a wide array of common challenges, and continually improving your Scrum practice. Realistically assess your current Scrum practice, and identify areas for improvement Recognize what a great Scrum Team looks like and get there Focus on “Done”–not “sort-of-Done” or “almost-Done” Measure and optimize the value delivered by every Product Increment Improve the way you plan, develop, and grow Clear away wider organizational impediments to agility and professionalism Overcome common misconceptions that stand in the way of progress Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

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.

How inclusive methods can build elegant design solutions that work for all.Sometimes designed objects reject their users: a computer mouse that doesn't work for left-handed people, for example, or a touchscreen payment system that only works for people who read English phrases, have 20/20 vision, and use a credit card. Something as simple as color choices can render a product unusable for millions. These mismatches are the building blocks of exclusion. In Mismatch, Kat Holmes describes how design can lead to exclusion, and how design can also remedy exclusion. Inclusive design methods—designing objects with rather than for excluded users—can create elegant solutions that work well and benefit all.Holmes tells stories of pioneers of inclusive design, many of whom were drawn to work on inclusion because of their own experiences of exclusion. A gamer and designer who depends on voice recognition shows Holmes his “Wall of Exclusion,” which displays dozens of game controllers that require two hands to operate; an architect shares her firsthand knowledge of how design can fail communities, gleaned from growing up in Detroit's housing projects; an astronomer who began to lose her eyesight adapts a technique called “sonification” so she can “listen” to the stars.Designing for inclusion is not a feel-good sideline. Holmes shows how inclusion can be a source of innovation and growth, especially for digital technologies. It can be a catalyst for creativity and a boost for the bottom line as a customer base expands. And each time we remedy a mismatched interaction, we create an opportunity for more people to contribute to society in meaningful ways.

Economics is not a field that is known for good writing. Charts, yes. Sparkling prose, no.Except, that is, when it comes to Deirdre Nansen McCloskey. Her conversational and witty yet always clear style is a hallmark of her classic works of economic history, enlivening the dismal science and engaging readers well beyond the discipline. And now she’s here to share the secrets of how it’s done.Economical Writing is itself economical: a collection of thirty-five pithy rules for making your writing clear, concise, and effective. Proceeding from big-picture ideas to concrete strategies for improvement at the level of the paragraph, sentence, or word, McCloskey shows us that good writing, after all, is not just a matter of taste—it’s a product of adept intuition and a rigorous revision process. Debunking stale rules, warning us that “footnotes are nests for pedants,” and offering an arsenal of readily applicable tools and methods, she shows writers of all levels of experience how to rethink the way they approach their work, and gives them the knowledge to turn mediocre prose into magic.At once efficient and digestible, hilarious and provocative, Economical Writing lives up to its promise. With McCloskey as our guide, it’s impossible not to see how any piece of writing—on economics or any other subject—can be a pleasure to read.

The definitive playbook by the pioneers of Growth Hacking, one of the hottest business methodologies in Silicon Valley and beyond.It seems hard to believe today, but there was a time when Airbnb was the best-kept secret of travel hackers and couch surfers, Pinterest was a niche web site frequented only by bakers and crafters, LinkedIn was an exclusive network for C-suite executives and top-level recruiters, Facebook was MySpace’s sorry step-brother, and Uber was a scrappy upstart that didn’t stand a chance against the Goliath that was New York City Yellow Cabs.So how did these companies grow from these humble beginnings into the powerhouses they are today? Contrary to popular belief, they didn’t explode to massive worldwide popularity simply by building a great product then crossing their fingers and hoping it would catch on. There was a studied, carefully implemented methodology behind these companies’ extraordinary rise. That methodology is called Growth Hacking, and it’s practitioners include not just today’s hottest start-ups, but also companies like IBM, Walmart, and Microsoft as well as the millions of entrepreneurs, marketers, managers and executives who make up the community of Growth Hackers.Think of the Growth Hacking methodology as doing for market-share growth what Lean Start-Up did for product development, and Scrum did for productivity. It involves cross-functional teams and rapid-tempo testing and iteration that focuses customers: attaining them, retaining them, engaging them, and motivating them to come back and buy more.An accessible and practical toolkit that teams and companies in all industries can use to increase their customer base and market share, this book walks readers through the process of creating and executing their own custom-made growth hacking strategy. It is a must read for any marketer, entrepreneur, innovator or manger looking to replace wasteful big bets and "spaghetti-on-the-wall" approaches with more consistent, replicable, cost-effective, and data-driven results.

* Provides engineers with a thorough understanding of how the architecture works by giving detailed information on the processor architecture, including programmer’s model instruction set and interrupt handling * Many examples of programming the Cortex-M0, in both C language and assembly language, gives engineers the ‘up-and-running’ they are looking for, quickly * Information on the software development flow including examples from various development tools for optimum efficiency * Information regarding software porting from other processor architectures including other ARM processors This is the first book to explain ARM’s new Cortex M0 architecture and how to program it from ARM’s leading engineer, Joseph Yiu, author of the successful The Definitive Guide to the ARM Cortex-M3. As well as being packed with examples on how to use the M0 architecture, the book gives detailed information on the processor architecture, an overview of the software development flow, and information on how to locate problems in the program code and software porting. This book is ideal for embedded software developers, embedded product designers, students taking an embedded systems design course where the Arm Cortex- M0 is used, and electronics hobbyists.The first and definitive book on the new ARM Cortex-M0 architecture targeting the large 8-bit and 16-bit microcontroller marketExplains the Cortex-M0 architecture and how to program it using practical examplesWritten by an engineer at ARM who was heavily involved in its development

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.

In The Clean Coder: A Code of Conduct for Professional Programmers, legendary software expert Robert C. Martin introduces the disciplines, techniques, tools, and practices of true software craftsmanship. This book is packed with practical advice–about everything from estimating and coding to refactoring and testing. It covers much more than technique: It is about attitude. Martin shows how to approach software development with honour, self-respect, and pride; work well and work clean; communicate and estimate faithfully; face difficult decisions with clarity and honesty; and understand that deep knowledge comes with a responsibility to act. Readers will learn What it means to behave as a true software craftsman How to deal with conflict, tight schedules, and unreasonable managers How to get into the flow of coding, and get past writer’s block How to handle unrelenting pressure and avoid burnout How to combine enduring attitudes with new development paradigms How to manage your time, and avoid blind alleys, marshes, bogs, and swamps How to foster environments where programmers and teams can thrive When to say “No”–and how to say it When to say “Yes”–and what yes really means

The Complete Guide to Avoiding and Fixing Common Rails 3 Code and Design Problems As developers worldwide have adopted the powerful Ruby on Rails web framework, many have fallen victim to common mistakes that reduce code quality, performance, reliability, stability, scalability, and maintainability. Rails™ AntiPatterns identifies these widespread Rails code and design problems, explains why they’re bad and why they happen—and shows exactly what to do instead. The book is organized into concise, modular chapters—each outlines a single common AntiPattern and offers detailed, cookbook-style code solutions that were previously difficult or impossible to find. Leading Rails developers Chad Pytel and Tammer Saleh also offer specific guidance for refactoring existing bad code or design to reflect sound object-oriented principles and established Rails best practices. With their help, developers, architects, and testers can dramatically improve new and existing applications, avoid future problems, and establish superior Rails coding standards throughout their organizations. This book will help you understand, avoid, and solve problems with Model layer code, from general object-oriented programming violations to complex SQL and excessive redundancy Domain modeling, including schema and database issues such as normalization and serialization View layer tools and conventions Controller-layer code, including RESTful code Service-related APIs, including timeouts, exceptions, backgrounding, and response codes Third-party code, including plug-ins and gems Testing, from test suites to test-driven development processes Scaling and deployment Database issues, including migrations and validations System design for “graceful degradation” in the real world