full-stack, mostly typescript, too invested in the details.bucharest. shipping things, breaking things.
Starless
King Crimson
a few things i've made.
reads the news all day so you don't have to scroll it
miez is the core of a thing, what's left once you take the crust off. that's the whole thesis: read widely, condense, then stop. a feed you can actually get to the end of.
most of it is pipeline, kept cheap enough to just run without anyone watching. web and mobile come out of one turborepo. biggest thing i've built, still changing most weeks.
typescript · tanstack start · convex · better auth · vercel
twelve hours, one take, first place
adobe's hackathon gave us twelve hours, which isn't enough time to design anything twice. every decision had to be the one that shipped.
feed, messages, notifications: three easy features and one state-management problem. we leaned hard on agentic tooling to hold that pace, and it won first place.
typescript · next.js · convex · clerk · openai api
twenty people, one repo, nobody lost
i led twenty engineers on this, and the hard part was never the code. at that size the git history is the real architecture, so that's where the evenings went.
what i'm proudest of isn't in the repo: people who had never shipped anything shipped something, and most of them stayed.
react · node.js · git
a photo of a sick plant goes out, an answer comes back
romanian farmers are not going to install your app. whatsapp is already open all day, so that's where the tool had to live.
weather for the specific crop, live cereal prices, a plant diagnosis from a photo taken in the field. it runs on cloudflare workers, close to free, which is how a tool with no revenue survives.
typescript · hono · drizzle · cloudflare workers · gemini api
an item, a country, one number to get right
something ordinary, sold somewhere specific. guess what it costs there. that's the entire game.
wordle's shape, because being 4% off and being 400% off are not the same kind of wrong and the game has to say so. turns out it isn't about prices, it's about how expensive you think a place is.
give it a word, it gives you a bad joke about it
my internship project at ubisoft: give it a keyword, get a joke back. the brief was genuinely that.
first time i'd wired a model into a product, and the lesson was how much of the job sits after the api call. shipped in docker, also a first.
react · openai api · docker
notes to myself, and four jobs told the wayyou'd tell them at the bar, not on a cv.
four lines, two still open
rasirom r.a.still open
react and next on top, spring boot and fastapi arguing over kafka underneath, keycloak at the door. i now know exactly what a real permissions model costs.
solo, building my own thingsnights and weekends
my own products, end to end. nobody briefed miez.news, so every call in it is mine to get wrong, and most of what i know about shipping came from that.
sisc, cybernetics students' union20 months
started on the back end in node, ended up leading twenty people, most of whom had never shipped anything. nobody got lost. some merges did.
ubisoft romania3 months
they asked for a chatbot that tells jokes. i learned the api call is the easy ten percent.
ase bucharest, cybernetics
i'm flavius. full-stack, mostly typescript, and i've never shaken the feeling that the details are the whole job.
i've led a twenty-person dev team, my day job is deep inside a platform a lot of people lean on, and every hour left over goes into products of my own.
away from the keyboard: hiking, chess i take far too personally, and reading the health papers rather than the headlines about them.