izhan
Let's Talk

I build software, and the systems around it.

Who I am

I'm Muhammad Izhan, a software engineer and CTO. I design, build and run web products — and lead the people who build them with me.

Most of my work sits where engineering decisions meet business ones: what to build, how to build it so it lasts, and how to ship it without burning the budget. I like solving complicated problems by breaking them into simple systems — small parts with clear jobs, wired together on purpose.

How I work.

  1. 01

    Business first

    Code is the last step. I start with who uses it, what it earns or saves, and what failure costs.

  2. 02

    Simple systems

    Complicated problems get broken into small parts with clear jobs, wired together on purpose.

  3. 03

    Small, real increments

    Working software every week beats a perfect plan every quarter.

  4. 04

    Leave it documented

    Every system I hand over can be understood by the next engineer without me in the room.

Engineering philosophy

  • Boring technology, used well, beats clever technology used badly.
  • Architecture is the set of decisions that are expensive to change — make fewer of them, and make them deliberately.
  • Performance is a feature users notice before anything else.
  • If it isn't monitored, it isn't in production.

Leadership

Good teams don't need more instructions. They need clear priorities, honest feedback and someone who clears blockers. As a technical lead my job is to make decisions early, explain them, and stay close enough to the code to know when they're wrong.

Working with clients

  1. 01Conversation — what you need, and whether I am the right person for it.
  2. 02Plan — scope, architecture, milestones and an honest estimate.
  3. 03Build — weekly working releases you can click through.
  4. 04Launch — deployment, monitoring and handover.
  5. 05Improve — iterate on what real users actually do.