Current Focus

What I am building, learning, and getting better at.

What I'm Currently Building

This repository is a founder-outreach AI knowledge base designed as a single source of truth for an AI outreach agent that maps my engineering experience, projects, and skills directly to startup problems.

The core idea is that founders do not buy skills; they buy solutions to bottlenecks.

The system analyzes a startup, infers likely engineering challenges, matches those challenges to evidence from my past work, and generates highly personalized founder outreach.

The repository contains profile, experience, skills, interests, achievements, project deep-dives, startup analysis frameworks, outreach guidelines, and prompts for startup analysis, problem matching, and DM writing.

The workflow is straightforward: analyze the startup, infer the hardest technical bottlenecks, match those bottlenecks to project evidence, and generate a concise outreach message.

I think of it as a blend of applied AI, knowledge design, structured prompting, and engineering positioning. It treats portfolio content as reusable structured intelligence instead of static resume text and reflects how I like to productize technical knowledge.

What I'm Learning

Building highly scalable automated workflows that can move complex work off the request path without losing clarity or operational control.

AI and LLM integrations with an emphasis on applied AI systems rather than isolated model demos.

Backend architecture and system design, especially where product behavior depends on strong infrastructure decisions.

Developer tools and platform engineering, including runtime isolation, orchestration, and browser-based tooling.

Distributed systems and execution isolation, both as technical interests and as practical constraints in real products.

Better ways to connect deep technical work to real business bottlenecks so engineering becomes easier to position, explain, and sell.

Tech Stack

Languages

I use these languages across product engineering, backend infrastructure, and systems work.

TypeScript · JavaScript · Go · Python

Frontend

I use the frontend to expose complex backend behavior cleanly, especially in real-time and developer-facing products.

React · Next.js · Vite · Tailwind CSS · Canvas API · EJS · HTML

Backend

My strongest work centers on APIs, orchestration, backend workflows, and real-time infrastructure.

Node.js · Express.js · FastAPI · WebSocket systems · Socket.io · REST API design

Databases and Storage

Most of my systems rely on relational modeling, coordination layers, and storage patterns built for correctness and speed.

PostgreSQL · Redis · Prisma · S3-backed content-addressed storage · AWS S3

Async, Messaging, and Real-Time

A recurring theme in my projects is moving heavy work off the request path and keeping progress visible in real time.

BullMQ · Celery · Redis Pub/Sub · Apache Kafka · WebSockets · PTY streaming · Event-driven backend patterns

Infrastructure, DevOps, and Platform

I am especially interested in the layer where runtime safety, orchestration, and product behavior meet.

Docker · Kubernetes · AWS EC2 · Runtime isolation · Workspace orchestration · Sandboxed execution environments

Systems and CS Foundations

I care about the fundamentals behind reliable systems, not just the frameworks used to expose them.

Distributed systems · Raft consensus · Fault tolerance · State machines · Transactional integrity · RBAC · Performance optimization · Indexing and schema design

Personal Edge / Engineering Strengths

Asynchronous job processing and pipelinesSandboxed code executionReal-time status streamingComplex database modeling and optimizationMonetization and access control systemsWorkspace orchestration and isolated runtime environmentsDistributed consensus and fault toleranceReal-time peer-to-peer communicationTransactional backend systemsHigh-volume data streaming and brokeringComplex state synchronization