Skip to main content
ariefrse.my
HomeSkillsProjectsAI WorkWritingContact
Resume
All writing

Note · Practice

Why I deleted my most impressive-looking case study

One unbacked claim is not one bad item in a list. It is a discount applied to the whole list.

July 6, 2026 · 3 min read

The best-looking thing on my portfolio was a Maritime API Contract Inspector. A five-stage pipeline, fully designed, polished diagrams, the works. It read beautifully.

It had never been built. Not a prototype, not a branch. Zero lines shipped.

Removed

Maritime API Contract Inspector. A polished five-stage pipeline diagram, fully designed, zero lines shipped. It could not survive one follow-up question.

So I deleted it.

The reasoning took me longer than it should have, because deleting your most impressive page feels like removing your best argument. It is the opposite. A polished presentation of something unverifiable does not add credibility, it spends it. Anyone who asks a single follow-up question finds the hole, and the moment they do, everything else on the page becomes suspect too. One unbacked claim is not one bad item in a list. It is a discount applied to the whole list.

What replaced it

Kept

A typed data file of evidence entries, each sourced from a real diff or commit message: the payroll parity bug an agent audit caught, the HTTPS downgrade root-caused on this very site, the authorization hardening pass before a release. Every entry traces to a commit someone could go and read.

Two things made that work, and neither of them was discipline.

Structure as a forcing function. The evidence lives in a typed data array, not in free-form page copy. Adding an entry means filling in fields: what happened, where is the proof. There is no slot for vibes. When the shape of the data has nowhere to put a vague claim, you stop writing vague claims. That is a better mechanism than intending to be honest.

Failures count as evidence. The entry where an agent's fix was wrong and I reverted it is more convincing than any of the successes, because it is the one that proves the review loop actually runs. Anyone can list wins. A list with no losses in it is a list nobody audited.

What I learned

A shorter list of true things beats a longer list of plausible ones. Deleting the most impressive-looking page on my portfolio made it more convincing, because every remaining claim now survives a follow-up question.

Everything traces back to something I actually shipped or actually broke. The failures earn more trust than the wins do.

portfoliocredibilityevidence

Share

XLinkedInWhatsAppThreads

Related

  • The redesign that landed on one page out of eightIf a design decision lives in more than one file, it is not a decision yet. It is a coincidence waiting to drift.
  • An HR platform where seven in ten commits came from an agentSeven in ten commits came from an agent. Zero in ten decisions about what "correct" means for the business did.

© 2026 Muhammad Arief Roseli

GitHubLinkedInSnapInvois