I am a developer (Rust & TypeScript), music artist, and multimedia enthusiast. I have been programming in TypeScript for 9 years and switched to loving Rust about 4 years ago (it happens). Most of my projects start from what I call "dumb ideas" that are usually ambitious in the beginning, but can end up working spectacularly.
Projects
Airwave
Development: August 2024 - Present
Download: Itch.io
Website: https://airwavegame.com
Airwave is an air traffic control sim-game that aims to make air traffic control fun for the enthusiast and the expert.
Frustrated by the current landscape of ATC games, I sought out to build one powered by your voice instead of directing aircraft with buttons strict text commands. Within a week, the first prototype was born. It was surprisingly fun to play, despite the limited functionality. As I kept building it, however, there was strain on having to support both a Rust backend and a TypeScript (SolidJS) frontend. So around February of 2026, after a much needed hiatus to focus on other work, I began rewriting Airwave into Bevy.
As of now (August of 2026), Airwave has been released to Itch.io under an in-development alpha. The debut release was published on July 20th, 2026. As of now, Airwave supports voice (and text) control, native multiplayer, multi-airport management, and both air and ground control. I plan to continue development of Airwave to expand its feature set and vision, leaning more towards uncharted waters where players are given more responsibilities and roles, optionally handing these off to Auto ATC if they'd like to focus on a subset of them, or bringing their friends to help out.
You can view an in-depth narrative on how Airwave came to be along with the big decisions I made along the way on the blog. I also have a Discord server that you can join to provide feedback, report bugs, get help with Airwave, or simply follow along for the ride.
Quip
Development: April 2026 - May 2026
Source: GitHub
Quip is a dynamic lisp-like language born out of the dream of building a language that was highly embeddable and strict in it's ruleset, making it infinitely expandable. I was frustrated with poorly-implemented DSLs that screwed the developer over once they wanted to implement more than a few if statements and a for loop. Inspired by the composition and native expansion of lisp-like languages, I built Quip to let the developer build their own functionality and behavior, all without leaving the language. This way, the implementor of Quip could provide a functionally small set of intrinsics while still allowing the end user to build anything with those primitives.
A spiritrual successor to Stack (see below), Quip was a reincarnation of the same principles but with a constrained scope and direction.
Stack
Development: December 2023 - July 2024
Source: GitHub
Website: https://vandesm14.github.io/stack (Website and Documentation)
Stack is a dynamic, stack-based, concatenative programming language.
I like to call myself the idea man. I'll have a random idea, such as "How hard is it to make an OS?" or "What if there was a language that implemented the bare-bones and allowed you to build it up from there?". Can you guess which one stuck? Fast forward from mid-December of 2023, I, and my good friend Leon, started on the daunting task to create our own programming language.
Surprisingly, parsing and executing the code was easy. The part I found most challenging was sketching the behavior of the language. Because Stack is incredibly dynamic, the evaluation engine couldn't make almost any inferences about the code, which means I had to find creative ways to get features like scopes (took me many tries to perfect).
Another fun feature was building a debugger with Egui, which allowed us to see inside the language and keep track of every operation (and even go back in time!).
Stack isn't finished and neither am I. I'm still working hard to make it a fully-fledged and usable language.
Ratio Timer
Development: July 2021 - July 2022
Source: GitHub
Website: https://vandesm14.github.io/ratio-timer
Ratio Timer is a dynamic pomodoro-like timer where you define a work:break ratio instead of rigid, fixed intervals.
A long time ago, I tried using a pomodoro timer. They were all the rage. The theory was neat, except for one fatal flaw: If you were in the zone and wanted to work for longer, you'd either have to start another 25min work session or pause the timer, do your work, then only have a 5min break regardless if you worked 25min or longer. I sought to fix that.
It was easy, really. Pomodoro timers use the same exact ratio: 5:1 (for every 5 work minutes, provide 1 break minute) but restrict you under a 5x step of that ratio, giving us the 25min:5min timer we're used to. But if you simply remove that limitation of 5x the ratio, you could have a timer that follows you as you work, giving you just the right amount of break time from the ratio you set. It's similar to a chess clock in a way, where you have two timers with only one running at a time.
To use it, you set a ratio, then you're off. Stay in the work mode while you work, then when you want to take a break, switch to the break mode and enjoy your ratio-perfect break! If you go over your break time, not a problem. It tracks the overage and applies an offset to your work time, showing you how much you need to work to resolve the disparity (more break + not enough work = more work).
Experience
Million
July 2025 - Present
Replit
May 2021 - February 2024
How did I get here?
My journey started on Replit, an online IDE, building tiny web apps, writing games, and my own cryptography system. At the time, I barely knew anything.
However, as I learned the limits of my knowledge, I continued to push forward, learning more and more. Instead of taking a coding class at school or getting a certificate online, I spent my time absorbing everything.
As I progressed, my use of Replit was not only developing apps but also interacting with the community. I climbed my way from being an early adopter, to a moderator of Repl Talk, the forum of the platform.
After graduating high school, I couldn’t find a job anywhere. But, after a Replit event in Discord, I saw that Amjad, the CEO, was still online. Knowing that this was my only chance to DM him (he was seldom online), I quickly wrote up a message on what I was good at and if I could get a job there.
That message marked the beginning of my professional career.
Life at Replit?
After a swift reply from Amjad, I was sent through a set of interviews. Then, one morning, I received an email from HR that had sealed my career as a customer support engineer.
That was many years ago. Since then, I have learned so much from my fellow engineers and from the job itself. Starting out as a simple “Reply to these emails”, I found my way around a full-time job. As things quickly accelerated, I had to keep a fast-paced mindset in order to keep up.
I was involved in hiring the new manager and the other support engineers. Though my title stayed the same, I provided a valuable role in not only communicating with troubled users but developing tools and software for our team.
Less than a year later, we had a new manager. With that, came more hires and changes to the team. We migrated from software to software, decreasing our footprint as much as we could. Through all of this, I was heavily involved in refactoring our integrations and workflows ensuring a smooth transition.
Where am I now?
I was laid off from Replit in late February of 2024, along with a few other members of the support team.