In larger companies, the people making decisions rarely deal with the consequences. That distance creates half-finished systems and short-term fixes.
We got tired of that. We wanted to build things we’d actually stand behind, where every decision mattered because we’d live with it ourselves.
Starting Hicode meant choosing clarity over cleverness. We don't chase impressive architectures or ship at any cost. We optimize for systems that stay maintainable, decisions we can defend years later, and codebases that improve under our hands. That's how we work now because that's what we needed from the teams we worked with before.
Moves fast because he thinks clearly. He digs into problems until they make sense, builds complete solutions, and knows when “good and solid” beats chasing perfection. Focused on getting things done properly, not just moving tickets.
Maps before building. Asks the hard questions about what’s actually broken and why, then designs a path forward that keeps quality intact while still moving fast. Brings clarity where things feel tangled.
We’ve both shipped products and owned systems. We’ve both felt the weight of decisions that echo through a codebase for years. That shared experience is where we actually work.
He moves quickly toward solutions. I dig deeper to understand the problem first. When I get lost in details, he pulls us into action. When he jumps ahead, I ground us in real needs. That back-and-forth keeps us balanced.
We don’t split work into thinking and doing. We do both, together, on everything.
If this resonates, we should talk about what you're working on
