About Me
I’m a front-end developer focused on engineering-driven building.
I care about how things are actually implemented in real projects—not just what “should” work in theory. Most of my time is spent working between Vue, modern frontend tooling, and real-world product constraints, trying to keep systems both practical and maintainable.
I tend to think like a builder more than a presenter. If something breaks, I want to understand the root cause. If something works, I want to know exactly why—and whether it will still work six months later.
What I’m building here
This site is my personal developer workspace.
It’s where I collect and refine things I’ve actually used or encountered in production work:
- Front-end implementation patterns and edge-case solutions
- Vue 3, VitePress, and modern frontend engineering setups
- Debugging stories: what went wrong, how I traced it, and how I fixed it
- Small tools, scripts, and workflow improvements that save time in practice
- Occasional notes on system design thinking and frontend architecture
Nothing here is meant to be theoretical or decorative. If it’s written down, it’s because it solved a real problem.
How I work
I prefer clarity over cleverness.
When I write or build something, I try to make sure:
- It can be understood without context switching too much
- It can be reused without rewriting everything
- It doesn’t rely on “tribal knowledge” in my head
- It stays maintainable after I move on to other things
I don’t like over-engineering, but I also don’t like shortcuts that come back to bite later. Most of the work is finding the balance between the two.
A bit of context
I’ve worked across frontend engineering and content-heavy systems, so I’m used to dealing with both structure and scale—not just UI, but also how information flows through a system.
Over time, I’ve become more interested in the “boring” parts of engineering: stability, consistency, and how small decisions compound over time.
Outside of code
Outside of development, I collect small observations from everyday life—things seen while traveling, patterns in how people use tools, and random thoughts that don’t belong in commit messages.
Sometimes they end up influencing how I design interfaces or structure systems. More often than not, they just sit there until they become useful later.
Closing
This site is not a portfolio.
It’s a working space that grows with me—one note, one fix, and one small improvement at a time.