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
August 2024 - Present
Source: GitHub
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 AI. But wait, not just because AI is a buzzword, but because it allowed me to parse tasks from speech-to-text requests made by the user without a hard-coded syntax for the user to follow.
Utilizing Rust, I was able to build a comprehensive simulation that matched the real-world operations of aircraft and ATC. As the game grew, the scope started to change. Focusing more on the gamification aspect of Airwave, I rebuilt it to feature airport-management strategies rather than the OG idea of building an ATC MMO-style simulator.
Quip
April 2026 - May 2026
Source: GitHub
Quip is a dynamic lisp-like language born out of the dream of building a usable language that was highly embeddable and strict in it's ruleset, making it infinitely expandable.
A spiritrual successor to Stack (see below), Quip was a reincarnation of the same principles but with a constrained scope and direction.
Stack
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.
Replit Testimony
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 5 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. They assured me that it wasn't due to performance or anything on my end. Their stated reason was to "restructure the support team". So, I've been enjoying my time off, working on Airwave, Stack, and other projects, along with applying to jobs once in a while. If you are reading this and you know a guy (or you are the guy), I'd love to hear from you!