From Accenture to Web3: Why I Made the Jump
I spent four years at Accenture building enterprise software. It was the right move at the time — I learned how large systems work, how to navigate corporate codebases with millions of lines, and how to ship software that thousands of people depend on daily. But by year three, I knew I wanted something different.
The Enterprise Trap
Enterprise development is optimized for reliability and process. That is its strength and its limitation. Every change goes through layers of review, every feature has a business case, every deployment has a rollback plan. You learn discipline, but you lose speed.
Discovering Web3
Web3 was the opposite. When I started exploring decentralized applications, I was struck by how much the culture reminded me of the early web — scrappy, experimental, moving fast and sometimes breaking things. The technology was rough around the edges, but the ideas were compelling.
Making the jump was not easy. I traded the predictability of corporate life for the chaos of building on my own. But even though the money was better, the real gain was something else: the feeling of building on a frontier. Every project taught me something new because the playbook had not been written yet.
Two Years Later
Two years later, I do not regret the decision. I have shipped products that would have taken quarters to approve in enterprise. I have learned more about cryptography, distributed systems, and token economics than I ever would have in a corporate role. And I wake up excited to work, which is worth more than any salary bump.
Keep Reading
The State of Web Development: A Talk for Students
→Notes from my university talk about modern web development, AI impact on developers, and practical career advice.
The System Is Rigged Against Small Builders
→I got suspended by Meta for no reason. Twitter Ads delivered 122 impressions for the same budget that got me 27,000 on Meta. The ad platforms are broken for indie builders.