Empfehlungen basierend auf "Enterprise Integration Patterns"

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. 

Google’s Executive Productivity Advisor offers insights on how to make the “new way of work” work for you, providing actionable steps to optimize your productivity, accomplish more, prevent burnout, and cultivate a harmonious work-life balance. Every day, tens of thousands of Google employees, from executives to interns, rely on Laura Mae Martin’s tips and best practices for how to make the most of their time. Now, with Uptime, Laura brings her unique approach to productivity and well-being to anyone who wants to be more effective and experience “calm accomplishment,” whether at work, at school, or in their own personal lives. Laura began her Google career in sales but quickly carved out a niche for herself as a productivity expert. For more than a decade, she’s been coaching Google executives and employees on how to achieve a state of “productivity Zen”—a holistic approach to conquering everything from the avalanche of emails in their inboxes to becoming the master of their own calendars and running excellent meetings. Her strategies have been widely adopted by many, including entry-level employees looking to amplify their individual impact, middle managers, and top executives working across global teams. As many of us have moved to a hybrid environment blending work and home, managing our time efficiently and remaining productive is more important than ever. In Uptime, Laura shows how to thrive no matter where you’re working, giving concrete steps that help you focus on your priorities and keep good systems, routines, and tactics in place. Uptime explains how to make technology work for you and make “feeling on top of it” your new normal. It’s a blueprint for operating at the highest levels of productivity while enhancing your own personal well-being.

Apply psychology and behavioral science to web, UX, and graphic designBehavioral science leader and CEO at The Team W, Inc., Susan M. Weinschenk, provides a guide that every designer needs, combining real science and research with practical examples on everything from font size to online interactions. With this book you'll design more intuitive and engaging apps, software, websites and products that match the way people think, decide and behave.Here are some of the questions this book will answer: What grabs and holds attention? What makes memories stick? What motivates people? How does listening to music make people feel? How do you engineer a decision? What line length for text is best? Are some fonts better than others?We design to elicit responses from people. We want them to buy something, read more, or take action of some kind. Designing without understanding what makes people act the way they do is like exploring a new city without a map: results will be haphazard, confusing, and inefficient. Increase the effectiveness of your designs by using science-backed examples on human behavior."Every once in a while, a book comes along that is so well-written, researched, and designed that I just can't put it down. That's how good 100 Things Every Designer Needs to Know About People is!"―Lynne Cooke, Clinical Assistant Professor at Arizona State University

The bestselling authors of the classic Difficult Conversations teach us how to turn evaluations, advice, criticisms, and coaching into productive listening and learningWe swim in an ocean of feedback. Bosses, colleagues, customers—but also family, friends, and in-laws—they all have “suggestions” for our performance, parenting, or appearance. We know that feedback is essential for healthy relationships and professional development—but we dread it and often dismiss it.That’s because receiving feedback sits at the junction of two conflicting human desires. We do want to learn and grow. And we also want to be accepted just as we are right now. Thanks for the Feedback is the first book to address this tension head on. It explains why getting feedback is so crucial yet so challenging, and offers a powerful framework to help us take on life’s blizzard of off-hand comments, annual evaluations, and unsolicited advice with curiosity and grace.The business world spends billions of dollars and millions of hours each year teaching people how to give feedback more effectively. Stone and Heen argue that we’ve got it backwards and show us why the smart money is on educating receivers— in the workplace and in personal relationships as well.Coauthors of the international bestseller Difficult Conversations, Stone and Heen have spent the last ten years working with businesses, nonprofits, governments, and families to determine what helps us learn and what gets in our way. With humor and clarity, they blend the latest insights from neuroscience and psychology with practical, hard-headed advice. The book is destined to become a classic in the world of leadership, organizational behavior, and education.

