I'm a slightly unhinged TypeScript enthusiast who builds things because I think I can do better

I'm a Chicago-based developer who believes TypeScript + Bun can solve 95% of your problems (fight me). When I'm not over-engineering solutions to simple problems, I'm probably messing with my home network or messing around with systems architecture because I find designing complex systems weirdly entertaining.

Check out my commit graph if you want to see what "too much free time" looks like in GitHub contributions. I put a lot of work into my passion projects, though most of them stay private because they're either private or too messy for public consumption.

My repos mostly follow the highly professional "*-lol" naming convention. My public repos are a mix of open-sourced internals from my main project and random stuff I built because something annoyed me enough to fix it:

reliably - A forked and heavily modified Ably Rust crate that I ended up reverse-engineering from scratch after the original went stale. Built it to power the real-time messaging layer in my main project. I (and by I, I mean Claude) had to dig through the Ably TypeScript SDK and hand-roll the WebSocket protocol implementation using tokio-tungstenite because no maintained Rust client existed.

chat-lol - I built this purely because I was bored one day and figured I could outdo my friend at making a P2P chat webapp. It started as a casual challenge but turned into a suprisingly decent real-time messaging platform.

data-lol - My teacher last year had these Python scripts we needed to run for class, but I didn't feel like waiting a whole minute for the web running environment to load on my Chromebook every single time just to run a simple script. So naturally, I ported the entire thing to NextJS, made it look actually good, and deployed it.

Most of my other repositories are private because they're either personal projects or experimental code that's too messy for public consumption. I have standards... sometimes.

I'm currently working on a massive web automation project that's somehow reached 30,000+ lines of TypeScript (only on the backend!) and keeps growing. This thing has been my main focus for nearly a year at this point and it's turned into quite the engineering adventure.

I built a custom command and queue system using a Rust-based load balancer. Instead of taking traditional HTTP web requests, it monitored a PubSub channel for new "jobs" and then dynamically figured out what node to send each job to based on active nodes in the database. I had to build this from scratch because I couldn't find any existing system that could handle the specific needs I had (specifically, I needed something completely infrastructure-agnostic. Compute nodes could spin up anywhere without port forwarding, firewall rules, or any network configuration, since all communication ran outbound through a PubSub channel. This also meant backend nodes stayed completely dark to the outside world, with zero exposed attack surface). Due to the long time horizon of web automation jobs, I couldn't find any load balancer capable of handling my super dynamic workload patterns.

• I made my username ogyeet10 when I was 10 years old (hence the 10) and I've been slowly migrating away from it across platforms
• GitHub will let me change my username and auto-redirect the old one, but it breaks a bunch of existing links so I just haven't bothered yet
• My home network setup probably rivals some small businesses in terms of features and monitoring

• Twitter/X: @aidan0x13 (preferred for DMs)
• Discord: @ogyeet10
• Email: aidanml05@gmail.com
• Instagram: @aidan0x13
• TikTok: @ogyeet10

Want to argue about why TypeScript is superior to everything else or discuss why I built my own load balancer instead of using existing solutions? My DMs are always open.