You enter in a bank and at your time the systems went down, then some "emergency tasks" are taken into action like "boot the server" run code XX or YY, that same "bla bla bla" and the things remains for tomorrow, nobody on that place had any fault, a communication breakdown occurred "national level" then some phone calls and in the mean time the attender try to "start to explain something", the resume was "no thank you" good that you talk using codes.
And all that "workflow" and systems "x, y, z" to process some activity that is "obscure", this is "the resume" of several "contractors" and hypothesis fired to solve a problem using "tuple like structures" on flat tables, then came the ESB "let's idealize a tunnel" and on this tunnel the information will flow from point to point and at end some process will be finished. But on theory just a small letter shall be approved at a certain date and some paper work done.
Because you know, since you worked on similar systems you don't want to come back, such approaches are the "reuse" of trash that have some "historical log inside", then you have to watch the apocalyptic process happens now as a "customer" but what is interesting when you inspect the codes is like "such guy never programmed on his life" but put all that marketing of for example "extreme programming", because spend a lot of time looking for concepts that were thrown just like any hypothesis generation, isn't interesting like "what is the chance" that you have a simple task to run "once in your life" and then something went wrong, and just observing you check some wrong tasks to solve a problem that "isn't there"? And what is bad, all that "bad memories" come back, like "the jerks", the bad design and all the bugs because someone try to "promote a fallacy"?