This completely updated volume presents the effective and practical tools you need to design great desktop applications, Web 2.0 sites, and mobile devices. You’ll learn the principles of good product behavior and gain an understanding of Cooper’s Goal-Directed Design method, which involves everything from conducting user research to defining your product using personas and scenarios. Ultimately, you’ll acquire the knowledge to design the best possible digital products and services.

From the cofounder of Square, an inspiring and entertaining account of what it means to be a true entrepreneur and what it takes to build a resilient, world-changing companyIn 2009, a St. Louis glassblowing artist and recovering computer scientist named Jim McKelvey lost a sale because he couldn't accept American Express cards. Frustrated by the high costs and difficulty of accepting credit card payments, McKelvey joined his friend Jack Dorsey (the cofounder of Twitter) to launch Square, a startup that would enable small merchants to accept credit card payments on their mobile phones. With no expertise or experience in the world of payments, they approached the problem of credit cards with a new perspective, questioning the industry's assumptions, experimenting and innovating their way through early challenges, and achieving widespread adoption from merchants small and large.But just as Square was taking off, Amazon launched a similar product, marketed it aggressively, and undercut Square on price. For most ordinary startups, this would have spelled the end. Instead, less than a year later, Amazon was in retreat and soon discontinued its service. How did Square beat the most dangerous company on the planet? Was it just luck? These questions motivated McKelvey to study what Square had done differently from all the other companies Amazon had killed. He eventually found the key: a strategy he calls the Innovation Stack.McKelvey's fascinating and humorous stories of Square's early days are blended with historical examples of other world-changing companies built on the Innovation Stack to reveal a pattern of ground-breaking, competition-proof entrepreneurship that is rare but repeatable.The Innovation Stack is a thrilling business narrative that's much bigger than the story of Square. It is an irreverent first-person look inside the world of entrepreneurship, and a call to action for all of us to find the entrepreneur within ourselves and identify and fix unsolved problems--one crazy idea at a time.

C# has matured over the past decade: It's now a rich language with generics, functional programming concepts, and support for both static and dynamic typing. This palette of techniques provides great tools for many different idioms, but there are also many ways to make mistakes. In Effective C#, Second Edition, respected .NET expert Bill Wagner identifies fifty ways you can leverage the full power of the C# 4.0 language to express your designs concisely and clearly. Effective C#, Second Edition, follows a clear format that makes it indispensable to hundreds of thousands of developers: clear, practical explanations, expert tips, and plenty of realistic code examples. Drawing on his unsurpassed C# experience, Wagner addresses everything from types to resource management to dynamic typing to multicore support in the C# language and the .NET framework. Along the way, he shows how to avoid common pitfalls in the C# language and the .NET environment. You'll learn how to Use both types of C# constants for efficiency and maintainability (see Item 2) Employ immutable data types to promote multicore processing (see Item 20) Minimize garbage collection, boxing, and unboxing (see Items 16 and 45) Take full advantage of interfaces and delegates (see Items 22 though 25) Make the most of the parallel framework (see Items 35 through 37) Use duck typing in C# (see Item 38) Spot the advantages of the dynamic and Expression types over reflection (see Items 42 and 43) Assess why query expressions are better than loops (see Item 8) Understand how generic covariance and contravariance affect your designs (see Item 29) See how optional parameters can minimize the number of method overloads (see Item 10) You're already a successful C# programmer-this book will help you become an outstanding one.

This book provides programmers with the ability to cost-effectively handle common legacy code problems without having to go through the hugely expensive task of rewriting all existing code. It describes a series of practical strategies that developers can employ to bring their existing software applications under control. The author provides useful guidance about how to use these strategies when refactoring or making functional changes to codebases. One of the book's key points is that it teaches developers to write tests that can be used to ensure they are not unintentionally changing the application as they optimize it. Examples are provided in Java, C++, and C#, and the book assumes that the reader has some knowledge of UML notation. Strategies using UML and code in C++ and Java are emphasized, while language-independent advice is delivered in sidebars and appendices for language-specific users.

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.

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.