sealWithIt

I can similarly output 2-3x more code but everything stalls down to me having to review and integrate in a meaningful way the moment I am the one that has to maintain that code.

It's eerie to observe collaborators output code they don't understand, spend days chatting with Claude instead of reading (like really reading) compiler's output or 3 pages of manual, and how lost and oblivious they look when the AI fixates on solving a different problem than the one they have been tasked.

Location: Pensacola, FL

Remote: Yes

Relocation: Yes (US)

Technologies: C++, Python, Java, Distributed Systems, Networking, Embedded, Full-stack

Resume: https://drive.google.com/file/d/1Zqk69PPyvQaxbKHXvSsydGSM-Xs...

Email: -> https://www.linkedin.com/in/rfronteddu/

---

Research Software Engineer with 10+ years of experience building distributed and real-time systems in unreliable and constrained environments.

Background in networking, including custom transport protocols, network monitoring, and adaptive systems. Recent work includes AI-assisted software engineering and intelligent systems.

Experience designing and building systems that need to remain reliable under failure, including tactical and edge environments.

Interested in backend, infrastructure, distributed systems, or AI-driven systems roles where I can build and improve core technology.

I think it was a good decision. I just spent a couple weeks doing experiments with meshcore/meshtastic/reticulum/... comparing them to our stealth solution and I experienced a functional core in meshcore surrounded by a lot of vibe coded slop.

In particular I did not like the shoddy documentation of the various vibe coded interfaces and how brittle the integration experience felt because of them.

Looks like exactly what I was looking for :p