enow.com Web Search

Search results

1. Results from the WOW.Com Content Network

2. Martin Fowler (software engineer) - Wikipedia

   en.wikipedia.org/wiki/Martin_Fowler_(software...

   Martin Fowler (18 December 1963) is a British software developer, [2] author and international public speaker on software development, specialising in object-oriented analysis and design, UML, patterns, and agile software development methodologies, including extreme programming. His 1999 book Refactoring popularised the practice of code ...

3. William Opdyke - Wikipedia

   en.wikipedia.org/wiki/William_Opdyke

   Refactoring: Improving the Design of Existing Programs. Opdyke, William F., and Ralph E. Johnson. "Creating abstract superclasses by refactoring." Proceedings of the 1993 ACM conference on Computer science. ACM, 1993. [5] Johnson, Ralph E., and William F. Opdyke. "Refactoring and aggregation." Object Technologies for Advanced Software.

4. Code refactoring - Wikipedia

   en.wikipedia.org/wiki/Code_refactoring

   In computer programming and software design, code refactoring is the process of restructuring existing source code—changing the factoring—without changing its external behavior. Refactoring is intended to improve the design, structure, and/or implementation of the software (its non-functional attributes), while preserving its functionality .

5. Rule of three (computer programming) - Wikipedia

   en.wikipedia.org/wiki/Rule_of_three_(computer...

   It states that two instances of similar code do not require refactoring, but when similar code is used three times, it should be extracted into a new procedure. The rule was popularised by Martin Fowler in Refactoring [1] and attributed to Don Roberts. Duplication is considered a bad practice in programming because it makes the code harder to ...

6. Design smell - Wikipedia

   en.wikipedia.org/wiki/Design_Smell

   In computer programming, a design smell is a structure in a design that indicates a violation of fundamental design principles, and which can negatively impact the project's quality. [1] The origin of the term can be traced to the term "code smell" which was featured in the book Refactoring: Improving the Design of Existing Code by Martin ...

7. Elliotte Rusty Harold - Wikipedia

   en.wikipedia.org/wiki/Elliotte_Rusty_Harold

   Java I/O, Second Edition (O'Reilly, 2006), ISBN 0-596-52750-0 Refactoring HTML: Improving the Design of Existing Web Applications (Addison-Wesley Professional, 2012), ISBN 0-321-50363-5 Java Network Programming, Fourth Edition (O'Reilly, 2013), ISBN 1-449-35767-9

8. Code smell - Wikipedia

   en.wikipedia.org/wiki/Code_smell

   [1] [2] Determining what is and is not a code smell is subjective, and varies by language, developer, and development methodology. The term was popularized by Kent Beck on WardsWiki in the late 1990s. [3] Usage of the term increased after it was featured in the 1999 book Refactoring: Improving the Design of Existing Code by Martin Fowler. [4]

9. Outline of software engineering - Wikipedia

   en.wikipedia.org/wiki/Outline_of_software...

   Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts. ISBN 0-201-48567-2; The Pragmatic Programmer: from journeyman to master by Andrew Hunt, and David Thomas. ISBN 0-201-61622-X; Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR 19759