HUGO.CHARMIES(1)
PRODUCTION
$ hugo --whoami
Full stack developer in Belgium. I build internal tools that replace manual and paper-based work, most recently at Vanwezel Autoparts.
$ hugo --status
status : ● Open to full stack roles location : Limburg · Belgium daily_driver : Claude Code favourite_stack: Next.js · Postgres
$
$ hugo --now
$ hugo --featured








$ hugo --stack
AI
────────────
FULL STACK
────────────
INFRA & TOOLS
────────────
$ hugo --origin
I studied Applied Computer Science in Leuven. For a school project, a client needed indicators scraped from the web, which was all manual work. I automated it with an AI model and saw how much faster you can build now.
Since then I build with AI coding tools like Claude Code, and I test and review what they produce. What I like most is finding a slow process and replacing it with a small app.
EDUCATION
UC Leuven Limburg
BSc Applied Computer Science · 2022–2025
FIRST AI PROJECT
Ecofoodmap · n8n → code-native
WAY OF WORKING
Claude Code, then test and review
$ hugo --archive
$ hugo --contact
$ open ~/projects/vanity-handle-bot
HUGO.BOT(1)
STACK
Python · python-telegram-bot · pyrogram · aiohttp · aiosqlite · Docker
01 / 04
The brief. An operator client runs a marketplace for good-looking handles across Telegram, Discord, YouTube, Instagram. He needed a bot to take ad submissions, an approval workflow, a way to publish to the right channel, and a clean admin surface his operator self could actually use.
02 / 04
What I shipped. A conversational submission flow on Telegram with a proper state machine, an admin approval pipeline that DMs the submitter on accept or reject, automated publication to the marketplace channels with rich formatting, a web admin for the operator to manage everything from a real UI instead of bot buttons. Live in production with real buyers and sellers.
03 / 04
The architectural detail I'd point at. Telegram has two kinds of clients, bots and user-accounts. Bots get a clean API but are restricted in where and how they can publish. User-accounts can post anywhere but don't have the bot UX surface. The bot here uses python-telegram-bot for the conversation and inline buttons. The publisher uses pyrogram as a logged-in user-account, in the same process, to actually post listings to channels with the formatting Telegram bots can't do. Two clients, one process, each picked for what only it can do. Plus an aiohttp server inside the bot for the web admin to call.
04 / 04
Why this is here. It's outside my usual stack. I live in TypeScript and Next.js. This is Python, async, two Telegram client types, a marketplace moderation workflow. Range across platforms, not just across languages. The frontend I show on other projects is what I do most. This is what I do when the problem doesn't fit it.
SCREENSHOTS
$ Operator's name kept private. Bot live, ads circulating.