Learning log · Coding practice · Original notes
I wrote code, then spent years in administration. When AI arrived I picked the technical side back up. Now I work on business analysis, MBSE and knowledge engineering — and write down the process as I go.
Turning a business problem into something you can actually analyse, rather than stopping at "something feels wrong".
Carrying system design in models instead of documents, so every change to a complex system has a traceable basis.
Turning experience into something searchable, reusable and legible to machines, instead of scattered across dozens of files.
If your international website gets traffic but zero leads, the problem is rarely bad translation. Use this 5-point technical checklist before going live.
A neglected knowledge base isn't usually a software or employee attitude problem. It's often due to missing governance mechanisms: write incentives, clear ownership, and expiration cleanup. This guide offers SMB owners and IT leads a 3-step diagnostic checklist to identify core issues before investing in new tools or RAG.
Thinking about implementing an Manufacturing Execution System (MES)? Don't rush into software selection. Assess your shop floor data, hidden costs, and implementation order first.
If something here is wrong, unclear, or you would have done it differently, I would like to hear about it.