Writing Notes
Engineering notes on offline protocols, AI infrastructure, deployment systems, and reliability choices drawn directly from shipped work.
05
Writing notes seeded
04
Core technical themes
368
LeetCode problems solved
Writing Direction
Use the blog to explain why these systems were designed this way.
The strongest portfolio writing is not motivational filler. It documents tradeoffs, constraints, benchmarks, and architectural choices in a way that lets other engineers see how the system actually behaves.
Turn resume bullet points into technical essays with proof and context.
Explain distributed systems tradeoffs through concrete shipped examples.
Use writing to connect protocol work, infra choices, and product decisions.
Perspective
If the systems work is real, the writing should make the tradeoffs legible instead of just sounding impressive.
WRITING STANDARD
Themes to Expand
Offline payments
Protocol design and failure modes.
AI infrastructure
Cost, latency, batching, and provider reliability.
Developer platforms
Deploy loops, queues, and self-hosted tradeoffs.
Systems thinking
Why transport and architecture decisions shape product UX.
Blog Seeds
Blog Seeds
Writing Note
Designing an Offline Wallet That Still Settles Trustlessly
From transport choice to on-chain resolution
A systems write-up on making wallet UX survive disconnection without handing trust back to a central relay or coordinator.
Writing Note
What 300-Device Mesh Trials Taught Me About Reliability
Testing beyond toy demos
A note on why distributed transport demos break in the messy middle and what changed after validating relay behavior across five hops.
Writing Note
Reducing AI API Cost by 40% Without Breaking UX
Batching, caching, and rate control
A backend-oriented explanation of how request shaping, Redis controls, and cache-aware architecture can cut spend while preserving output quality.
Writing Note
Self-Hosted PaaS Deploys in Under 60 Seconds
Layer caching done right
A practical breakdown of deploy pipeline decisions that materially reduce iteration time for self-hosted developer platforms.
Writing Note
Streaming Agent Responses Under 500ms
Prefilling, context extraction, and perceived latency
An engineering note on making always-on assistants feel immediate through event pipelines, incremental delivery, and better context boundaries.