choose your scene
EXT. AN OPEN FIELD — DUSK
A beast with horns and a figure in white dance on the horizon.
Neither leads. Neither falls.
NARRATOR (V.O.)
Every system is that dance. On one side, the beast:
voltage, noise, relays, legacy protocols, hardware
that does not forgive. On the other, the grace: an
operator's thumb on a screen, a checkout that closes,
a dashboard that tells the truth at 3 a.m.
CUT TO:
I build the choreography between the two.
My starting point is programming logic in C and Java. I work outward from there: the protocol, the data model, the interface, then the person who has to use it. I choose a language for the job and leave the reasoning alongside the implementation.
Architecture, journeys and technical decisions focused on operational results. SCADA, PLC, IoT, automation and signal reading for real processes. I connect engineering thinking, digital product and operational context to turn messy requirements into usable systems.
A working laboratory by Brunno Dev. Follow a signal, inspect the source, and open the evidence behind it.
Director's notes (open)
| # | Rule on set |
|---|---|
| 01 | Read the signal before writing the code. |
| 02 | If the operator needs a manual, the interface failed. |
| 03 | Nothing ships until it has run against the real process. |
From a wire in the field to a decision on a screen. Every reel below is one stretch of this path.
Original motion study by Brunno Dev · conceptual flow · Still diagram · Mobile still
| Start with | Follow the scene | Inspect the work |
|---|---|---|
| A relay, a sensor, a process | 01 / Industrial logic | SCADA Code Studio |
| A device sending readings | 02 / Telemetry | Bench-to-dashboard evidence |
| A request crossing a boundary | 03 / Architecture | Balanced ledger |
| An operator in the field | 04 / Mobile interfaces | Android field console |
| A checkout under pressure | 05 / POS systems | Stone POS evidence |
Open each reel below for context, technologies and source code.
REEL 01 — Automation & industrial logic · the beast wakes up
INT. CONTROL ROOM — NIGHT
A relay clicks. A PLC answers. The process becomes visible.
Electrical commands, PLC/SCADA thinking and process visibility.
PLC / SCADA / SIGNAL CONTROL / MODBUS / PID
▸ On screen: Circuit exporter · SCADA control studio
REEL 02 — IoT & telemetry · the field starts talking
EXT. ANYWHERE — CONTINUOUS
A sensor whispers. The cloud listens. A chart moves in real time.
Sensors, connected devices, cloud signals and real-time product feedback.
ARDUINO / CLOUD IoT / TELEMETRY / WEBSOCKETS / SENSOR NETWORKS
▸ On screen: Durable archive client (C17) · Arduino telemetry evidence
REEL 03 — System architecture · the rules of the house
INT. THE VAULT — DAY
Every request has a door. Every door has a lock.
APIs, integrations, security boundaries and sustainable technical decisions.
BANK APIs / SECURITY SYSTEMS / DATABASES / AWS / SYSTEM DESIGN
▸ On screen: Balanced ledger · Supabase inventory API · Concurrent task queue
REEL 04 — Android field interfaces · gloves on, screen on
EXT. OFFSHORE DECK — WIND
An operator taps once. The inspection is saved. No one waits.
Touch-first surfaces for mobile operators and hardware-aware workflows.
KOTLIN / MOBILE UX / DEVICE STATES / FIELD OPERATIONS
▸ On screen: Android offshore field console · Native iOS inspection store
REEL 05 — POS & payment systems · the money scene
INT. STORE COUNTER — RUSH HOUR
Card in. QR on screen. Stock updated. Cash drawer reconciled.
Checkout, catalog, inventory, cash control and role-based operations.
STONE / SUNMI / POS / QR / OPERATOR UX
▸ On screen: RF Solutions × Stone POS evidence
LANGUAGES I SPEAK TO MACHINES
THE CRAFT
THE BEAST — FIELD & CLOUD
THE GRACE — BEYOND CODE
| Company | Role | Operating focus |
|---|---|---|
| RF Offshore | CEO | Industrial, offshore and field operations |
| RF WALLMARKET | CEO | Autonomous retail, infrastructure and operational technology |
Project screenshots and bench photos. Open a case to view the original images.
CASE #01 — RF Solutions × Stone — POS System
CASE #02 — OFS — Offshore Fleet POB Platform
CASE #03 — Arduino / ESP32 Telemetry
Device output — ESP32 serial monitor
Python bridge — MQTT messages received
Database — persisted sensor readings
Dashboard — temperature, humidity and inventory
Activity log — inventory movements and recent readings
CASE #04 — Just for Fun · off the record
Cast sheet — native implementations (click a role to watch the scene)
| Actor · language / target | Role · working source |
|---|---|
| C17 | Durable archive client |
| C++ | Concurrent task queue |
| C# | Supabase inventory API |
| Java | Balanced ledger |
| Kotlin | Android inspections |
| Swift | Native inspection store |
| Ruby | Git collaboration auditor |
| IEC 61131-3 Structured Text / PLC | Circuit exporter |
| SCADA | Control studio |
Recorded execution evidence for the scenarios listed in the index. Check the source commit and prerequisites before reproducing a run.
Verified run · Execution report · Verified execution index
How to reproduce the take
Run python .proof/record.py with the prerequisites listed in the execution index. The scenarios execute repository code and verify exit codes and expected output. CI publishes execution-proof with the transcript, input fingerprints and source commit. The downloadable report identifies the exact tested version; the workflow badge tracks the latest run.
I build around a simple loop: investigate a real problem, make the implementation inspectable, and document what it takes to run it. Sponsorship helps me keep that work moving.
 @ineedfoundmyway PART OF THE STORY Thank you for supporting the lab. |
| In the lab | For the people using it |
|---|---|
| Maintenance and troubleshooting | Projects that remain useful beyond the first release |
| Reproducible examples and documentation | A clearer path from reading the source to running it |
| New tools and technical experiments | More decisions, tradeoffs and results shared in the open |
Sponsor access / support and collaboration
Verified sponsors can discuss code reviews, troubleshooting, project guidance and collaboration ideas. Access instructions are provided privately in the GitHub Sponsors welcome message; refer to the selected tier for its terms.
Buy Me a Coffee contributions use separate verification. Please do not post payment details or private project information in public issues.
Public GitHub supporters are synchronized by the scheduled workflow. Private sponsorships are not displayed. Sponsor options · Explore the work first
BUILD SYSTEMS. READ SIGNALS. SHIP OPERATIONS.
Back to the opening · Follow a signal · Support the next frame
Original source and documentation are MIT licensed; see LICENSE. Third-party dependencies and media retain their respective terms. Maintained by Brunno Dev.