About Me
How a person makes sense of the world says more about who they are than their resume ever could.
The logic is simple: a resume is a summary of the past, while the way you understand the world shapes the choices you will make, the opportunities you will notice, and the people you will choose to build with. One is a static label. The other is a dynamic filter. And that filter is the truer outline of a person.
I’m not the kind of person who can introduce himself with a neat, standard set of answers—name, profession, background, list of achievements. If that’s what you’re looking for, there’s already enough of it on my GitHub and X. But this is the first post on this blog, and I want to use it to answer a more fundamental question: who I am, and why you might have ended up here.
If you also find yourself jumping between disciplines, feeling that any single answer is never quite enough, always trying to connect technology, business, and philosophy into a larger picture, then we may be the same kind of person. This piece is for you.
My starting point was something I didn’t choose
One weekend in middle school, my father put a Python textbook in front of me.
He told me it would be useful. I couldn’t really argue with that, but I resisted it immediately. I looked at the syntax and the functions and had no idea what any of it was for. The tension was obvious: his reason was that it was “useful,” but I had no idea where that usefulness actually lived. When the purpose is unclear, the method becomes hard to tolerate. At the time, I hadn’t yet discovered that the real appeal of technology lies in building things with it, not in code for its own sake.
That changed later. Once I started using code to solve concrete problems, a chain of reasoning snapped into focus: code has no value by itself → code solves specific problems → solved problems improve people’s experience → better experiences create business value → and value creation is where technology ultimately finds its meaning. That was when I realized that technology matters not because it is technology, but because of what it can create, what pain points it can remove, and what realities it can change.
That naturally opened the door to business.
The boy who had been pushed into learning Python gradually developed a habit: I stopped being satisfied with any single point of view. The reason is straightforward. Every single lens simplifies. A technical lens tends to abstract away the human element. A business lens tends to abstract away the complexity of implementation. Any one perspective necessarily leaves something out. And the things I most want to understand usually only become visible when I move across multiple perspectives. Something is interesting not just because of what it is in isolation, but because of what else it connects to. Technology connects to business. Business connects to human needs. Human needs connect to deeper patterns of behavior.
That was the beginning of how I learned to see the world.
Who I am
If I had to describe myself, I wouldn’t start with what I do.
I would start with how I understand the world.
Any way of looking at a problem through a single lens makes me uneasy. The reason is that a single lens always carries an implicit assumption: that a given field has already produced a sufficiently accurate framework for understanding reality. My experience has been the opposite. Every field builds frameworks optimized for the kinds of problems that field is designed to solve. But when the problem in front of you spills across boundaries, any one framework starts to distort what you are looking at. Technology, business, economics, philosophy—I’m not committed to any one of them. They are simply some of the fragments I’m currently using to piece reality together. What matters to me is the process of exploration itself, not settling permanently in any one destination.
There is a basic cost-benefit logic behind that choice. The costs are obvious: it becomes difficult to be satisfied with ready-made answers; difficult to accept “that’s just how people think about it” at face value; difficult to glide smoothly down any well-paved path. You are always questioning, always standing at a crossroads, watching other people speed ahead on a single track while you are still trying to piece the map together. But the upside is obvious too: each new fragment of perspective makes the shape of reality a little clearer. And that kind of clarity cannot be traded for speed.
To me, that tradeoff is worth it.
Because reality is multidimensional. In a sense, that is almost tautological. If reality has many dimensions, then any one-dimensional description of it will always be incomplete. But education and professional life tend to slice the world into separate compartments, and over time we start to mistake those compartments for reality itself. We begin to act as though the world runs along disciplinary boundaries. I’m willing to live with the discomfort of resisting that illusion, because in the process of stitching those fragments back together, I get closer to something that feels true.
If you see the world this way too—not because you want to seem well-read, but because you genuinely need multiple perspectives to see clearly—then we are probably looking at the same picture.
Just from different positions.
What this blog is
To be honest, I’m not entirely sure what this blog will eventually become.
There is a logic to that honesty. If I claimed to already know its final form, I would be doing exactly the thing I distrust most: pretending to have answers I do not actually have. If I want this space to reflect a real thinking process, then I cannot act as though the script is already finished. I’m still exploring. Still forming. Still discovering, through writing, what it is I actually want to say.
This blog documents a process of exploration, not a polished set of conclusions. That distinction matters. Writing built around conclusions is optimized to help the reader get answers quickly. Writing built around process is optimized to make thinking itself visible. The first favors efficient information transfer. The second favors cognitive transparency. If you come here looking for “how to learn Python” or “the most important business trends of 2024,” you will probably be disappointed. What you will find instead is one person moving between different lenses, getting stuck on certain questions, struggling through confusion, and sometimes having to tear down his own earlier conclusions. I think that texture of real thinking is more valuable than polished certainty.
I can promise very little, but I can promise these two things.
Honesty. I will not pretend to have answers I do not have. I will tell you what I am still wrestling with, and where I may be wrong. That means you will see me make mistakes, change my mind, and admit that something I previously believed may not hold up anymore. I do not see that uncertainty as a flaw. I see it as part of being honest.
Openness. What I write here is not meant to be definitive. I welcome disagreement. I welcome being challenged. I want to hear what you see that I do not. I’m not trying to persuade you to adopt my point of view. I’m trying to create a conversation in which both your perspective and mine can be revised, sharpened, or expanded.
If you are the kind of person who believes that the act of asking better questions already has value, you may find something here that resonates.
In closing
If you’ve made it this far, thank you.
This blog is not going to be a “content product.” The logic is simple: the core function of a content product is to satisfy demand, and I’m not even fully sure what my own demand is, let alone how to precisely serve someone else’s. I’m not here to chase traffic, follow trends, or optimize headlines for metrics. I write here because I genuinely need a space to sort out my thoughts, and because I believe there are enough people in the world trying to think in a similar way—we just haven’t found each other yet.
If you are one of those people, if you are curious about where this goes, if you have thoughts of your own you want to share, question, or push against, then you are welcome here.
You can find me on X and GitHub, or reach out by email. I may not be able to reply to everything quickly, but I will read carefully.
Let’s stay in touch.