Development through the ass
The software industry is probably the world's largest nursery of new control systems . Agile , Extreme Programming , Development Through Testing (Test Driven Development, TDD) - acronyms and frameworks continue to multiply. Why?
Someone will say: immaturity - the production of software is still a young industry and all these changes are the way to some true basics. Others say it is because people from programming just love to invent all sorts of things and can not figure it out. And I will say this: since we are going to have dozens of models, at least some of them can be honest, albeit cynical, in relation to what actually happens most of the time.
(A positive list, I am sure, exists, but here is a cynical one)
Asshole Driven Development (ADD) - any team in which the greatest moron makes all the important decisions is developing through the ass. Common sense, logic and process are thrown out the window when Mr. Bum is in the room and does what he considers necessary, no matter how silly and egocentric it is. The rules and processes may be present, but Mr. Z. violates them and people still follow him.
')
Development through cognitive dissonance (CDD) - happens in any organization where there are two or more different points of view on how to write programs. The tension between these points of view, being manifested in various meetings and individual decisions by participants on both sides of the barricades, determines the project to a greater extent than each of the points of view separately.
The technique of “Cover your ass” - the engine of most personal efforts is the desire not to get hit when it smells fried.
Development By Denial (DBD) - everyone pretends that there is a method for what is happening, and that everything is in order, whereas in reality everything is in complete disarray, and the process is gathering dust in the corner. The worse things are, the more survival depends on the denial of what is actually happening, or on isolation in its small part of the project.
Get Me Promoted Methodology (GMPM) Methodology - People write code and solve problems in order to increase their visibility, satisfy their boss’s whims and speed up their path to improvement or spacious room, no matter how far their efforts are set goals. Among other things, emergencies are allowed in order to look like a hero, creating patches that look great in the short term, but crumble to dust as soon as the person has moved on; the focus is on the work surface, not on its meaning.
Translated by Translated.By
Note translator: the original article caused quite a large response, as a result of 287 comments, which offered about 60 (according to the author) ext. methodologies, many of which are very clever (I mean, if you are interested, I can do the translation :)).
Someone will say: immaturity - the production of software is still a young industry and all these changes are the way to some true basics. Others say it is because people from programming just love to invent all sorts of things and can not figure it out. And I will say this: since we are going to have dozens of models, at least some of them can be honest, albeit cynical, in relation to what actually happens most of the time.
(A positive list, I am sure, exists, but here is a cynical one)
Asshole Driven Development (ADD) - any team in which the greatest moron makes all the important decisions is developing through the ass. Common sense, logic and process are thrown out the window when Mr. Bum is in the room and does what he considers necessary, no matter how silly and egocentric it is. The rules and processes may be present, but Mr. Z. violates them and people still follow him.
')
Development through cognitive dissonance (CDD) - happens in any organization where there are two or more different points of view on how to write programs. The tension between these points of view, being manifested in various meetings and individual decisions by participants on both sides of the barricades, determines the project to a greater extent than each of the points of view separately.
The technique of “Cover your ass” - the engine of most personal efforts is the desire not to get hit when it smells fried.
Development By Denial (DBD) - everyone pretends that there is a method for what is happening, and that everything is in order, whereas in reality everything is in complete disarray, and the process is gathering dust in the corner. The worse things are, the more survival depends on the denial of what is actually happening, or on isolation in its small part of the project.
Get Me Promoted Methodology (GMPM) Methodology - People write code and solve problems in order to increase their visibility, satisfy their boss’s whims and speed up their path to improvement or spacious room, no matter how far their efforts are set goals. Among other things, emergencies are allowed in order to look like a hero, creating patches that look great in the short term, but crumble to dust as soon as the person has moved on; the focus is on the work surface, not on its meaning.
Translated by Translated.By
Note translator: the original article caused quite a large response, as a result of 287 comments, which offered about 60 (according to the author) ext. methodologies, many of which are very clever (I mean, if you are interested, I can do the translation :)).
Source: https://habr.com/ru/post/56975/
All Articles