What I am learning, and why I write it down

What this site is

My public notebook. Written first for myself three months from now, by which point I will have forgotten most of what I worked out today.

And written for anyone chasing the same questions: if one note here saves you an afternoon, it has paid for itself.

Background

I wrote code, then moved into administration. For a long stretch after that, the technical thread was simply cut.

When AI arrived I picked it back up — and it felt different this time. The cost of writing code had dropped; what remained hard was working out which problem is worth solving. The administrative years turned out to be an unexpected asset, because I had watched a lot of processes go sideways inside real organisations.

What I work on now

• Business analysis　Turning a business problem into something you can actually analyse, rather than stopping at “something feels wrong”.
• MBSE　Carrying system design in models instead of documents, so changes to a complex system have a traceable basis.
• Knowledge engineering　Turning experience into something searchable, reusable, and legible to machines.

For me these are one line, not three: state the problem clearly, build the structure, then make the knowledge callable again and again.

How I write

Only about things I have actually built or tested. When I get something wrong I come back and fix it, and the change shows up in the updated date. Where AI helped with drafting, the opinions and conclusions are still mine.

Languages

Native Chinese, working English, Italian in progress. The three versions are not translations of each other — the same topic pulls my attention in different directions in each language.