Full-stack developer passionate about building elegant solutions to complex problems. I specialize in modern web technologies with a focus on creating scalable, user-centric applications.

A real event platform built by someone who actually ran events. After years of fighting with bloated event software that charged per feature and held data hostage, I built what I wished existed - a platform that respects both organizers and their communities. Self-host it and create your own branded event ecosystem (perfect for streamers, companies, or anyone wanting their own space), or use the cloud version to tap into cross-organization networking. It's completely open source because I believe nonprofits shouldn't have to choose between good tools and their budget, and organizations shouldn't need a vendor's permission to access their own data. Whether you're running a 10-person meetup or a thousand-person conference, Atria adapts to what you actually need - not what some pricing tier dictates. No feature bloat, no vendor lock-in, no surprises. Just a solid platform that puts your event first and gives you the freedom to run it your way.

• DS&A Practice: Working through Grind 75 for technical interview preparation

• DevOps: CI/CD pipelines: Automated testing (Frontend/E2E)
• Atria: Adding Redis cache strategy to reduce database load and improve API response times
• AWS/GCP Cloud Services: Expanding beyond self-hosted infrastructure to cloud-native solutions
• GraphQL & Apollo: Building more efficient APIs with better client-server communication
• Data Engineering & ETL: Building robust pipelines to normalize messy third-party API data into clean, actionable datasets
• TypeScript Mastery: Building upcoming projects with goal of 100% type safety

• Atria: Updated streaming player integration (Jitsi as a Service, "Other" - external link)
• Testing Strategies: TDD on future Atria features
• Atria: Updated streaming player integration (Zoom, Mux - signed and public, Vimeo)
• Atria: Systematic refactoring and ESLint compliance to eliminate code smells and enhance maintainability
• Atria: User facing Docs, Blog/Release Notes, API reference (in preparation for a 0.1.0 release along with a more standardized release schedule)
• Atria: Kubernetes hosted Dev stack for 1:1 testing before pushing to production
• Atria: Prepare for scalability via query efficiency, connection pooling, and Redis implementation
• DevOps: CI/CD pipelines: Automated testing (Backend)
• Infrastructure: Multi-node K3s deployment with PostgreSQL HA (CNPG), distributed storage (Longhorn), and automated disaster recovery to Backblaze B2

"The purpose of architecture is to defer decisions, not to make them." — Robert C. Martin