System Architect • Researcher • Learner

I work across thermodynamics, neuroscience, cryptography, and systems design, trying to understand how energy and information move through both living systems and technical infrastructure.

I'm interested in what keeps systems stable under pressure — neurons, power grids, robots, networks — and what causes them to fail. I'm still learning, but I'm learning in public.

Guiding Principle

Energy is the real currency.

In biology, computation, and infrastructure, everything eventually comes down to flow, constraints, and efficiency.

I spend a lot of time studying how nature solves these problems, and then trying to translate those patterns into systems that are more resilient and more honest about their limits. Sometimes I get it right. Sometimes I learn what not to do next time.

How I Work

⚙️ Care • Discipline • Follow-through

I'm a Harvard Biology + AI student working across multiple domains simultaneously. I balance education, research, and building production systems that people actually use.

Faith matters to me. It reminds me that building things isn't about ego — it's about stewardship and service. Technology carries consequences, and I try not to forget that. I don't always get it right, but I try to stay accountable.

What I build is meant to be:

• 🔓 Open — MIT-licensed, no paywalls
• 🌍 Transparent — clear intent, auditable behavior
• 💫 Principled — guided by ethics and restraint
• 🤲 For others — usefulness over recognition

I don't chase novelty. I try to maintain what I start, even when it's hard.

Why Support Matters

Support doesn't fund hype.

It buys time and continuity.

It helps me:

• keep projects maintained instead of abandoned
• continue my education and research
• build tools that stay open and usable
• dedicate more time to the work that matters

Most of what I work on sits in unglamorous places:

• safety layers
• infrastructure
• trust and verification
• energy efficiency

That work takes patience more than publicity. And I'm still figuring a lot of it out.

The Mission

I don't really think in terms of disciplines.

I think in terms of patterns.

The same ideas show up everywhere: feedback, delay, noise, failure, recovery. Each project teaches me something that carries into the next. I make mistakes, but I try to learn from them and document what I find so others don't have to repeat them.

I'm not here to compete or posture. I'm here to solve problems carefully, share what works, and be honest about what doesn't.

If you care about:

• systems that fail safely
• technology that respects constraints
• open work that anyone can inspect
• building things that last

then you're already aligned with what I'm doing.

I'm grateful for collaborators like Marcel Krüger and tools like AI that help me build faster and learn better. I couldn't do this work alone, and I don't pretend to.

Good systems are shared systems.

Thanks for taking the time to read.
Any support — code, feedback, or otherwise — helps keep this work steady and open.

I'm still learning, still building, and still grateful for the chance to do it.

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

— Don