I build open-source Rust systems at the intersection of amateur radio, computational electromagnetics, and practical HF data communication. Across Rusty Wire, fnec-rust, and OpenPulseHF, my work focuses on turning real engineering requirements into reliable tools: from antenna-length planning and NEC-compatible modeling workflows to plugin-based digital modem architecture.

My approach is strongly rooted in requirements engineering. I aim to define clear problem boundaries, keep interfaces explicit, validate assumptions with testable designs, and evolve systems in modular steps that remain maintainable over time. The goal is not only to make things work, but to make them understandable, verifiable, and reusable by others.

I am deeply dedicated to Free and Open Source Software (FOSS): building in public, choosing copyleft licenses for shared progress, and contributing software that helps the radio and engineering communities learn, experiment, and collaborate.

The strongest impression from these projects is disciplined technical intent. You are not just shipping code; you are building a coherent engineering stack with clear traceability from requirements to implementation. There is a consistent preference for modular architecture, transparent documentation, and community-first licensing that reflects long-term commitment rather than short-term experimentation.

I like to work from requirements to reproducible results.

Short examples:

• Engineering execution: In Rusty Wire, practical antenna calculations are implemented as clear models with documented assumptions, so users can verify why a result was produced.
• Challenging existing solutions: In fnec-rust, I am not only reusing classic NEC ideas, but rethinking solver structure and modularity to improve portability, maintainability, and long-term evolution.
• Testing approach: I use layered validation, from parser/model consistency checks to numerical sanity checks and benchmark comparisons, so changes are measurable and regressions are visible early.

Your sponsorship helps me dedicate sustained time to high-value FOSS engineering for radio and computational electromagnetics.

With sponsorship, I can:

• deliver better documented releases and onboarding material,
• expand automated testing and reproducibility infrastructure,
• prioritize community issues and requested features,
• keep core tooling open, modular, and accessible.

I am applying the same standards to project stewardship as to code quality: clear scope, transparent progress, and practical outcomes that the community can directly use.

If you value rigorous requirements engineering, open collaboration, and durable technical work, sponsoring is the most direct way to help this ecosystem grow.

What sponsors can expect from me:

• regular public progress updates,
• transparent priorities and scope decisions,
• responsible maintenance of released code,
• respectful and constructive community collaboration.

My objective is simple: convert sponsor support into reliable, open infrastructure and practical tools the community can trust.