𝔖 Scriptorium
✦   LIBER   ✦

πŸ“

Antipatterns. Refactoring Software, Archtectures and Projects in Crisis

✍ Scribed by William J. Brown, Raphael C. Malveau, Hays W. "Skip" McCormick, Thomas J. Mowbray


Publisher
Wiley
Year
1998
Tongue
English
Leaves
157
Edition
1
Category
Library

⬇  Acquire This Volume

No coin nor oath required. For personal study only.

✦ Synopsis


If patterns are good ideas that can be re-applied to new situations, AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis looks at what goes wrong in software development, time and time again. This entertaining and often enlightening text defines what seasoned developers have long suspected: despite advances in software engineering, most software projects still fail to meet expectations - and about a third are cancelled altogether. The authors of AntiPatterns draw on extensive industry experience, their own and others, to help define what's wrong with software development today. They outline reasons why problem patterns develop (such as sloth, avarice, and greed) and proceed to outline several dozen patterns that can give you headaches or worse.Their deadliest hit list begins with the Blob, where one object does most of the work in a project, and Continuous Obsolescence, where technology changes so quickly that developers can't keep up. Some of the more entertaining antipatterns include the Poltergeist (where do-nothing classes add unnecessary overhead), the Boat Anchor (a white elephant piece of hardware or software bought at great cost) and the Golden Hammer (a single technology that is used for every conceivable programming problem). The authors then proceed to define antipatterns oriented toward management problems with software (including Death by Planning and Project Mismanagement, along with several miniature antipatterns, that help define why so many software projects are late and overbudget).The authors use several big vendors' technologies as examples of today's antipatterns. Luckily, they suggest ways to overcome antipatterns and improve software productivity in "refactored solutions" that can overcome some of these obstacles. However, this is a realistic book, a mix of "Dilbert" and software engineering. A clever antidote to getting too optimistic about software development, AntiPatterns should be required reading for any manager facing a large-scale development project.

✦ Subjects


Π‘ΠΈΠ±Π»ΠΈΠΎΡ‚Π΅ΠΊΠ°;ΠšΠΎΠΌΠΏΡŒΡŽΡ‚Π΅Ρ€Π½Π°Ρ Π»ΠΈΡ‚Π΅Ρ€Π°Ρ‚ΡƒΡ€Π°;ΠšΡƒΠ»ΡŒΡ‚ΡƒΡ€Π° ΠΈ искусство программирования;


πŸ“œ SIMILAR VOLUMES


Antipatterns: Identification, Refactorin
✍ Phillip A. Laplante, Colin J. Neill πŸ“‚ Library πŸ“… 2005 πŸ› Auerbach Publications 🌐 English

<b>AntiPatterns: Identification, Refactoring, and Management catalogs 48 bad management practices and environments common to software development, IT, and other organizations. The authors cover antipatterns of management, along with environmental/cultural antipatterns and personality antipatterns/p

Refactoring in Large Software Projects
✍ Martin Lippert, Stephen Roock πŸ“‚ Library πŸ“… 2006 πŸ› John Wiley & Sons 🌐 English

Large Refactorings looks at methods of establish design improvements as an important and independent activity during development of software, and will help to ensure that software continues to adapt, improve and remain easy to read and modify without altering its observable behaviour. It provides re

Antipatterns: Identification, Refactorin
✍ Phillip A. Laplante, Colin J. Neill πŸ“‚ Library πŸ“… 2006 πŸ› Auerbach Publications 🌐 English

AntiPatterns: Identification, Refactoring, and Management catalogs 48 bad management practices and environments common to software development, IT, and other organizations. The authors cover antipatterns of management, along with environmental/cultural antipatterns and personality antipatterns/pheno

Antipatterns: Identification, Refactorin
✍ Phillip A. Laplante, Colin J. Neill πŸ“‚ Library πŸ“… 2005 πŸ› Auerbach Publications 🌐 English

Antipatterns are conventional problem-solution pairs in software engineering that do more harm than good, and three general types were identified by Brown and colleagues in their groundbreaking Antipatterns (1998): architectural, design, and management. Laplante and Neill (both software engineering,