01
I ship whole products, not tickets
Melodius runs on the web, Windows, Linux and Android, with its own audio infrastructure, and I built all of it. I can take something from a database schema to a store listing.
How one app ships to four platformsAbout
Full-stack developer in India. I build music platforms, Discord bots and the infrastructure that keeps them running.
I go by notherhacker online and ItzYourHacker on GitHub. My bio there says it best: if it's repetitive, it's automated. Break. Learn. Rebuild.
My main work today is Melodius, an ad-free music streaming app I build end to end for the web, Windows, Linux and Android, and Krypton, a Discord security and moderation bot. I also built Melodius for Discord, which brings Melodius playlists and stats into voice channels.
Why work with me
01
Melodius runs on the web, Windows, Linux and Android, with its own audio infrastructure, and I built all of it. I can take something from a database schema to a store listing.
How one app ships to four platforms02
Krypton's anti-nuke is tested against real PostgreSQL and real audit-log parsing, including a database outage, thirty simultaneous deletions and two attackers at once.
How the anti-nuke decides who to punish03
Sharded, supervised processes across more than one server, with health checks, backoff and claims in the database so work happens exactly once.
Sharding discord.py across processes04
Audits, design notes and these posts. Decisions come with the reasoning and the known limits, so the next person can change them safely.
Read the blog05
How fast a song starts, whether a remix gets merged into the original by mistake, whether a seek gets you rate-limited. Small things decide if a product feels good.
Making a track start fast06
Hashed and bound recovery codes, constant-time comparison, lockouts in the database, read-only database roles for integrations.
Backup owner codesWhat problem, for whom, and what failure looks like. I ask about the edge cases early.
The smallest architecture that holds up, written down with its trade-offs before code.
In small, reviewable changes with tests for the parts that must not break.
Deploy, log every important decision, and fix what real use reveals.