My Plate

I'm building my foundation here — how well I control the language and runtime. Most engineers write Go; I want to actually understand concurrency. Everything I build above this depends on getting this right.

I'm learning to build services that can handle thousands of requests per second — HTTP architecture, middleware, caching, and the patterns that make backends production-ready.

I'm moving beyond single-service thinking. Message queues, event-driven design, idempotency — this is how large systems actually work. It's the layer I'm pushing myself to reach.

I'm learning to turn code into real production systems — logging, metrics, tracing. My goal: services I can actually operate and debug when things go wrong.

This is where my backend experience becomes a weapon. RAG, embeddings, agent orchestration — I'm combining AI with systems engineering. It's a niche I'm betting on.

I'm building my foundation here — how well I control the language and runtime. Most engineers write Go; I want to actually understand concurrency. Everything I build above this depends on getting this right.

I'm learning to build services that can handle thousands of requests per second — HTTP architecture, middleware, caching, and the patterns that make backends production-ready.

I'm moving beyond single-service thinking. Message queues, event-driven design, idempotency — this is how large systems actually work. It's the layer I'm pushing myself to reach.

I'm learning to turn code into real production systems — logging, metrics, tracing. My goal: services I can actually operate and debug when things go wrong.

This is where my backend experience becomes a weapon. RAG, embeddings, agent orchestration — I'm combining AI with systems engineering. It's a niche I'm betting on.