How we did it:
For any feedback, any questions, any notes or just for chat - feel free to follow us on social networks
Michael C. Feathers
The average book on Agile software development describes a fairyland of greenfield projects, with wall-to-wall tests that run after every few edits, and clean & simple source code.
The average software project, in our industry, was written under some aspect of code-and-fix, and without automated unit tests. And we can't just throw this code away; it represents a significant effort debugging and maintaining. It contains many latent requirements decisions. Just as Agile processes are incremental, Agile adoption must be incremental too. No more throwing away code just because it looked at us funny.
Mike begins his book with a very diplomatic definition of "Legacy". I'l skip ahead to the undiplomatic version: Legacy code is code without unit tests.
Before cleaning that code up, and before adding new features and removing bugs, such code must be de-legacified. It needs unit tests.
To add unit tests, you must change the code. To change the code, you need unit tests to show how safe your change was.
The core of the book is a cookbook of recipes to conduct various careful attacks. Each presents a particular problem, and a relatively safe way to migrate the code towards tests.
Code undergoing this migration will begin to experience the benefits of unit tests, and these benefits will incrementally make new tests easier to write. These efforts will make aspects of a legacy codebase easy to change.
It's an unfortunate commentary on the state of our programming industry how much we need this book.
Features the best practices in the art and science of constructing software--topics include design, applying good techniques to construction, eliminating errors, planning, managing construction activities, and relating personal character to superior software. Original. (Intermediate)
Martin Fowler, Kent Beck
Users can dramatically improve the design, performance, and manageability of object-oriented code without altering its interfaces or behavior. "Refactoring" shows users exactly how to spot the best opportunities for refactoring and exactly how to do it, step by step.
Robert C. Martin
Written by a software developer for software developers, this book is a unique collection of the latest software development methods. The author incudes OOD, UML, Design Patterns, Agile and XP methods with a detailed description of a complete software design for reusable programs in C++ and Java. Using a practical, problem-solving approach, it shows how to develop an object-oriented application -- from the early stages of analysis, through the low-level design and into the implementation. Walks readers through the designer's thoughts — showing the errors, blind alleys, and creative insights that occur throughout the software design process. Covers: Statics and Dynamics; Principles of Class Design; Complexity Management; Principles of Package Design; Analysis and Design; Patterns and Paradigm Crossings. Explains the principles of OOD, one by one, and then demonstrates them with numerous examples, completely worked-through designs, and case studies. Covers traps, pitfalls, and work arounds in the application of C++ and OOD and then shows how Agile methods can be used. Discusses the methods for designing and developing big software in detail. Features a three-chapter, in-depth, single case study of a building security system. For Software Engineers, Programmers, and Analysts who want to understand how to design object oriented software with state of the art methods.
Illustrating some of the most common misconceptions and pitfalls software developers face using relational databases, this book helps readers use a database to produce the most efficient results, and turn sluggish, inflexible code into high-quality, reliable solutions.
Kerievsky lays the foundation for maximizing the use of design patterns by helping the reader view them in the context of refactorings. He ties together two of the most popular methods in software engineering today--refactoring and design patterns--as he helps the experienced developer create more robust software.
Chad Pytel, Tammer Saleh
How to avoid the most common code and design mistakes in Ruby on Rails applications - and refactor away problems that already exist • •A unique guide to improving Rails code quality, performance, reliability, stability, scalability, and maintainability. •Practical, proven techniques for ensuring that every new Rails application reflects today's best practices. •Highly realistic: reflects Rails mistakes and bad habits the authors have repeatedly seen 'in the wild' As millions of web developers have turned to the Ruby on Rails framework, many have fallen victim to the same mistakes, misconceptions, and bad habits. These errors can significantly reduce code quality, performance, reliability, stability, scalability, and maintainability. In some cases, they can even derail a project. In this book, these common Rails code and design problems are compiled into a complete set of AntiPatterns: what they look like, why they happen, why they're bad - and what to do instead. Every AntiPattern is illuminated with real world code, as well as specific guidance for refactoring existing bad code or design to reflect sound Object Oriented principles and established Ruby on Rails best practices. This 'cookbook' is organized into short, concise, easy-to-use chapters - each outlining a single common AntiPattern and offering detailed solutions. Until now, this information was difficult to find - and much of it wasn't available at all. Using Rails AntiPatterns, developers can dramatically improve the quality of both new and existing Rails applications; avoid future bad practices; and establish more effective Rails coding standards throughout the development organization.
Design patterns, which express relationships between recurring problems and proven solutions, have become immensely popular in the world of software development. More and more software developers are recognizing the supreme usefulness of design patterns and how they ease the design and delivery of software applications. This book builds upon the information presented in the seminal work in this field, Design Patterns: Elements of Reusable Object-Oriented Software, and gives software professionals the information they need to recognize and write their own patterns. Pattern Hatching, written by one of the co-authors of Design Patterns, truly helps the software professional apply one of the most popular concepts in software development.
A. K. Dewdney
No other volume provides as broad, as thorough, or as accessible an introduction to the realm of computers as A. K. Dewdney's The Turing Omnibus. Updated and expanded, The Turing Omnibus offers 66 concise, brilliantly written articles on the major points of interest in computer science theory, technology, and applications. New for this tour: updated information on algorithms, detecting primes, noncomputable functions, and self-replicating computers--plus completely new sections on the Mandelbrot set, genetic algorithms, the Newton-Raphson Method, neural networks that learn, DOS systems for personal computers, and computer viruses.
Bug Patterns in Java presents a methodology for diagnosing and debugging computer programs. The act of debugging will be presented as an ideal application of the scientific method. Skill in this area is entirely independent of other programming skills, such as designing for extensibility and reuse. Nevertheless, it is seldom taught explicitly. Eric Allen lays out a theory of debugging, and how it relates to the rest of the development cycle. In particular, he stresses the critical role of unit testing in effective debugging. At the same time, he argues that testing and debugging, while often conflated, are properly considered to be distinct tasks. Upon laying this groundwork, Allen then discusses various "bug patterns" (recurring relationships between signaled errors and underlying bugs in a program) that occur frequently in computer programs. For each pattern, the book discusses how to identify them, how to treat them, and how to prevent them. Table of Contents Agile Methods in a Chaotic Environment Bugs, Specifications, and Implementations Debugging and the Development Process Debugging and the Testing Process The Scientific Method of Debugging About the Bug Patterns The Rogue Tile Null Pointers Everywhere! The Dangling Composite The Null Flag The Double Descent The Liar View Saboteur Data The Broken Dispatch The Impostor Type The Split Cleaner The Fictitious Implementation The Orphaned Thread The Run-On Initialization Platform-Dependent Patterns A Diagnostic Checklist Design Patterns for Debugging References