I look for root causes, dependencies, and practical fixes. At 18, I found an old electronics repair book that made the logic of systems feel visible. Later I studied electronics at Rex Electronics and built a foundation in resistors, capacitors, diodes, transistors, and integrated circuits. I built an AM/FM radio, a telephone, and my first computer in 1996 during the DOS era.
What the work taught me
My first professional work reinforced that mindset. I watched technicians solve problems that others could not, and I realized my strength was not only writing code. My strength was finding what was broken, understanding why, and building a workable solution.
I became a problem solver first and a developer second.
Career shape
I moved through DOS, Windows, cloud, and mobile systems. I also helped people work through applications, spreadsheets, and documentation workflows, which taught me how technology actually behaves in daily use.
What changed
Around 2015, no-code platforms made the full stack feel visible to me: UI, logic, and data as one system. Later, AI tools expanded that work with APIs, infrastructure automation, and modern development workflows.
How I build now
Today I build systems that combine AI-assisted development, hybrid cloud architecture, no-code and traditional development, edge computing, and human-centered design. My work reflects three principles: presence, intent, and truth.
That journey led me to REFER.OS, sovereign infrastructure ideas, and local-first systems that stay practical while still using cloud services where they add value.
Closing note
I am not defined by one language or framework. I am defined by my ability to understand complex systems, identify problems, and build practical solutions that last.