Imagine how future archaeologists will discover countless things we have thrown away: plastic and metal objects, discarded electronics, synthetic textiles, and other items that do not easily decompose; the leftovers of an age of rampant, imperishable objects. Today, in an economic system that revolves around producing and consuming such things, we now face how to deal with them in the challenges that lie ahead. The intrinsic design ideologies of sustainability and social responsibility are often not new. This book presents a history of socially committed design strategies within the Western tradition.

Object technology pioneer Wirfs-Brock teams with expert McKean to present a thoroughly updated, modern, and proven method for the design of software. The book is packed with practical design techniques that enable the practitioner to get the job done.

Do modern programming languages, IDEs, and libraries make coding easy? Maybe, but coding is not design. Large-scale or expensive apps clearly require evaluation of design choices. Still, software design directly impacts code reuse and longevity even for small-scale apps with limited overhead. This text evaluates and contrasts common object-oriented designs. A given problem may have many solutions. A developer may employ different design techniques – composition, inheritance, dependency injection, delegation, etc. – to solve a particular problem. A skilled developer can determine the costs and benefits of different design responses, even amid competing concerns. A responsible developer documents design choices as a contract with the client, delineating external and internal responsibilities. To promote effective software design, this book examines contractual, object-oriented designs for immediate and sustained use as well as code reuse. The intent of identifying design variants is to recognize and manage conflicting goals such as short versus long-term utility, stability versus flexibility, and storage versus computation. Many examples are given to evaluate and contrast different solutions and to compare C# and C++ effects. No one has a crystal ball; however, deliberate design promotes software longevity. With the prominence of legacy OO code, a clear understanding of different object-oriented designs is essential. Design questions abound. Is code reuse better with inheritance or composition? Should composition rely on complete encapsulation? Design choices impact flexibility, efficiency, stability, longevity, and reuse, yet compilers do not enforce design and syntax does not necessarily illustrate design. Through deliberate design, or redesign when refactoring, developers construct sustainable, efficient code.

The Complete Guide to Writing More Maintainable, Manageable, Pleasing, and Powerful Ruby Applications Ruby's widely admired ease of use has a downside: Too many Ruby and Rails applications have been created without concern for their long-term maintenance or evolution. The Web is awash in Ruby code that is now virtually impossible to change or extend. This text helps you solve that problem by using powerful real-world object-oriented design techniques, which it thoroughly explains using simple and practical Ruby examples. This book focuses squarely on object-oriented Ruby application design. Practical Object-Oriented Design in Ruby will guide you to superior outcomes, whatever your previous Ruby experience. Novice Ruby programmers will find specific rules to live by; intermediate Ruby programmers will find valuable principles they can flexibly interpret and apply; and advanced Ruby programmers will find a common language they can use to lead development and guide their colleagues. This guide will help you Understand how object-oriented programming can help you craft Ruby code that is easier to maintain and upgrade Decide what belongs in a single Ruby class Avoid entangling objects that should be kept separate Define flexible interfaces among objects Reduce programming overhead costs with duck typing Successfully apply inheritance Build objects via composition Design cost-effective tests Solve common problems associated with poorly designed Ruby code

Design for the Real World has, since its first appearance twenty-five years ago, become a classic. Translated into twenty-three languages, it is one of the world's most widely read books on design. In this edition, Victor Papanek examines the attempts by designers to combat the tawdry, the unsafe, the frivolous, the useless product, once again providing a blueprint for sensible, responsible design in this world which is deficient in resources and energy.

Emotionally Durable Design presents counterpoints to our ‘throwaway society’ by developing powerful design tools, methods and frameworks that build resilience into relationships between people and things. The book takes us beyond the sustainable design field’s established focus on energy and materials, to engage the underlying psychological phenomena that shape patterns of consumption and waste. In fluid and accessible writing, the author asks: why do we discard products that still work? He then moves forward to define strategies for the design of products that people want to keep for longer. Along the way we are introduced to over twenty examples of emotional durability in smart phones, shoes, chairs, clocks, teacups, toasters, boats and other material experiences. Emotionally Durable Design transcends the prevailing doom and gloom rhetoric of sustainability discourse, to pioneer a more hopeful, meaningful and resilient form of material culture. This second edition features pull-out quotes, illustrated product examples, a running glossary and comprehensive stand firsts; this book can be read cover to cover, or dipped in-and-out of. It is a daring call to arms for professional designers, educators, researchers and students from in a range of disciplines from product design to architecture; framing an alternative genre of design that reduces the consumption and waste of resources by increasing the durability of relationships between people and things.

A presentation of the formal underpinnings of object-oriented programming languages.