For over two decades, my focus was centered on large-scale leadership, operational strategy, and mission-critical decision-making. That background ingrained a permanent habit: I look at everything through the lens of systems, feedback loops, and downstream effects.
Today, that same mindset fuels my obsession with modern technology and hands-on creation. When I'm not architecting enterprise cloud workflows or running a segmented home lab stack, you'll find me on the pitch coaching youth soccer, dialing in mechanics on the fairway, or dissecting complex automation pipelines.
I don't come from a cookie-cutter computer science track (hence the handle @NoProfessional582). I build because I am relentlessly curious about how pieces connect, where friction hides, and how thoughtful tooling can give people their time and autonomy back.
Most modern software demands a recurring subscription, an active account, and custody of your sensitive data just to organize a simple workflow. I prefer software that respects your sovereignty: fast, local-first tools that run directly on your own hardware, solve immediate problems, and get out of your way.
01 // CORE PILLAR
Data Sovereignty First
Your notes, applications, files, and personal data belong entirely to you, not an external third-party cloud. Privacy shouldn't be an opt-in luxury; it should be the baseline architecture.
02 // CORE PILLAR
Frictionless Deployment
Good software shouldn't require a 30-step configuration guide. Whether it launches via a clean container run, a single-command startup script (run.bat / npm start), or a standalone binary, getting up and running should be dead simple.
03 // CORE PILLAR
Built for Ground-Level Utility
I don't build software to showcase unnecessary abstractions. Every interface, script, and application is born from real operational friction, designed to eliminate redundant clicks, remove cognitive clutter, and run reliably day in, day out.
Minisforum N5 NAS
Dedicated production server hosting self-managed Docker stacks, local databases, and internal services across segmented Zero-Trust VLANs, currently being rebuilt on a pure Debian base.
HP Omen 16 + MX-Linux VM
All active development runs inside a Debian-based MX-Linux virtual machine on my primary HP Omen 16 gaming laptop, sharing a common Debian foundation and Docker service layout with production while keeping desktop dev tooling, experiments, and AI agents strictly isolated.