Now this classic book has been fully updated and revised with leading-edge practices--and hundreds of new code samples--illustrating the art and science of software construction. Capturing the body of knowledge available from research, academia, and everyday commercial practice, McConnell synthesizes the most effective techniques and must-know principles into clear, pragmatic guidance. No matter what your experience level, development environment, or project size, this book will inform and stimulate your thinking--and help you build the highest quality code. Discover the timeless techniques and strategies that help you: Design for minimum complexity and maximum creativity Reap the benefits of collaborative development Apply defensive programming techniques to reduce and flush out errors Exploit opportunities to refactor--or evolve--code, and do it safely Use construction practices that are right-weight for your project Debug problems quickly and effectively Resolve critical construction issues early and correctly Build quality into the beginning, middle, and end of your project

    Not to worry: This book is the one place you can turn to find quick, non-intimidating, excellent design help. In The Non-Designer's Design Book, 2nd Edition, best-selling author Robin Williams turns her attention to the basic principles of good design and typography. All you have to do is follow her clearly explained concepts, and you'll begin producing more sophisticated, professional, and interesting pages immediately. Humor-infused, jargon-free prose interspersed with design exercises, quizzes, illustrations, and dozens of examples make learning a snap—which is just what audiences have come to expect from this best-selling author.

    Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, non-optimal applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as refactoring, these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use... until now. In Refactoring: Improving the Design of Existing Software, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process.

    The book provides not only amusement, but a commentary on how America has changed, and a celebration of those places that have been forgotten by conventional history.

    Relevant psychological principles will help you predict your viewer's emotional reaction to your photographic images, giving you more power, control, and tools for communicating your desired message. Knowing how our minds work helps photographers, graphic designers, videographers, animators, and visual communicators both create and critique sophisticated works of visual art. Benefit from this insight in your work. Topics covered in this book: gestalt grouping, memory and association, space, time, color, contours, illusion and ambiguity, morphics, personality, subliminals, critiquing photographs, and rhetoric.

    What is it that persuades us to camp outside Apple stores to be the first to buy an iPhone? Why is it that a generation ago a typewriter might have lasted someone a lifetime, but now we write on computers that we upgrade every couple of years to shinier, faster, sleeker models? Why do the clicks of some car doors sound “expensive”? Deyan Sudjic charts our relationship—both innocent and knowing—with all things designed. From the opulent excesses of the catwalk to the playfulness of an Alessi jam jar, he shows how we can be manipulated and seduced by our possessions. With scintillating wit he addresses these questions and more, exploring the reasons why every designer yearns to put a personal stamp on a chair or an adjustable lamp, and where design ends and art begins. 71 black-and-white and 5 color illustrations.

    A prescient advocate of sustainable consumption and the matchless utility of good design, Muji’s founding principle was to develop new and simple products at reasonable prices by making the best use of materials while minimizing their impact on the environment. From a humble inaugural line of eight products nearly three decades ago, the brand now sells nearly seven thousand different products in hundreds of its own stores in Asia, Europe, and North America.

    The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver!This handbook is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organisations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking.Who is this book for?The primary audience of this book are senior people involved in building software products or delivering software projects, from both business and delivery sides. This includes business sponsors and those whose responsibilities include product ownership, project oversight or portfolio management, architecture, business analysis, quality improvement and assurance and delivery. - Business people assigned to software projects will learn how to communicate their ideas better.- Senior product or project sponsors will learn how to communicate their assumptions more effectively to delivery teams, how to engage delivery teams to make better strategic decisions, and how to manage their project portfolio more effectively.- Delivery teams that are already working under the umbrella of agile or lean delivery methods, and more recently lean startup ideas, will learn how to better focus deliverables and engage business sponsors and users.- Delivery teams moving to agile or lean delivery methods will get ideas on how to address some common issues with scaling these practices, such as creating a big picture view, splitting work into small chunks that still have business value and reporting progress more meaningfully.About the authorGojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko won the 2012 Jolt Award for the best book, was voted by peers as the most influential agile testing professional in 2011, and his blog won the UK Agile Award for the best online publication in 2010. To get in touch, write to gojko@neuri.co.uk or visit http://gojko.net.

    Ideas for new businesses, solutions to the world's problems, and artistic breakthroughs are common, but great execution is rare. According to Scott Belsky, the capacity to make ideas happen can be developed by anyone willing to develop their organizational habits and leadership capability. That's why he founded Behance, a company that helps creative people and teams across industries develop these skills. Belsky has spent six years studying the habits of creative people and teams that are especially productive-the ones who make their ideas happen time and time again. After interviewing hundreds of successful creatives, he has compiled their most powerful-and often counterintuitive-practices, such as: •Generate ideas in moderation and kill ideas liberally •Prioritize through nagging •Encourage fighting within your team While many of us obsess about discovering great new ideas, Belsky shows why it's better to develop the capacity to make ideas happen-a capacity that endures over time.

    No, membership is not dead, argues author Sarah Sladek. But associations do need to change their thinking and their models. In The End of Membership As We Know It: Building the Fortune-Flipping, Must-Have Association of the Next Century, Sladek offers practical, proven ways that associations can respond to changes affecting participation such as the generational shifts in the workforce, social changes, and technology-eased access to content and community.The End of Membership As We Know It explains:How niche the new competitive advantage is Why organizational culture has an enormous impact on recruitment and retention What emerging member-prospects value and want Why and how to focus on member ROI instead of program ROI How to craft and deliver compelling benefits rather than features How to extend your reach Which emerging models are taking root and showing promise Providing numerous real-world examples along with specific guidance, The End of Membership As We Know It is a must-have guide for moving your membership model into the future.

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic." --Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." --Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling--and building--business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." --Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." --Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." --Kyle Brown, author of Enterprise Java(TM) Programming with IBM(R) WebSphere(R) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:Getting all team members to speak the same language Connecting model and implementation more deeply Sharpening key distinctions in a model Managing the lifecycle of a domain object Writing domain code that is safe to combine in elaborate ways Making complex code obvious and predictable Formulating a domain vision statement Distilling the core of a complex domain Digging out implicit concepts needed in the model Applying analysis patterns Relating design patterns to the model Maintaining model integrity in a large system Dealing with coexisting models on the same project Organizing systems with large-scale structures Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

    Did you design your system to survivef a sudden rush of visitors from Digg or Slashdot? Or an influx of real world customers from 100 different countries? Are you ready for a world filled with flakey networks, tangled databases, and impatient users?If you're a developer and don't want to be on call for 3AM for the rest of your life, this book will help.In Release It!, Michael T. Nygard shows you how to design and architect your application for the harsh realities it will face. You'll learn how to design your application for maximum uptime, performance, and return on investment.Mike explains that many problems with systems today start with the design.

    Weaving storytelling with masses of new and updated research, Richard Florida traces the fundamental theme that runs through a host of seemingly unrelated changes in American society: the growing role of creativity in our economy. Just as William Whyte's 1956 classic The Organization Man showed how the organizational ethos of that age permeated every aspect of life, Florida describes a society in which the creative ethos is increasingly dominant. Millions of us are beginning to work and live much as creative types like artists and scientists always have-with the result that our values and tastes, our personal relationships, our choices of where to live, and even our sense and use of time are changing. Leading the shift are the nearly 38 million Americans in many diverse fields who create for a living-the Creative Class. The Rise of the Creative Class chronicles the ongoing sea of change in people's choices and attitudes, and shows not only what's happening but also how it stems from a fundamental economic change. The Creative Class now comprises more than thirty percent of the entire workforce. Their choices have already had a huge economic impact. In the future they will determine how the workplace is organized, what companies will prosper or go bankrupt, and even which cities will thrive or wither.

    In this compact volume, Koolhaas addresses the urban and architectural implications of extra-large construction, using as examples three of OMA's important large-scale projects: the Zeebrugge Ferry Terminal in Belgium, the Tres Grande Bibliotheque in Paris, and the Karlsruhe Center for Art and Media Technology in Germany.Tackling questions about the difficult state of urbanism and modernism in contemporary Europe, America, and Asia, this slim volume forms a concise and coherent explanation of the theories and polemics of Koolhaas and OMA. This beautifully designed book serves as an inexpensive alternative and companion to Koolhaas's recent "S, M, L, XL."