The Builder Behind the Work

I Learned to Code Without a Laptop

My journey into software didn’t begin in an elite university lab or with high-end developer hardware. It began with discovering that websites could be built, writing code in Windows Notepad on shared cybercafe computers, and saving files onto tiny USB sticks.

I spent months saving and raising money just to afford my first used laptop so I could practice at night. Not long after I finally got it, the laptop was stolen. I had every rational reason to quit. Instead, that setback forced an uncompromising resilience into my DNA: constraints do not determine what you are capable of creating.

I taught myself software engineering line by line, studying system design, database indexing, and network protocols. A few years later, I was hired to teach production software development at the very technical academy whose tuition I could never afford as a beginner.

For years, I wrote software for other people's businesses. But the pivotal transformation occurred when I stopped simply being a developer for hire and stepped into the arena of product ownership. Experiencing the brutal difference between code that passes a test and software that must survive live traffic, customer support, payment gateway drops, and payroll changed how I build forever.

In 2023, years of nonstop execution culminated in severe founder burnout. Stepping back wasn't easy, but it gave me an invaluable gift: the space to examine how I work, eliminate vanity distractions, and rebuild my operating standards. In late 2025, I picked up my magic again — not out of obligation, but with crystal clarity, deeper discipline, and a profound commitment to building products that move humanity forward.

Seven Principles for Building Reality

An idea doesn’t come to life by simply believing in it. It comes to life when you develop the discipline, creativity, and technical ability to build it. Here are the core beliefs that govern everything I build and advise:

The Operator & The Rebel

My approach to technology and business is defined by two complementary archetypes:

The Operator (Primary): I have spent over a decade writing code, managing production deployments, refactoring technical debt, and navigating live outages. I don't speak in buzzwords. I share the actual engineering trade-offs, the database lock bottlenecks, and the messy behind-the-scenes realities of building products. Instead of telling people I am a builder, I let them watch me build.

The Rebel (Secondary): I reject the prevailing culture of shortcuts, inflated vanity metrics, and superficial startup hype. I challenge conventional Silicon Valley dogmas that fail in emerging markets. When everyone else says something cannot be built under local infrastructure constraints, I take it as an architectural invitation to build a better system.

How the Pieces Fit Together

To keep my work clear, coherent, and focused, my personal brand and my companies operate in harmony without competing:

Self-Mastery & Personal Standards

Talent won’t save you if you don’t have the discipline to use it. Many founders build brilliant prototypes only to sabotage their companies through emotional volatility, lack of focus, or undisciplined habits.

I believe that before you can lead an engineering team or carry the weight of a commercial product, you must learn to govern yourself. That means holding uncompromising personal standards, cultivating cognitive clarity, mastering your physical and mental energy, and showing up with relentless consistency every single day.

Art, Storytelling & Music (Zahavii)

Engineering and creativity are not opposing forces; they are reflections of the same impulse to bring something out of nothing. Beyond software architecture, I write music, poetry, and narrative art under the moniker Zahavii.

Composing music demands the same discipline as architecting distributed systems: understanding timing, harmony, rhythm, and tension. It sharpens my taste, enriches my product storytelling, and keeps my imagination expansive.