> ROLE: SYSTEMS ENGINEER · RUST
Systems Engineer.
High-performance systems engineering. Rust at the core. Building reliable, fast software for demanding domains where every cycle counts.
> READ MOREAbout me
> UNIT: MAURICIO KLAINBARD · STATUS: ACTIVE
I design high-performance architectures and critical systems centered on Rust. My approach prioritizes memory safety and predictability in demanding environments where every processing cycle counts.
Deep technical rigor turns complex problems into logical, deterministic solutions that maximize hardware utilization. My priority is building solid, scalable infrastructure that eliminates technical debt at its source, ensuring long-term stability and agility.
Projects
> REGISTERED PROJECTS · DATA INSTRUMENTS
Euclidean geometry library in Rust: vectors, points, bodies, figures, intersections, collisions. Generic over N dimensions. Transformation matrices and affine transforms (matrix + translation) for most types in the crate.
Apollonius is a computation layer only. It does not ship simulations; it provides the primitives to build them. Separate binary crates use it for the math and pipe results into Macroquad for rendering. Example applications: black hole (Schwarzschild) and N-body orbit simulations, but the same tools extend to buoyancy, fluids, raytracing, and other domains that need geometric and kinematic calculations.
My first workflow system. Topological sort via Kahn's algorithm. Data structures for O(1) access to any node; dynamic update as the flow runs. Socket connections for real-time feedback. Custom forms, scheduled tasks. Real-time execution driven by a single request and the workflow map.
Evolution of the first workflow system. Same idea—connect steps, run them in order—but here AI figures out the connections. You describe what you want in plain language and the system suggests how to chain the steps and how to fit each step's output into the next one's input. No manual wiring.
Stack: Rust, Proto, CEL (formatting at runtime). Proto is the bridge between nodes written in different languages—so the project can stay open source: anyone can add nodes in their language of choice and they all talk to each other through the same protocol. Goal: a visual interface where you type what you need and the workflow builds itself.
System Operational Protocol
> SKILLS · WORK STYLE · PROFILE
Stack: Rust (primary), systems and high-performance tooling. Solid background in math and physics; comfortable with algorithms (e.g. topological sort, O(1) structures), real-time flows, and simulation pipelines. Experience from web and workflow engines to geometric libraries and numerical integration.
Work style: Calm and proactive. I focus on clarity, readable code, and teams that move in the same direction. I prefer to identify and use each person's strengths and to keep the environment constructive.
Under pressure: I perform well and tend to defuse tension for others, look for resolution paths, and encourage persistence. I aim to deliver reliable results and to support the team until the goal is reached.
Contact
> LINKS · EXTERNAL HANDLES
Open to collaboration, consulting, and roles in systems engineering, simulation, or high-performance software.
GitHub for code and projects · LinkedIn for profile and experience · YouTube for simulation demos.