I build software around operational problems: developer workflows, industrial control, telemetry and field interfaces. My foundation is C and Java; my work connects hardware, firmware, APIs and the people using them.
Full-stack · Cybersecurity · Industrial automation · Low-code
Cambridge C2 English · Brazil / international collaboration
Enter the laboratory ↗ · LinkedIn · Contact · Skills · Evidence · Sponsors
| Project | Problem → approach | Try it |
|---|---|---|
| PatchScope | Large diffs → focused review checklists with file and line evidence. Browser, CLI and GitHub Actions. | Review a diff ↗ |
| CIFuse | Noisy CI logs → grouped failure signals, source context and investigation steps. Browser, CLI and GitHub Actions. | Inspect a log ↗ |
| DevStart Lab | Unsure where to begin → a programming roadmap, exercises and project ideas through the first pull request. | Start learning ↗ |
| RepoRelief | Scattered maintenance work → a prioritized plan for documentation gaps, broken local links and missing test-file matches. Browser and CLI. | Run an audit ↗ |
| RevScope | Too many reverse engineering tools → a searchable catalog with comparisons, official documentation and task-based workflows. | Explore tools ↗ |
PatchScope, CIFuse and RepoRelief process inputs locally with static heuristics. Their reports support review; they do not establish correctness, root cause or test coverage.
| Area | Skills |
|---|---|
| Languages | C / C17, Java, TypeScript, Python, C++, C#, Ruby, Swift, Kotlin, IEC 61131-3 Structured Text |
| Software & data | Full-stack, system design, API integration, banking APIs, databases, PostgreSQL, SQLite, security systems, cybersecurity, testing |
| Field & cloud | PLC, SCADA, HMI, signal control, Modbus, PID, Arduino, ESP32, sensor networks, IoT, telemetry, MQTT, WebSockets, AWS, Oracle Cloud IoT, Supabase |
| Product & operations | Mobile UX, Room, Android Keystore, local transactions, persistent synchronization queues, device states, field operations, Stone / Sunmi POS, QR payments, checkout, catalog, inventory, cash control, role-based operations |
| Collaboration | Project management, technical writing, documented architecture and technical decisions, Cambridge C2 English, numerical modeling (RK4) |
Inspect implementations by language
| Language / target | 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 |
From the field to the interface — architecture & working principles
Sensors and relays feed PLC / SCADA logic, cloud telemetry and operator interfaces; operator decisions feed back into the process.
Original motion study by Brunno Dev · Still diagram · Mobile still
| Focus | Work to inspect |
|---|---|
| Electrical commands & process visibility | Circuit exporter · SCADA studio |
| Connected devices & real-time feedback | C17 archive client · Telemetry evidence |
| APIs, security boundaries & data models | Balanced ledger · Inventory API · Concurrent queue |
| Touch-first field interfaces | Android console · iOS inspection store |
| Checkout & operator workflows | Stone POS evidence |
I start with the signal, then the protocol, data model, interface and person using it. Read the signal before writing code; keep operator journeys clear; validate against the real process before shipping.
Leadership: RF Offshore — industrial, offshore and field operations. RF WALLMARKET — autonomous retail, infrastructure and operational technology.
Recorded run · Execution report · Execution index · Project demonstrations
Execution records cover the listed scenarios and source commits. Screenshots below document project interfaces and bench work.
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
Reproduce the recorded execution
Run python .proof/record.py with the prerequisites in the execution index. Scenarios run repository code and check exit codes and expected output. CI publishes the execution-proof artifact with transcripts, input fingerprints and the source commit. The report identifies the tested version; the badge follows the latest workflow run.
Electrical control, embedded telemetry, mobile operations and retail systems live in the project catalog. Start with SCADA Code Studio, PID pressure control or industrial IoT event handling.
All repositories ↗ · Operations archive ↗
Support funds maintenance, reproducible examples and documentation. Thank you to the people supporting the lab.
![]() @ineedfoundmyway PART OF THE STORY Thank you for supporting the lab. |
GitHub Sponsors · Donate via Stripe · Buy Me a Coffee
Public GitHub supporters are synchronized automatically. Private sponsorships stay private.
A thought behind the work
“Archimedes will be remembered when Aeschylus is forgotten, because languages die but mathematical ideas endure.” — G. H. Hardy
Back to top · brunnodev.store · Original source and documentation: MIT. Third-party dependencies and media retain their terms.


















