Python engineer. I build async backends, real-time integrations and automation — and the tooling that lets AI models actually do things: MCP servers, agent memory, multi-agent coordination.
I like software that is boring in the right places: typed, tested, and predictable under load.
class Rufus011:
focus = ["async backends", "real-time systems", "AI agents & MCP"]
stack = ["Python", "asyncio", "socket.io", "pydantic", "pytest"]
tooling = ["ruff", "mypy", "GitHub Actions", "Docker"]
principle = "typed · tested · no secrets in the repo"
speaks = ["ru_RU", "en_US"]
def looking_for(self) -> str:
return "interesting automation problems · open-source collaboration"Important
Now building: MCP servers & multi-agent tooling. Hacking on the same? My DMs are open → @romis_111
%%{init: {'theme':'dark','themeVariables':{'primaryColor':'#0d1117','primaryTextColor':'#c9d1d9','primaryBorderColor':'#a277ff','lineColor':'#ff6ac1','fontFamily':'monospace'}}}%%
flowchart LR
R(("RUFUS_011"))
A["⚙️ Async backends<br/>asyncio · websockets"]
B["🤖 AI agents<br/>MCP servers · tooling"]
C["🔌 Integrations<br/>REST · socket.io · scrapers"]
D["🧪 Quality<br/>pytest · mypy · ruff · CI"]
R --> A & B & C & D
style R fill:#0d1117,stroke:#a277ff,color:#a277ff
style A fill:#161122,stroke:#a277ff,color:#c9d1d9
style B fill:#161122,stroke:#ff6ac1,color:#c9d1d9
style C fill:#161122,stroke:#56d4ff,color:#c9d1d9
style D fill:#161122,stroke:#a277ff,color:#c9d1d9
Async backends — event-driven clients that stay alive: reconnects, backpressure, no polling loops. AI agents — MCP servers, persistent memory, and coordination so several models can work together. Integrations — talking to APIs that don't want to be talked to. Quality — offline test suites, strict typing, CI that actually catches things.
📈 more stats — activity graph & trophies
Tip
Everything I publish is MIT and free — a ⭐ on a repo is already plenty.
Open to collaboration and interesting problems.
