START FROM THE ROOT
Before reaching for a framework or architecture, I want to understand what actually needs to be solved.
#01 / IDENTITYSYS/PROFILE
// WHO IS SEPTIAN?
I BUILD END-TO-END SOFTWARE.
I TAKE
OWNERSHIP.
I like understanding why a system should exist before deciding how it should be built.
PORTRAIT_001
ID: SEPTIAN
ASSET: ACTIVE
#02
A LITTLE BACKSTORY
I started by learning how to build things that work.
Then the more useful questions showed up: Why does this process exist? Who depends on it? What problem are we actually solving? What happens when the system fails?
Those questions changed how I approach engineering. Code is still the material—but context decides whether it becomes something useful, maintainable, and worth continuing.
#03HOW
HOW
I THINK.
Three habits that keep a technical decision connected to the thing it is meant to serve.
UNDERSTAND THE PROCESS
Requirements describe what someone asks for. Understanding the process explains why it matters.
FIGURE IT OUT
If I do not know the answer yet, I research, experiment, read the documentation, and find out what actually works.
#04
THINGS YOU WON’T FIND IN MY CV
01I LIKE TO EXPERIMENT.+
A small prototype can answer a question faster than a long assumption chain.
02I ASK “WHY?” A LOT.+
It is usually the shortest route from a feature request to the problem behind it.
03I LIKE UNDERSTANDING BUSINESS PROCESSES.+
A useful system fits the way work actually happens—not only the diagram.
04I ENJOY BUILDING THINGS FROM ZERO.+
The first boundary, workflow, and deployment path shape everything that follows.
05I DON’T PANIC WHEN THE FIRST APPROACH FAILS.+
A failed approach is still information. The next one should be more informed.
// NEXT CHAPTER