Empfehlungen basierend auf "The Great Mental Models: Systems and Mathematics"

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, who has helped bring agile principles from a practitioner's point of view to tens of thousands of programmers, 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 software craftsman, and make you a better programmerbut only if you work at it.What kind of work will you be doing? You'll be reading codelots 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 codeof 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 understandingHow 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 What smells and heuristics can help you identify bad codeThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code. 

In It Doesn't Have to Be Crazy at Work, Jason Fried and David Heinemeier Hansson, founders of the trailblazing software company Basecamp, reveal a bold, iconoclastic strategy for creating the ideal company culture, directly attacking the chaos, anxiety and stress that hamper billions of workers every day.Enduring long hours, carrying excessive workloads and functioning with a lack of sleep have become badges of honour for modern professionals. But these realities should be marks of stupidity, the authors argue. The answer to better productivity isn't more hours – it's less waste and fewer things that induce distraction and persistent stress. It's time to stop celebrating 'crazy' and start celebrating 'calm'.

  Capturing a wealth of experience about the design of object-oriented software, four top-notch designers present a catalog of simple and succinct solutions to commonly occurring design problems. Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves. The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently.  

The Law of Market Failure: Most new products will fail in the market, even if competently executed.Using his experience at Google, his remarkable success as an entrepreneur and consultant, and insights from his lectures at Stanford University and Google, Alberto Savoia’s The Right It offers an unparalleled approach to beating the beast that is market failure.Millions of people around the world are working hard to bring to life new ideas. 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”.

What makes an effective executive?The measure of the executive, Peter F. Drucker reminds us, is the ability to "get the right things done." This usually involves doing what other people have overlooked as well as avoiding what is unproductive. Intelligence, imagination, and knowledge may all be wasted in an executive job without the acquired habits of mind that mold them into results. Drucker identifies five practices essential to business effectiveness that can, and must, be learned: Managing time Choosing what to contribute to the organization Knowing where and how to mobilize strength for best effect Setting the right priorities Knitting all of them together with effective decision-makingRanging widely through the annals of business and government, Peter F. Drucker demonstrates the distinctive skill of the executive and offers fresh insights into old and seemingly obvious business situations.

Skilled at puncturing financial bubbles and other delusions of the Wall Street crowd, Burton Malkiel shows why a broad portfolio of stocks selected at random will match the performance of one carefully chosen by experts. Taking a shrewd look at the high-tech boom and its aftermath, Malkiel shows how to maximize gains and minimize losses in this era of electronic brokers, virtual gurus, and flashy investment vehicles. Learn how to analyze the potential returns, not only for stocks and bonds, but for the full range of investment opportunities, from money market accounts and real estate investment trusts to insurance, home owning, and tangible assets like gold and collectibles. Decode the rating game for mutual funds and discover the unique advantages of index mutual funds over the wide range of riskier alternatives. Year in and year out the best investing guide money can buy, this enhanced edition includes an update of Malkiel's famous "Life-Cycle Guide to Investing," showing how to match an investment strategy to your stage in life.

Totally revised and expanded to cover the newest forms of wagering and the latest handicapping theories, with examples of how to apply them, this book proves that the key to winning at the track is not in one all-powerful secret, but involves using the right tools at the right time.

In The Software Craftsman, Sandro Mancuso explains what craftsmanship means to the developer and his or her organization, and shows how to live it every day in your real-world development environment. Mancuso shows how software craftsmanship fits with and helps students improve upon best-practice technical disciplines such as agile and lean, taking all development projects to the next level. Readers will learn how to change the disastrous perception that software developers are the same as factory workers, and that software projects can be run like factories.

Twenty years after the Agile Manifesto was first presented, the legendary Robert C. Martin (Uncle Bob) reintroduces agile values and principles for a new generation of software developers. In this eagerly awaited book, the best-selling author of The Clean Coder shows how to bring unprecedented levels of professionalism and discipline to agile development — and thereby write far more effective, successful software.As with his other books, Martin's Clean Agile: Back to Basics doesn't merely present multiple choices and options, and say "use your best judgment"; it tells you what choices to make and why those choices are critical to your success. Writing in the agile context, Martin offers direct, no-nonsense answers to crucial questions:How and why did agile begin?What are the costs and benefits of agile?What are the most effective practices of agile development?How should an agile team be organized?What roles do programmers, testers, and managers play in an agile team?What is the role of the Agile Coach?What about agile for large projects?What kinds of projects benefit from agile?Clean Agile: Back to Basics is essential reading for students, programmers, managers, testers, project managers, and every software professional called upon to lead or participate in an agile project.

The Go Programming Language is the authoritative resource for any programmer who wants to learn Go. It shows how to write clear and idiomatic Go to solve real-world problems. The book does not assume prior knowledge of Go nor experience with any specific language, so you’ll find it accessible whether you’re most comfortable with JavaScript, Ruby, Python, Java, or C++. The first chapter is a tutorial on the basic concepts of Go, introduced through programs for file I/O and text processing, simple graphics, and web clients and servers. Early chapters cover the structural elements of Go programs: syntax, control flow, data types, and the organization of a program into packages, files, and functions. The examples illustrate many packages from the standard library and show how to create new ones of your own. Later chapters explain the package mechanism in more detail, and how to build, test, and maintain projects using the go tool. The chapters on methods and interfaces introduce Go’s unconventional approach to object-oriented programming, in which methods can be declared on any type and interfaces are implicitly satisfied. They explain the key principles of encapsulation, composition, and substitutability using realistic examples. Two chapters on concurrency present in-depth approaches to this increasingly important topic. The first, which covers the basic mechanisms of goroutines and channels, illustrates the style known as communicating sequential processes for which Go is renowned. The second covers more traditional aspects of concurrency with shared variables. These chapters provide a solid foundation for programmers encountering concurrency for the first time. The final two chapters explore lower-level features of Go. One covers the art of metaprogramming using reflection. The other shows how to use the unsafe package to step outside the type system for special situations, and how to use the cgo tool to create Go bindings for C libraries. The book features hundreds of interesting and practical examples of well-written Go code that cover the whole language, its most important packages, and a wide range of applications. Each chapter has exercises to test your understanding and explore extensions and alternatives. Source code is freely available for download from http://gopl.io/ and may be conveniently fetched, built, and installed using the go get command.