I've been writing code since 2015 and using GitHub since 2018, back when most people my age didn't even know it existed. I've contributed to so many systems over the years that I genuinely can't remember half of them. If you worked with me on something and I don't remember it, it's not you, it's me. (It's probably also the codebase.)
- The early days: HTML, CSS, jQuery and vanilla JS. Every website I made had a marquee tag somewhere. I'm not proud of it.
- The Bootstrap era: Laravel + PHP + Bootstrap. Every site I built looked like every other site on the internet, and that was the whole point.
- The bachelor's degree: I used so many tools, languages and frameworks I couldn't name them all if you paid me. Some of them probably don't exist anymore.
- The game dev arc: Unity and C#. I made games, wrote stories inside games, and built algorithm visualizers so you could watch BFS, Dijkstra and A* find their way around a map (and occasionally walk into a wall).
- The XR phase: Built XR stuff with Unity and ARCore. Waving my phone around at empty rooms like a lunatic, for science.
- The framework buffet: React, Svelte, Next.js, visual scripting. I tried everything on the menu.
- The industry years: Full-stack on MEAN (Angular + Express) and MERN. Python with Django, Flask and FastAPI at various points of my life, depending on which version of me you ask.
- The fun bits: Rust, Axum, Three.js, GSAP. I also ran game servers with a ridiculous amount of load on tiny AWS free-tier boxes. Jeff Bezos owes me one.
Where I landed: Axum + SvelteKit. That combo is the bomb, and I'll fight you on it.
I used to love coding. That moment when something finally works after hours of staring at it? Unbeatable.
These days AI writes most of the code, and "coding" is basically me having a long conversation with Claude. Kinda boring, not gonna lie. But it taught me something: coding was never the passion. Building things was.
So now I spend my brain cells on what AI can't just autocomplete for me:
- RAG and other AI-native ways of building things
- System design: how the big boys actually architect stuff
- Concurrency, caching, load balancing, and the algorithms behind them
- How systems survive millions of users without catching fire
Running my own business and building systems that automate and manage it, using my own products. Eating my own dog food, and it tastes alright.
I also take on freelance projects to keep the building itch scratched. I did the 9-5 thing. It felt like slavery with a dental plan.
Time > Money. Every time.
|
Infor |
Kerner Norland |
Accario |
Bluewave |
|
WD Strategies |
AdLever |
Open edX |
Vinovalab.ai |
- avaia.design: my agency. We make websites for personal brands, hotels and e-commerce folks.
- teyabeach.com: Teya Beach Hotel's website. Its job is to make you want a vacation and then book one.
- acekavi.me: my little corner of the internet. Portfolio, blog, occasional rants.
- Crypto: trading bots, backtesting and research tooling. No, I'm not rich yet.
- booking-extranet-bot: automates the Booking.com extranet, 2FA and all, so I never have to click through it again.
- grubsi: a restaurant and bar POS written in Rust, because why not.
- keytide: an IAM microservice for auth. It decides who gets in.
- tradingview-mcp: lets AI poke at TradingView so I don't have to.
Not pictured: the dozens of things I used once in 2019 and immediately forgot.
- Portfolio: acekavi.me
- Blog: acekavi.me/blog
- LinkedIn: linkedin.com/in/acekavi
If I've gone quiet on GitHub, I'm not dead. I'm probably busy with client work or my business, or arguing with an AI about why my code broke.
obsession beats talent

