Back to Today I Write
Opinion·3 min read

Why I'm Starting 'Today I Write': Thinking in Public Beyond Tutorials

A personal manifesto for this writing space — why I want a home for half-formed lessons, honest engineering opinions, and quiet observations.

#Writing#Opinion#Personal#Reflection

Most developer blogs only publish polished, 3,000-word tutorials after everything has already worked out. While tutorials are useful, they hide the most interesting part of building software: how your mind actually changes along the way.

That is why I rebuilt this site around a simple ritual I call Today I Write.

Two Streams, One Habit

I wanted one clean, monochrome corner of the internet where two different kinds of writing can live side by side:

  1. Today I Learned (TIL): Concrete technical discoveries — a subtle query behavior, a clean architectural pattern, an Android layout trick, or an ML evaluation pitfall worth remembering.
  2. Opinions & Field Notes: Unfiltered perspectives on engineering craft, enterprise systems, books I'm reading, and the small lessons that don't fit inside a documentation page.

Writing as Compression

Writing forces vague intuition to survive contact with plain language. If I cannot explain why a design choice works in four clean paragraphs, I probably don't understand it as well as I thought.

Clear writing is not the decoration on top of clear thinking — it is the tool that produces it.

So whether an entry here is a two-minute technical note or a strong opinion I might revise a year from now, it belongs here. Welcome to the notebook.

Wildan Fatahillah Akbar

Written by Wildan Fatahillah Akbar

ODP IT at Bank Negara Indonesia (BNI) sharing notes on banking tech, Android, ML, and ideas. Want to continue the conversation? Say hi on LinkedIn or via email.