Inflate, inflate and will inflate. Programmer bubbles

Not only cans, kids, and animators can blow big bubbles. We, programmers, implementers, automation engineers and project managers, do it just as well. And perhaps even more often.





But we are cooler. Under certain conditions, we are able to inflate huge pearlescent bubbles, which then do not burst for years. There is no sense from them, but ... It's beautiful!





Automation projects

Large business automation projects are the area where I personally see bubbles most often. The biggest, the most beautiful, the most expensive. And these bubbles burst extremely beautifully, leaving tons of sticky slurry on the walls and people.





No matter how hard the agile gypsies try, automation projects are still done the old fashioned way - a cascade, a waterfall, PMBOK. Flexible methods are used only where it is not scary to make mistakes. And a project worth several million wants to be "controlled".





The bubble is growing from the very beginning of the project - surveys, modeling, writing technical specifications. The customer pretends to know what he needs. The integrator pretends not to notice that the customer is pretending. All are smart, intelligent, businesslike and polite. And the bubble is growing.





Analysts write TK in one of two options. Or a list of system improvements purchased by the customer, or a description of the target state of the system, taking into account all the functionality. The customer reads, suggests corrections, nods, signs. The bubble is already a serious size. The customer continues to pretend that he has everything “under control”.





This is where the main inflators - programmers - come in. They take the technical assignment and figure it out. Our business is small - to do what is written. Is it written correctly, or is it some kind of nonsense - what do we have to do with it? The bubble, along with the costs, grows very quickly.





, . , , , , . - . , – , , . , , . .





. , . , . , – , . , .





. . . … … … , , .





. .





, , , – , , , . , – , , , , .





: , , agile . , , . , , . , .





.





– , . - « » - , .





, .. , . , . , . « ».





, , .





– , , . , . 10 – .





– , . , , . , . , , – , , . .





, , . . , « !».





, . , .





– «». , . – . , – , .





, . – . , – - . – , , , , , .





. – , . - , , , … -.





«» . , , , , , . , , « ». 3 , , .





, . « », « », « », « » .. .





«» – . , – , , .





, , , «», . , , , , .





, . . – . – .





, . . – … .








All Articles