Blog
Writing on software, systems, and the craft of building.
What a 1920s Loom Taught Us About Software
The five whys, gemba, and kaizen did not start in software. They began with Sakichi Toyoda and a loom that stopped itself: the lineage behind how we build.
AYA · Jun 2026
The Craft Mindset: What Kaizen Actually Means for Software Teams
Kaizen is not a pep talk but a method: eliminate waste, prevent errors at the source, and raise quality permanently. How it maps to software engineering.
AYA · Apr 2026
Taming Complex Behaviour with Explicit State Machines
Ad-hoc booleans are the quiet debt that breaks production at the worst moment. Why modelling states and transitions explicitly eliminates whole classes of bugs.
AYA · Mar 2026
When the Desktop Still Wins
A practical look at why certain software problems belong on the desktop, and what it takes to build desktop applications that are fast, secure, and dependable.
AYA · Feb 2026
Mobile Products That Earn Their Place on the Home Screen
Native versus cross-platform, performance budgets, offline data, release pipelines: the engineering that decides whether a mobile app is kept or deleted.
AYA · Feb 2026
Rust for Software That Has to Be Right
Why Rust is a serious engineering choice when reliability, performance, and long-term maintainability are non-negotiable. Examined from both sides of the table.
AYA · Jan 2026