Living as a Modular Human
[Incident Report 202X-XX-XX]
Symptoms — From Friday evening to Sunday night, a heavy silence filled the house. Even when the child smiled and babbled, the subject responded with a blank stare.
Root Cause Analysis — A communication mishap and a reprimand from a superior occurred at 4:00 PM on Friday. These unresolved issues continued to run as a background process throughout the weekend.
Impact — Depression from the [Work] module caused a Cascading Failure into the [Home] module. This resulted in severe performance degradation of the entire Weekend system.
My life used to be a typical Monolithic structure.
In software, a monolithic architecture means every function is lumped together into one giant block of code. User registration, payments, and shipping tracking all run in the same pot. It is simple to design at first, but it has a fatal flaw. If a small error occurs in the payment module, it can paralyze the completely unrelated registration function and eventually bring the entire server down.
My life was exactly like that.
If a project went wrong or I was scolded by my boss, that depression did not stop at the subway ride home. It hovered over the living room all weekend. I could not smile when I met friends. Even while eating delicious food, my head was filled with worries about how to fix things on Monday.
A structure where my wife and child have to walk on eggshells because I am unhappy is a dangerous system. It holds my loved ones hostage to my mood. I decided to refactor my life not just for myself, but to protect the people I love.
Just as modern IT companies break down massive services into a Microservices Architecture (MSA), I began the work of splitting myself into several independent services.
The core of MSA is Isolation and the Circuit Breaker.
A ship does not sink just because there is a hole in the hull. This is because the interior is divided by multiple bulkheads. If one compartment floods, the watertight doors are immediately sealed. That specific compartment may be lost, but the ship as a whole is saved.
I applied this exact principle to my relationships.
I no longer define myself as a single persona. Instead, I am an operating system that runs different Docker containers depending on the context.
1. Corporate Worker Matt Park (Container A)
Role — A player who proves his worth in fierce competition and survives according to organizational logic.
Feature — Efficiency and speed are paramount. Sometimes, swallowing pride and enduring politics is required.
Policy — The logs for this container are complex and full of stress. I input the "Stop" command immediately upon leaving work to unload it from memory.
2. Dad and Husband Matt Park (Container B)
Role — An affectionate guardian who plays with his child and a companion who listens to his wife’s day.
Firewall — I set up a strong firewall so that data regarding work mistakes cannot ingress into this container. This must be a Clean Zone.
3. Artist Matt Park (Container C)
Role — An ego that plays jazz piano and practices Kendo by following the rhythm of sensation rather than logic.
Recovery — A backup power station that restores damaged self-esteem and recharges energy.
Of course, this is not easy. When a work issue is buffering in my brain on a Friday evening, genuinely laughing and playing with my child requires a high cost of Context Switching. It takes a tremendous amount of energy.
But this is not hypocrisy. It is Professional Ethics.
Just as a surgeon should not lose focus in the operating room because of personal sadness, I should not transmit my gloomy vibes to my family just because I am down about work. My family is not a trash can for my emotions. They are my most precious VIP Clients.
That is why I use my front door not just as an entrance, but as an Air Lock.
Like the intermediate chamber in a spacecraft between the contaminated zone and the clean zone, I pause before I enter the door code. I take three deep breaths to shake off the heavy air of the office. I declare to myself that I am in "Home Mode" from now on.
The sound of the door unlocking is the signal that I am logging into a new system. Washing my hands is a ritual to scrub away the residual data of the company.
Sometimes this Air Lock is not enough. On days when emotional overload threatens to crash the system, I use a Physical Circuit Breaker to secure time alone.
I head to the Kendo gym, sit at the piano, or put in my earphones to run for 30 minutes. The moment I struggle for breath and sweat pours down, the anguish in my brain is physically struck away. I rinse my brain not with the language of logic, but with the language of sensation.
Wiping away the sweat, I feel a strange sense of relief. I realize that while work is a bit tangled, my entire life is not ruined.
The [Work] compartment is flooded, but the [Home] and [Self] compartments are safe thanks to the watertight doors. The ship does not sink. It continues to sail.
This separation saves me and my relationships. The belief that other parts of life are still standing strong to support me is the true nature of Resilience.
We cannot build a perfect system. Living means things will inevitably break. Projects will fail, promotions will be missed, and relationships will be exhausting.
The important thing is not to let that failure swallow the entire system. Sadness can be shared, but it must not be allowed to propagate. That is the attitude of a responsible operator who protects their loved ones from system errors.
Today, I was mentally crushed at work again.
But as I pass through the Air Lock, I leave my contaminated clothes outside the door and run a new container.
docker run -it --name husband_and_dad loving_family_image
Connection established.
Now, I am the happiest husband and dad in the world.