Field notes
Ideas tested
in the work.
Short observations about building data tools, reliable automation, and decision workflows. Written in English and Thai.
A green status is not an end-to-end test
Why a healthy deployment view can coexist with a broken user request path—and how to inspect the difference safely.
Revit, AI, and the approval boundary
A practical way to start using AI with construction information without confusing exported data, documented integrations, and authorized model changes.
The evidence ladder: source, runtime, and acceptance
A vocabulary for describing what a technical investigation actually proves—and what it does not.
SDLC in plain language: from a requirement to software a team can maintain
A practical English adaptation of a Thai learning guide to the seven stages of software development, with examples and prompts for using AI in each stage.
Auditing a legacy network platform without touching production
A read-only method for mapping authentication, accounting, policy, and maintenance paths before proposing change.
A dashboard is only as useful as its source trail
Why freshness, provenance, and failure states belong in the interface—not only in the pipeline logs.
Automation should admit what it does not know
A short design principle for research workflows that operate with incomplete or stale evidence.
From notes to working systems
A way to turn scattered knowledge into steps that can be checked, used, and improved over time.