I build systems that survive reality.
Not demos. Not abstractions for their own sake. Systems that handle messy data, imperfect users, changing requirements, and operational pressure.
▸ Backend systems with clear state, traceable data, and strict rules ▸ Inventory, stock, FIFO, and transaction-driven logic ▸ Translating real-world business processes into deterministic software ▸ Preventing invalid actions before they become problems
I care more about correctness and durability than novelty.
▸ Every system will be misused ▸ Every edge case will eventually happen ▸ If data changes, the reason must be visible ▸ If something can be deleted, it must be recoverable
I design with failure in mind, not optimism.
▸ Backend: PHP (Laravel), GoLang, Node.js, Python, Java, C++ ▸ Database: MySQL, PostgreSQL ▸ Frontend: Next.js, React.js, Flutter ▸ Patterns: OOP, state-based workflows ▸ Additional Tools: Docker, GIT/GITHUB, DBeaver, XAMPP
Tools are choices, not identities.
▸ Buzzword-driven architecture ▸ "Move fast, fix later" systems ▸ UI that hides broken logic ▸ Code that cannot be explained end-to-end
If it can’t be reasoned about, it’s already technical debt.
I am moving toward: ▸ System architecture ▸ Product-aware engineering ▸ Building software meant to last inside real organizations
Influence comes from systems that endure, not trends.
Expect clarity, direct feedback, and strong opinions about structure.
In return, you get someone who treats your system as if it will still matter years from now.
If this resonates, we likely speak the same language.