ONLINE
UNCLASSIFIED REV. 2024.12

DOCUMENT: Engineering Manifest

Why I build what I build. A declaration of principles for distributed systems engineering.

01

The Problem With Modern Infrastructure

The distributed systems ecosystem is broken. We've normalized 300,000-line codebases for what should be simple middleware. We've accepted 50+ dependencies as "normal." We've built debugging tools that require PhDs to operate.

This isn't engineering. This is collective Stockholm syndrome.

" Complexity is not a badge of honor. It's a sign of failure. "

When a robot's middleware has more lines of code than the robot's mission logic, something has gone terribly wrong. When debugging a satellite's communication layer requires a team of 10, we've failed at our jobs.

02

What I Believe

Zero Dependencies, Zero Excuses

Every dependency is a liability. Every external library is a potential security hole, a maintenance burden, a point of failure. The best dependency is the one you don't have.

Performance Is Non-Negotiable

In real-time systems, microseconds matter. A robot arm can't wait 10ms for a message. A satellite can't afford jitter. Performance isn't optimization—it's correctness.

Debuggability Over Cleverness

Clever code is code you'll hate at 3 AM. I write code that future-me can understand, that a junior dev can trace, that prints meaningful errors. Boring is beautiful.

Ship or Die

Theory without practice is philosophy. Code that doesn't run in production isn't engineering. I build things that work, not things that look good in papers.

03

Why Rust

I didn't choose Rust because it's trendy. I chose it because I was tired of debugging segfaults at 2 AM. Because I was tired of memory leaks that only showed up in production. Because I was tired of data races that corrupted satellite telemetry.

Before Segmentation fault (core dumped)
After error[E0382]: use of moved value: `data`

Rust moves entire classes of bugs from runtime to compile time. In mission-critical systems, this isn't a nice-to-have. It's the difference between success and disaster.

04

The Mission

Build infrastructure that enables the next generation of autonomous systems. Robots that work. Satellites that don't crash. Industrial systems that operators can actually understand.

600K+ lines of Rust, written with purpose
257 ns message latency, because milliseconds are too slow
0 dependencies in core, because less is more

This isn't about building another DDS implementation. It's about proving that infrastructure can be simple, fast, and correct—all at once.

05

Join the Mission

If you're building robots, satellites, or anything that needs to work reliably, I want to hear from you. If you're tired of the status quo, let's talk.

// NASKEL Distributed Systems Engineer Somewhere in France