About
About
Engineering notes from writing code, building products, and debugging real problems.
This is where I keep my engineering notes.
I do not want it to read like a tutorial site, and I do not try to turn every post into a polished “best practice”. Most posts start from something real: a Flutter screen behaving incorrectly, an iOS or Android packaging issue, a deployment detail, or a project structure that I later decided to rethink.
If I leave these things only in memory, they quickly turn into “I think I fixed something like this before”. Writing them down keeps the context, the judgment, and the final fix close enough for the next time.
What I Write Here
Most notes are related to the work I usually do:
- Flutter, iOS, and Android issues
- project structure, architecture boundaries, and engineering tradeoffs
- build, release, deployment, scripts, and toolchains
- things I am learning and trying to explain in my own words
Not every post needs to be long. Some are just a command, a config option, or a debugging conclusion. Others keep more of the story: the background, the dead ends, and the reason a particular solution was chosen.
What I Care About
I try to avoid sentences that sound correct but are hard to use.
For debugging notes, I want to preserve:
- what I saw
- the environment and constraints
- what I tried, and why it did not work
- how it was solved, and what judgment is reusable
For learning notes, I try to write my own understanding instead of copying documentation. Documentation can always be looked up again. The reasoning at the time is usually the more useful part to keep.