(03) — Environment
CJNET
Our family printing and computer-services shop—and the environment where I find, test and break the workflows my software has to survive.
CJNET — project cover
(02) — What this is
Not a job title. A counter, a printer, a queue of people and a shop network I am responsible for keeping alive.
Technical support, network and equipment configuration, print workflow changes and internal tools.
Every assumption gets tested by someone impatient, on a bad connection, with a file that will not open.
(03) — What I have built and tried here
The upload-and-print path—the one system that graduated into daily use.
Router, hotspot and local-network configuration.
Small process fixes that never became software because they did not need to.
Interfaces staff bypassed and flows customers ignored in favour of Messenger.
(04) — What it taught me
Software has to work for busy staff, impatient customers, unreliable connectivity, physical equipment and habits that already exist.
Shipping the feature was the easy half. Changing the task was the real work.
Every path needs the old way still available.
The requirements I trust came from standing at the counter.