Process automation, bots, AI integrations. I work in production — meaning my solutions are designed to be resilient, self-healing, and production-ready from day one.
Python · Node.js · Redis · PostgreSQL · Docker · LLM APIs
View projectsAbout
I don't have a CS degree. I have working systems in production. I learn by building — each project is a new problem to solve, new bugs to fix, new knowledge gained.
I specialize in systems that must run autonomously: trading bots, business process automation, API integrations. Things that work on their own after deployment.
Before I deploy anything, I ensure I understand how it works under the hood. It's not about perfectionism — it's about knowing what can break and how to handle it.
Technologies
Asynchronous code that handles thousands of operations in parallel without blocking.
Dual-write architecture: Redis for speed, PostgreSQL for persistence and analytics.
WebSocket, REST API, Telegram Bot API, Discord.js, crypto payments.
Containerization, monitoring, graceful shutdown, auto-recovery.
Portfolio
Telegram bot for real-time cryptocurrency signal monitoring. Filters tokens based on user criteria, tracks price multipliers, handles payments and subscriptions. 24/7 system built for a fintech startup.
Real-time exchange feed, ms response
Redis + PostgreSQL, speed + durability
Flood protection, zero API bans
Reconnect on Redis/WebSocket failure
Wallet verification + NOWPayments
Replaced SCAN with dict lookup
Discord bot with timers, voice notifications, microphone history, and channel management tools. Text commands, slash commands, interactive buttons.
Real-time countdown updates
Warning/end sounds in voice channel
Track who unmuted their mic
Approach
If your idea doesn't make technical sense or there's a simpler solution, I'll tell you. I'd rather lose a contract than watch a client burn budget on something that won't work.
Before I start coding, I need to understand the problem. It's not about perfectionism — it's about knowing what can break and how to handle it before it becomes an issue.
What happens when the server crashes? When the API returns an error? When data is incomplete? I ask these questions before deployment, not after a client call.
A script requires you to run. A system runs for you. I build the latter — with monitoring, logs, alerts, and documentation.
Contact
You don't need a ready spec. Describe the problem — we'll talk about whether automation makes sense, how much it might cost, and how quickly you'll see results.
I reserve the right to decline if a project doesn't align with my expertise or ethics.