The operating problem
Field equipment does not behave like a static spreadsheet. Serialized assets are assigned into kits, used on different jobs, returned with exceptions, repaired, replaced, and replenished. Effective tracking needs to model those transitions rather than only tallying item counts.
RoadBoxOS: independent application work
Beginning in 2025, before the current workplace role, I developed inventory workflows around families, serialized children, kits, road boxes, show deployments, reconciliation, resupply, scan-to-kit, and PDF reporting. Iterative versions improved data entry, handling of provisional records, and scan-based workflows.
AtomicOS: a connected Linux appliance
In the operational environment, I configured a Raspberry Pi-hosted FastAPI/Uvicorn service with a SQLite/SQLAlchemy data layer, authentication roles, event/activity records, barcode inputs, a dedicated wireless access point, local DHCP, and systemd startup.
Testing and engineering judgment
The important lesson was to validate what real users needed to do with the tool: scan, find, assign, reconcile, and understand exceptions. Field trials surfaced usability changes. Designing the database, configuring the network, and testing physical scanners each required different modes of troubleshooting.
What I would improve next
Restore-tested backups, more rigorous concurrent-user testing, audit and permission reviews, label-printing integration, and a clearer API contract for other business systems.