Internet of Things · Field Notes
My IoT journey lives where the physical world meets software: turning signals into context, context into action, and working prototypes into dependable operational systems.
The shape of the work
The device is the visible part. The real craft is the path from a physical event to a decision someone can trust.
The journey
First edition: the story architecture is in place. Specific builds, dates, devices, and field artifacts will be added as the archive is assembled.
Observe
Every connected system starts with a useful observation: temperature, movement, position, state, usage, or change. The first shift is learning to see those signals as material for software.
A signal only matters when it is attached to a real question.
Connect
The interesting work begins between the device and the screen: connectivity, protocols, power, identity, ingestion, and all the unreliable edges that a tidy architecture diagram leaves out.
Connectivity is a product behaviour, not an infrastructure footnote.
Operate
Collecting telemetry is not the finish line. The value appears when a signal changes an operational decision, triggers useful automation, or makes a hidden condition visible to the people doing the work.
The best dashboard is often the one that helps someone act sooner.
Interpret
IoT turns the physical world into a stream of context. AI can make that context easier to interpret, but only when the underlying signals are dependable, explainable, and grounded in the operation they represent.
Intelligence is only as trustworthy as the system underneath it.
What the field teaches
A clever prototype earns attention. A device that reconnects, recovers, and explains its state earns trust.
More telemetry does not automatically create more insight. The useful signal is the one tied to a decision.
Power, placement, interference, maintenance, and human behaviour reshape every clean technical plan.
From connected to intelligent
The through-line into Wrightforge’s current work is simple: reliable inputs, operational context, useful interfaces, and an honest understanding of what automation can—and cannot—do.
See what that becameContact
I’m always up for talking shop — AI, contact centres, or whatever you’re building.