“No. No. No. No-no. Not good. No, no.”
“Come on, find what you need and lets get away from here. We are running out of time.”
“Can not run out of time, there is infinite time. You are finite, Zathras is finite.
This is . . . wrong tool. No. No. Not good. No. No. . . . Never use this.”
-Zathras and Ivanova
Zathras had good sense of what tool is appropriate and was a “clumper” as defined in Bruce Eckel’s Web Log entry of Aug 16, 2004.
It is both strangely comforting to know that I recognize both of the organization anti-patterns mentioned towards the end of his article, and distressing that the company in question also began to recognize it but at a far too late stage to avoid implosion.
The following description also strikes home as to the kind of thing the organization in question was building :
I have consulted on projects where the technologists decided that they want to solve a much broader problem than what was assigned, and usually it’s a disaster. In fact, I would characterize the desire to solve a bigger problem than necessary to be an important flaw in the technical management of the project, whereas a desire to “do the simplest thing that could possibly work” is an indication, to me anyway, of a depth of understanding of how hard it is to just get something working, and how likely it is that you’ll fail.
– Bruce Eckel’s Web Log entry of Jan 1, 2004
I must try to recognize this stuff earlier and try harder to effect change or activate my trapdoor escape plan earlier if corrective change does not appear relatively soon. I was far too long in that unhealthy work environment. (Bad for stress, bad for career … other than “it was a learning experience” euphamism)
Next time . . .