Why this portfolio is a public engineering notebook

I wanted this site to be more useful than a polished landing page. A portfolio can show finished work, but it often hides the decisions that actually matter: what tradeoffs were made, what failed, what changed after the first version, and what I would do differently next time.

That is why I am treating hamza.my.id as a public notebook. The goal is simple: keep project notes, technical writing, and retrospectives in one place, with enough structure that someone can understand the work without needing a long explanation from me.

The failure mode I am avoiding

The common developer portfolio failure is over-polish without evidence:

hero slogan
technology logos
generic project cards
contact button

That can look clean, but it does not answer the useful questions. What problem did the project solve? What failed? Which tradeoff did the engineer choose? What would they do differently next time?

What I want the site to prove

I want the site to show that I build, write, and think clearly about engineering decisions. That means fewer impressive-looking sections and more useful pages: writing, projects, resume, now, and lab.

The site should make it easy to answer practical questions:

• What kind of applications do I build?
• How do I think through technical decisions?
• What am I strengthening right now?
• Which projects show useful proof of work?

Why writing matters

Writing is a forcing function. If I cannot explain why a project is structured a certain way, the design probably needs more thought. If I cannot describe what I learned from a build, I may not have extracted the lesson clearly enough.

The writing section is where I want to document backend notes, frontend architecture decisions, automation work, AI API experiments, Web3 interfaces, and project retrospectives.

The tradeoff

A notebook-style site is slower to build than a one-page portfolio. It needs real project context, stronger editing, and enough restraint to avoid becoming a pile of unfinished notes.

The benefit is credibility. A reader can inspect the thinking behind the work, not just the final label.

What I am avoiding

I am intentionally avoiding a flashy developer portfolio style. No fake terminal hero, no skill bars, no oversized animations, and no generic sections that only exist because other portfolios have them.

The site should feel fast, calm, and readable. Good engineering taste should show through the structure and clarity, not through decoration.