Daniel Netto
Software engineer working close to systems, storage and machines
Over the last years I have been building software that keeps useful work local: desktop runtimes, encrypted storage, offline-first workflows, signed updates, industrial tools and hardware projects where failure is visible in the real world.
I am interested in the line where software stops being a screen and starts becoming infrastructure: the part that decides how data is stored, how work continues without a network, how a machine receives instructions, how a user recovers from an interrupted write, and how an application evolves without turning every business rule into framework glue.
The strongest examples are recent:
AppCore Runtime
A modular Rust runtime for local-first applications: manifests, lifecycle, commands, queries, storage contracts, security, sync, peer RPC, supervision, observability and signed updates.
Primland Devis Traiteur
A Tauri desktop application for real catering quotation work: NAS storage, encrypted DNTJ files, local locks, offline numbering, PDF generation and release channels.
What the work says
Local-first before cloud-first
A business workstation should not become useless because a network share is slow, a connection drops, or an update endpoint is unavailable. AppCore and Traiteur both treat local continuity as an architecture constraint, not a feature toggle.
Infrastructure belongs behind a contract
AppCore's 1.0 contract asks an application for three artifacts: an application manifest, a deployment manifest and business code implementing the public application facade. The runtime owns the rest.
Small tools are still design exercises
A VS Code header extension, a terminal color table or an LED scanner are smaller than a runtime, but they show the same instinct: reduce repeated friction, make behavior explicit and leave a reusable artifact behind.
A career arc, not a stack
My path starts with Bash scripts and Minecraft servers, moves through CNC programming and factory constraints, then into C/C++ at École 42, embedded and hardware projects, and more recently Rust runtimes and desktop systems for industrial work.
That path matters. CNC teaches that code can waste material. 3D printers teach that calibration is part of the system. C teaches what abstractions cost. Rust offers a way to keep low-level control while making more failures impossible by construction.
Start with Engineering if you want the operating principles. Start with AppCore Runtime if you want the most complete architecture story. Start with Hardware if you want to see why my software work keeps returning to physical constraints.
2026 © Daniel Netto. Todos os direitos reservados.