Sixteen years old. Five years on GitHub. One Poco X3 Pro that has been flashed more times than the average router gets restarted. I write small, careful Python — mostly Telegram bots — from a phone in a hill town in Kerala, India, and I keep a quiet +1 BioScience textbook open on the other tab.
Sixteen, self-taught, and terminally curious. Most of what I know I learned by flashing the wrong file at 2 AM and then learning what the right file was supposed to be.
My name is Abhishek Issac. I'm sixteen years old, I live in Wayanad, a green corner of Kerala in southern India where the wifi forgets you exist about twice an hour and the sunsets are usually generous enough to make up for it. I attend +1 BioScience on the NCERT syllabus, which means my school week is divided fairly evenly between Botany, Zoology, Physics, Chemistry, Maths, English, and Hindi — and the rest of the day belongs to the laptop.
I write code in Python, mostly Telegram bots, on top of Pyrogram. Behind the bots there's usually MongoDB with Motor for the fast-and-forgetful state, and PostgreSQL with asyncpg for the data I refuse to lose. Almost all of it gets typed on a Poco X3 Pro running Termux, sometimes connected to a Bluetooth keyboard, sometimes not. The Poco is technically a phone but at this point it has spent more of its life being a development machine.
Outside the editor I am a professional ROM tourist — I have flashed, unflashed, dirty-flashed, EDL-rescued and OrangeFox-sideloaded my way through MIUI, HyperOS ports, crDroid A15, Project Infinity X, crDroid A16, and finally the OxygenOS 15 port for vayu/bhima that I'm currently sitting on. I keep KernelSU on top of all of this for root and a small collection of Magisk-style modules for school apps and games.
I prefer hand-built things over generated ones — this site, for example, is a single HTML file, a single CSS file, and a single JavaScript file. No frameworks, no build step, no telemetry, no shortcuts. The numbers you see (repo count, stars, languages, recent commits) are pulled live from the GitHub REST API at page-load. The contributions snake gets rebuilt by a GitHub Action every twelve hours. Everything else is copied carefully out of a private notes file I keep on the same phone I'm typing this from.
# whoami.py — the very short version from life import Person, Telegram, Android me = Person( name="Abhishek Issac", from_="Wayanad, Kerala, India", age=16, school="NCERT +1 BioScience", subjects=["biology", "physics", "chemistry", "maths", "english", "hindi"], stack=["python", "pyrogram", "mongo", "postgres"], phones=["poco x3 pro", "moto g52", "moto e5"], rom="oxygenos 15 port (vayu/bhima)", tools=["termux", "git", "orangefox", "kernelsu"], ) while curious: me.build("a tiny telegram bot") me.flash("another rom, carefully") me.study("a chapter of biology") me.push("a small commit to github") # exit code: 0 — still going.
Six small categories — languages, bot frameworks, storage, hosting, Android tooling, and the editor I open before the kettle finishes boiling. No logo wall, no buzzword bingo.
Python first, almost always. A bit of HTML/CSS and vanilla JavaScript for the web layer, plus shell glue for ops scripts and tiny CLI helpers when I can't be bothered to write a Python file.
Bots and userbots in Pyrogram on top of MTProto, with the Bot API as a fallback. Force-sub gates, batch generators, voice-chat moderation, small Telegram-native games, and the occasional userbot for the things bots can't do.
MongoDB for fast cache layers with TTLs, PostgreSQL for the persistent truth, JSONB for game-state blobs, and SQLite for tiny local tools that have no business hitting a server.
Whatever runs cheapest with the least pain. Easypanel and Koyeb for bots, GitHub Pages for static sites, plus a small VPS for things that need to stay alive between deploys.
Custom ROMs, OrangeFox recoveries, KernelSU root, the occasional Magisk module. Two phones in the testing pile and one backup that lives permanently in fastboot.
Where the typing actually happens. A phone with Termux for almost everything, a laptop when one is nearby, and the same handful of CLI tools every single time.
These bars try to tell the truth. Comfortable means I've shipped real code with it and I can debug it without a search bar. Learning means I've broken things with it and I'm still pulling out of the curve.
I take a small number of paid jobs at a time, mostly from friends-of-friends in the Telegram community. Six things I'm comfortable picking up; everything else I'll gently say no to.
Pyrogram-based bots and userbots. Force-sub gates, file batching, broadcast tools, voice-chat moderation, small Telegram-native games, anti-abuse rules. Mongo or Postgres depending on what survives best.
Caption normalization, quality-tag rewriting, dedup against Mongo, multi-source → multi-destination forwarders, scheduled re-broadcasts. Turning ten ad-hoc admin tasks into one command.
Moving an existing bot from MongoDB to PostgreSQL (or back) without downtime — sync bridges, JSONB schemas, backup & restore commands, and a small admin panel for the people who actually run it.
One-file HTML/CSS/JS sites, deployed on GitHub Pages or Cloudflare. No frameworks, no build step, no surprise tracking. Like this site, but yours.
Walking you through unlocking, flashing OrangeFox/TWRP, picking a ROM with an active maintainer, KernelSU setup, and EDL-unbricking. Mostly Snapdragon Xiaomi/Poco devices and a handful of OnePluses.
Stuck on FloodWait spam, a deploy that won't bind to $PORT, or a Pyrogram session that keeps logging out? I'll sit through one voice chat with you and we'll fix it together.
All of the above happens around school hours. Plus-One BioScience, NCERT syllabus, with these six subjects rotating through every week of the term.
Botany & Zoology — the whole reason this is BioScience and not pure science. Cell structure, plant kingdom, animal kingdom, biomolecules, transport in plants. Heaviest text-book of the lot.
Mechanics → kinematics → laws of motion → work, energy, power → gravitation → electricity. The chapter I always re-read at 1 AM the night before the exam, and one I quietly enjoy.
Organic > Inorganic > Physical, in that exact order of comfort. The mole concept and I have an understanding. Equilibrium and I are still negotiating.
Calculus is friendly, vectors are fine, statistics is a continuing project. The textbook lives next to the laptop and gets opened roughly as often.
I read more than the syllabus and write exactly the syllabus. The compositions are fine; the literature questions are an ongoing argument with the answer key.
Second language. Slow but improving every term. Reading is fine, writing under timer is the goal.
Five public projects you can star, clone, or steal patterns from today. The other ~120 repos on my profile are forks, experiments and small Termux scripts — private repos stay private, no leaks.
A Telegram-based Word Grid challenge bot. Real-time word-guessing sessions across many groups, persistent player stats, daily-refilling hint currency, broadcast tools, and a "Lightning Round" achievement for clearing a grid in under 120 seconds. Migrated end-to-end from MongoDB to PostgreSQL while keeping a sync bridge so existing groups never went down. JSONB settings tables, score-log events, and a small admin panel that costs me roughly nothing to run.
view code →An automated voice-chat moderator for Telegram. A dual-client architecture (Bot + Userbot) watches group calls in real time and enforces join rules, streaming permissions, and anti-abuse policies. It falls back gracefully from userbot mute to Bot-API restrict, deduplicates joins in memory, and writes every decision to a private audit log channel. Anonymous-admin handling is built in because somebody always tries it.
view code →A full Telegram implementation of the Jackaroo (Tock) board game. Four-player partnership matches with persistent state, CPU placeholders for empty seats, special-card rules (4 backward, 7 split, etc.), compact pipe-encoded callback data to fit within Telegram's 64-byte limit, and live rehydration of in-progress games from PostgreSQL after every restart. The kind of project where the rules engine is bigger than the bot.
view code →A high-throughput forwarder that watches source channels, normalizes captions and quality tags through a battery of regexes, deduplicates against a Mongo index, and rebroadcasts cleanly to destination channels — keeping admin workload on movie hubs down to almost zero. The kind of bot that runs for months and only gets noticed when it stops.
view code →The page you are currently reading. Three files: one HTML, one CSS (a small premium-themed system in this case, gold on warm white), and one JavaScript that talks to the GitHub REST API and animates the things you're scrolling past. A scheduled GitHub Action rebuilds the contributions snake every twelve hours. Zero frameworks, zero build step, zero excuses.
view code → view live →Forks I learned from, half-finished file-share bots, music players, request-join handlers, small Termux scripts, and the occasional Magisk module. Some are great references. Some are quiet experiments that didn't pan out. They're all on the profile if you want a tour through how I learned this craft, very publicly, over the last five years.
browse all repos →
Everything below is fetched at page-load from the GitHub REST API or rebuilt on a
schedule by a GitHub Action. Private repository names are excluded by design —
only !fork && !private repos appear.
Computed at page load by counting each public, non-fork repo's primary language. Python comes out on top — usually by a margin that surprises me.
A short and honest list. Three phones, one daily driver, two helpers. No iPhones, no flagships — Snapdragon mid-range from end to end.
Roughly chronological. Some lasted weeks, some lasted three days. The current one is highlighted.
I'd rather have a working version one in production tonight than a beautiful diagram on Monday. The commit graph is my notebook — features land in tiny pieces, and refactors happen out in the open instead of in a long-lived branch nobody is allowed to touch.
Two things get optimized first: uptime for the people using the bot, and readability for whoever has to debug this at 2 AM on a phone keyboard — which is usually a slightly-tired version of me. Everything else is negotiable.
Not testimonials, not catchphrases. Three sentences I've said out loud often enough that they've quietly become how I work.
Ship the smallest version that helps a real person. Iterate from feedback, not from a whiteboard.
If a script can run on a 6 GB phone over flaky 4G, it can probably run anywhere I'd ever deploy it. Optimize for the worst environment first.
Future-me reading this code at 2 AM has zero patience for cleverness. Plain functions, named variables, boring patterns.
Only verifiable dates. Pre-2021 is intentionally blank — I was learning then, but nothing public, so I'm not going to invent dates I can't prove.
Account created on 2021-11-08. Early commits were shell scripts, half-broken file-share bots, and a fairly long list of forks I used to read other people's code from the inside out.
Years of small-to-medium Telegram bots — autobatch, request-handlers, file-share variants, a series-fetcher that taught me regex the hard way. MongoDB with TTL caches became the default. Most of these repos are still on the profile.
Migrated the whole word-grid bot to PostgreSQL with a sync bridge. JSONB settings, score-log tables, and the first proper backup/restore commands I'd ever written.
Most of the codebase work paused while biology, physics, chemistry, maths, English and Hindi took over the calendar for a few weeks.
Bot + userbot voice-chat moderator on top of MTProto raw. Falls back from userbot mute to Bot-API restrict, deduplicates joins, writes audit logs to a private channel.
From MIUI 13 → HyperOS 3 port → crDroid A15 → Project Infinity X → crDroid A16 → OxygenOS 15 port. Six custom ROMs in two months without losing a kernel.
4-player partnership board game on Telegram. PostgreSQL JSONB for game state, compact pipe-encoded callback data, and live rehydration of in-progress games on every restart.
This site, rebuilt from scratch in a heavier white-and-gold theme. Live GitHub data, contributions snake, and a quiet effort to keep my +1 grades from sliding while bots keep shipping.
A loose "now page" inspired by nownownow.com. Updated by hand whenever life shifts gears.
Tightening up Cavin VC Guard, fixing a stubborn $PORT binding issue on Easypanel, and refactoring the movie-hub forwarders to share a single Mongo cache layer.
A bit more Go, a lot more PostgreSQL internals, and how to write Pyrogram handlers that fail loudly instead of silently.
Wuthering Waves on the Poco X3 Pro at medium settings. Long-running campaign in Genshin Impact when the schedule allows.
NCERT +1 BioScience second-term — Botany, Zoology, Physics, Chemistry, Maths, English, Hindi. Three chapters underlined per night, when it actually works out.
OxygenOS 15 port on the Poco X3 Pro, KernelSU root, OrangeFox recovery on standby, Termux as the IDE, JetBrains Mono everywhere.
Small paid Telegram-bot edits, weird automation problems, kind humans, and any contest where I can lose gracefully. DM me on Telegram before anywhere else.
Telegram is fastest. GitHub is best for code. Instagram is mostly memes. Email works if you're patient.