Human System Design

Human System Design
Photo by Martin Adams / Unsplash

As a software engineer I learned tons of jargon and definitions we use to describe what we do or pretend to do. However concepts are initially borrowed from the real life and shaped according to the needs. I think it is interesting to use these computer definitions to describe our human nature. I’m gonna try to see how it will turn out.

The main components

We used to imagine we have 2 parts: inner and outer, being our soul and body respectively. Recently I figured out it is not exactly the truth, as there are 3 components. The core, gateway and hardware layer.

Using the tech language will help other engineers to understand concepts easier, but I will make necessary comments, to be sure the structure is clear.

The Core

The Core, soul, Gods sparkle - humanity has a lot of names, that might be very close or very far from what it is. But that’s the main component, and the presence of it makes the difference between the live and death.

Our inability to capture it, investigate or explain it comes from the mismatch of the tooling we use. As everything we create operates using logic, while the Core uses feelings.

The Gateway

This is the part we think all the mystery happens. The ego or personality. In reality this looks like helpful “smart toolbox”. The coolest part - it is programmable. It has enormous even unreal potential when used the right way. Filters, proxies, rate limiters, relays, adapters, drivers! That’s the entire own world!

The Hardware

Our body is a hardware. It must be present to run the Gateway and the Core. We must power it (feed it), exercise and take care of it (maintain). Reacting properly to the signals (monitoring) is also necessary to prolong the lifetime.

About HumanOS

From the beginning of our lives our environment teaches us and shapes our Gateway. At some point we are overwhelmed with all the signals we receive and the process of degrading starts. We begin to rely on our Gateway solely. It’s like executing scripts on the edge. Responses are faster, but data may be invalid or too old. Because the real process happens at the Core level. It is the place where the response, having all the details and big picture could be generated and decision can be made.

When responses generated on the edge are not working well it’s time to focus on the “inner world” and adjust the filters, work with the traumas etc. It is obviously a good thing to fix the bugs in the Gateway software, but it does not solve all the problems. Fixing and adjusting all the filter, proxies etc. might not magically unclog the connection between the Gateway and the Core. Without that connection and proper adapters we are blind.

Since there nothing in this Universe was meant to harm us - it was meant either to teach us or to help us. Our Gateway was meant to help us, but we must control it. But when there is literally “allow all” firewall policy regarding our parents when we are child - it takes years or even decades to understand all that. And some more time to get the control back.

With the proper control fear becomes an intensive and useful signal, when processed by the Core it leads to innovation. When processed by the Gateway there are 2 possible responses: hit or run. None of them is even close to being creative or positive. Familiar, huh?

When connected to the Core it becomes possible to reprogram the Gateway on your own. That’s the reason why having a Goal is crucial. When Goal is felt - Human becomes unstoppable. When the Core, the Gateway and the Hardware are optimized towards the Goal it becomes an ultimate solution to any problem.

I used to use Apple’s devices as an example of excellent work, when hardware and software works together. It performs very well for years. But be aware and don’t trust anyone outside. The source of truth is at the Core.

Human System Design: API compatibility
When trying to adopt new tool: first of all validate if it’s compatible with your Core. Not all tools and methodologies are replaceable. This is the second part of explaining a vision of human being using software developer naming. Human System DesignAs a software engineer I learned tons of

Read next article