Curiosity-driven engineering. Building resilient systems from the metal up.

I've never been a fan of staying in a single lane. To me, engineering is about following curiosity wherever it leads—whether that means tearing down a Linux kernel setup to see how it ticks, writing PySpark pipelines that make messy data behave, or deploying lightweight edge systems that just work when network connections drop.

I love working as a forward-deployed builder because it forces you to look past abstract diagrams and care about the actual human on the other end of the screen. If software doesn't make someone's life easier or solve a real pain point, what's the point?

• Obsessed with the Real World: Code looks great in a local container, but reality is messy. I build with failure modes, intermittent networks, and tight hardware constraints (<4GB RAM) in mind from day one.
• Driven by Curiosity: I didn't learn this stuff by checking boxes; I learned it by breaking things, reading raw documentation, and tinkering until I understood the underlying mechanics.
• The Intersection of Code & Economics: Because of my background bridging technical design with economic structures, I can't look at infrastructure without wondering: Is this cost-effective? Will this scale sustainably? What's the long-term TCO?
• Pragmatic Tooling: No unnecessary bloat. Just asynchronous event loops (EventBridge, Lambda, DynamoDB), clean Linux terminals (Zsh, tmux, Vim), and automation that gets out of the way.

• The Environment: Fedora Linux, Zsh, tmux, Vim, SSH
• The Cloud & Backends: AWS Serverless, IAM/VPC hardening, event-driven architectures
• The Data & AI Layer: Python, PySpark, Advanced SQL, Amazon Bedrock, local model workflows
• The Workflow: Terminal-first tooling, Docker, Git, local-first iteration

• Offline-First Assistive Tooling: Building lightweight terminal utilities and local model workflows to keep my dev loop fast and completely self-contained.
• Self-Healing Daemons: Tinkering with background scripts that watch cloud logs, catch anomalies, and trigger safe automated fallbacks before things cascade.
• Streamlining Data Flow: Wrangling messy data streams into clean, well-partitioned analytical layouts that don't hemorrhage money on storage.

guest@lundi-terminal ~ % ./vibe-check.sh

[████████████████████] 100% | System Status: Fully operational
⚡ Fuel Source : Strong coffee, terminal commands, & late-night curiosity
🧠 Mindset   : Forward-deployed, customer-obsessed, & allergic to bloat

guest@lundi-terminal ~ % cat ./invitation.txt

"Working on something interesting? Drop me a line. Whether it's 
distributed systems, edge Linux, messy data, or just building weird 
things with code—let's build something great together."