Systems Architect • Researcher • Lifelong Learner

I study what keeps systems stable under pressure and what causes them to fail — from neurons and software to power grids and networks. With a QA and engineering background, I look for edge cases, limits, and failure modes.

My Approach

I focus on how energy and information move through systems — where they bottleneck, distort, or fail. I study natural systems under stress and apply those lessons to engineered ones.

What I Do

I'm a Graduate student studying Biology and AI/Computer Science while building and maintaining real software systems.

My QA background means I:

• Test assumptions
• Look for failure paths
• Prioritize reproducibility and documentation

My faith keeps me grounded. Technology has consequences, and I try to stay aware of that.

What I build is:

• Open — MIT-licensed
• Transparent — clear intent, inspectable
• Conservative — safety before ambition
• Useful — practical over novel

Why Support Matters

Support funds time, continuity, and maintenance — not hype.

It helps me:

• Keep projects alive
• Balance education with research
• Maintain open tools
• Do unglamorous but necessary work

I focus on safety layers, governance systems, infrastructure, and efficiency — work that rarely trends but keeps systems from failing when it matters.

My Focus

I think in patterns, not disciplines. Feedback loops, delays, noise, collapse, recovery — they appear everywhere. I document mistakes and share lessons learned.

If you care about systems that fail safely, technology that respects limits, and open work built to last — that's what I'm doing.

Good systems are shared systems.

Thanks for reading. Support through code, feedback, or conversation keeps this work steady and open.

Still learning. Still building.

"Wait for the Lord; be strong, and let your heart take courage; wait for the Lord." — Psalm 27:14

— Don