I'm not a dev who just codes. I'm a dev who makes code run on a server, on a network, securely, in production. Mid-level from day one at Babita, because the scope was never just code.
LEDGB exists because I wanted an AI agent that ran on MY PC, using free AI, with no subscription, no provider lock-in. I built what the market was missing.
Every portfolio (V1→V5) was an excuse to learn a new stack. Every volunteer project was a proving ground. No paid course, no bootcamp.
That's why the YouTube channel. That's why this portfolio. Good code without good narrative disappears on GitHub. I'm investing heavily in this part.
Autonomous dev agent. Local-first. Runs on your PC. Uses free AI. Falls back to other free AI on rate limit. Remembers projects across sessions. Telegram-controlled.
Visual and UX analysis tool I use to audit interfaces including this portfolio. Three interfaces over one engine: an MCP server for AI agents, a REST API and an Electron app.
Search and ask questions over your own documents, running locally. End-to-end RAG: embeddings on Ollama, vectors in ChromaDB, orchestration with LangChain and metadata in Postgres.
I keep the whole ecosystem running with a small team: building new features, servers, networks, security, support. Not a job title a one-man stack.
Institutional site rebuilt from scratch, then a V2 when V1 aged. Volunteer work delivered, maintained, no expiry date.
The site you're reading. Stencil + Web Components in light DOM, bilingual PT/EN, prerendered and tuned to be found by search engines and AI. Successor to V4, faithful to the same visual identity.
Investing in communication as a differentiator. Focus: a Linux-for-servers track, from zero to production.
From fundamentals to real-world scenarios. Hands-on, process happening in real time not a static video. The initial track covers 11 modules:
+ two advanced courses on the roadmap: infrastructure, automation and applied development.
WATCH ON YOUTUBE →At Babita, the same person maintains the backend, the frontend, the Linux servers, the network and security. The whole stack out of necessity and taste.
LEDGB Orchestrator has no team. It's one dev, one Electron app, and the decision not to wait for permission to build what was missing.