● hi, I'm Dev — a workshop, not a portfolio
The name says developer. The CV doesn't. I build Discord bots, community control panels and the odd party game anyway. Careful checklists, a lot of reading the docs, and everything written down.
Every one of these runs on a single small server I look after myself. Some are public, some are behind a staff sign-in.
Spot the red flags, fill the card, shout bingo. Share a card code, or start a watch party and play along together in real time.
The control panel for the 1stMD Discord community: logging, thread watching, server analytics and self-cleaning temporary voice rooms — all managed from one place.
Players press a button, paste their game ID and privately see whether their VIP is active and when it ends. Read-only by design.
Event sign-ups for a partner community, plus a roadmap bot that keeps a server's plans in one tidy channel.
My own workbench: a sync desk and a bot dashboard for keeping an eye on everything else.
I can't lean on years of instinct, so I lean on habits instead. Four of them do most of the work.
No script touches the live server until I've read every line of it and know what it changes.
Things get built and checked in isolation first. Live only changes once the tests pass.
Each release keeps the previous version and a rollback path, plus encrypted off-site backups.
Read-only containers, no spare permissions, memory caps and staff-only panels by default.
"Not a dev" isn't an excuse. It's the reason I write everything down.