The patience and dedication required to input a Konami code on a portfolio site is genuinely impressive. I respect you.
India 🇮🇳 · Self-Taught Developer · Since 2017
I build Telegram bots, automate things that shouldn't be automated, and write Python that — against all odds — runs in production. Available for hire. My maa still thinks I fix computers.
I'm Paidguy — a developer from India who learned to code by breaking things, Googling furiously, and refusing to give up at 3am. No CS degree. No bootcamp. Just Stack Overflow, stubbornness, and a serious chai problem.
I specialise in Telegram bots (the kind that actually work, not the kind your cousin made in 2021 that crashed on the first message), automation scripts, and web development.
My commit messages are a historically accurate record: mostly just "fix" repeated until something stops breaking. Occasionally "hotfix" when I broke the first fix.
Advanced bots built with Pyrogram. Content restriction bypass, media handling, FloodWait protection, userbot automation. The kind that don't crash when someone types in Hindi at 3am. Tested under actual conditions.
If you're doing something manually more than twice, that's a script waiting to happen. API integrations, scrapers, file processors, scheduled jobs. I automate boring stuff so you can be bored differently.
Responsive sites that load before users abandon them. I've centered more divs than rotis consumed. That is a lot of divs. Clean code by my standards, which are negotiable but higher than zero.
I nod confidently while secretly opening three new Google tabs. I will ask you to repeat the important parts once, then twice, then again on WhatsApp at 11pm because my notes say "bot thing with the stuff".
// chai: 1 consumed. google tabs: 7. confidence: manufactured.
This is always a lie. Nothing is ever simple. But saying it out loud makes both of us feel better for exactly 4 hours before reality arrives, uninvited, without even taking its shoes off at the door.
// actual complexity: 3× estimated. timeline: "it depends".
Staring at code that worked fine until I "improved" it. I will blame the environment, the library, BSNL outage, IRCTC API, Mercury retrograde, and finally myself. The answer was on line 47 the entire time.
// solved while making chai. it is always solved while making chai.
Deployed. Working. I am not touching it again. Future changes are a new project, a new quote, and a new small personal crisis. If it breaks on a Sunday, I did not deploy on a Sunday.
// git push main. laptop closed. weekend secured. responsibility: dissolved.
"He sent the bot at 2am with a message that just said 'it works'. No docs. No explanation. No hello. It works perfectly. I am afraid to ask questions."
"I asked for a small automation script. He gave me exactly that. It ran first try. I do not know how to explain this. I have accepted it as a miracle and moved on."
"My cousin quoted me 5x the price for half the features. Paidguy built the whole thing in a week. My cousin has blocked me on WhatsApp. It was worth it."
You have a budget. We will find it. Possibly behind the sofa cushions. Maybe in your savings account. It's somewhere.
You respect timelines. I'll respect yours. We'll both pretend this was straightforward. The code will disagree.
"It won't take long yaar." Famous last words. Chronologically always the last words.
sudo reboot?
No? Do that. If it fails, buy a new one. That is my complete professional advice
on this matter and I will not be taking questions.
Got a project? A haunting bug? A bot idea you've been sitting on for four months? Send a message. I reply fast during IST hours. Slower on weekends. Never on Diwali — that is fair, non-negotiable, and absolutely final.