Self-taught developer building bots, apps, APIs, automation systems and experimental software.
Type a command to explore. Available: help, whoami, skills, projects, github, journey, contact, clear
Tuku is a self-taught developer who started by experimenting with code and gradually moved toward understanding architectures, debugging failures, working with APIs, deployment systems, bots, Android applications and automation.
This portfolio presents an evolving engineering journey — not pretending to be an already-finished expert. Every project here is a step in the process of building, breaking, debugging, and learning.
The philosophy is simple: "I don't just learn technologies. I build things with them."
Every project follows the same cycle — from raw idea to deployed reality.
Projects chosen for technical significance — not repository count.
A Telegram-driven DNS management workflow. Control Cloudflare DNS records directly from a chat interface — add, update, and delete records without leaving Telegram.
An automated payment verification system exposed as an API. Handles verification workflows, reduces manual checks, and integrates with external services for real-time validation.
A Telegram bot that serves as a storefront for codebases and developer resources. Demonstrates bot-based commerce, file delivery, and user interaction flows inside Telegram.
Experimentation with AI endpoints and developer-friendly API wrappers. Explores how different models can be unified behind a consistent interface for rapid prototyping.
A Telegram-driven project hosting concept. Deploy and manage hosted projects through a conversational interface — bringing deployment controls into the chat.
Built for constraints — lightweight experiences targeting slow networks, low-storage devices, and keypad-phone users. A demonstration of "build for constraints" philosophy.
Different stages of the same journey — from experimental archive to current focus.
Not a formal résumé — a timeline of learning by doing.
Familiarity indicators — not precise proficiency percentages.
Real data from public GitHub profiles. Loading states and failures are handled gracefully.
How the pieces connect — from bot interfaces to deployment infrastructure.
Reach out through any of these channels.