PSYCHOTHERAPY AS TECHNOLOGY STACK UPDATE AND CODE REFACTORING

The human psyche is like a legacy system. Developed by who knows when and not always by who. The source code is confusing and lacks commentary. The language is outdated. The architecture is not well thought out. The logic is hidden and not obvious. There are crutches sticking out here and there to make this design work somehow.

Consequences of habitual actions are not always predictable - you pressed a button on the toaster, it responded with fireworks and sent an invitation to tea to your ex.

You apply to the registry office, and the system generates a critical error and formats all available discs. So you wake up in Saratov, in a hotel, in the most expensive room overlooking the Volga, in the arms of an Angora goat, in the bathroom locked Filipino stripper, under the sofa curled up royal python.

Having tortured yourself in this way for the first 25-30 years of your life, you start looking for a universal system architect. One who has eaten his dog on these legacy systems. And preferably two.

Then you work together step by step for the next couple of years to write the specification, build ER diagrams, make a user manual and rewrite especially confusing parts.

In about five years you can already boast of a new-fangled data storage in the cloud, a freshly developed system and regular releases. You think about becoming a universal architect yourself.

Why - you have experience, you have knowledge, and there is an unploughed field of obsolete systems around. Study, get certified - voila.

It's exactly the same in psychotherapy.