All of my long-form thoughts on programming, leadership, product design, and more, collected and organized for you on a chronomlogical order and love what you do.
A single curve for thinking about AI slop: why it rises with capability, why it peaks and lingers around AGI-shaped systems we cannot yet govern, and why it eventually decays while intelligence keeps climbing.
Why I built FarmJS around rendering choices, typed server contracts, and product integrations, and how that grew into multiple renderers, agent-readable apps, and an experimental AOT React compiler.
Why I built @farming-labs/docs, what makes its open-source, themeable, token-efficient architecture AI-native, and what we learned using Docs Cloud while it serves private-beta teams.
The choice between React Server Components and client-rendered data is workload-dependent. This post designs a representation-aware transport system that can choose HTML, raw data, or Flight per route segment using AOT analysis, guarded JIT selection, cache state, privacy, and real measurements.
Why I built @farming-labs/grag: a TypeScript-first GraphRAG package with relational storage, provider-agnostic models, inspectable retrieval, hybrid retrieval paths, and stronger grounding for answers.
a thinking behind on why I built orm.farming-labs.dev: a storage-agnostic ORM layer with one unified DSL, generated outputs, and runtime drivers across many stacks.
RSC is a serialization and streaming model for UI, not a runtime. This post explains why RSC is stateless by design, then explores Trial #1: externalizing navigation memory into Edge KV so the server can remember what it already fetched—without making the stream stateful.
Language interoperability is the most important technical problem of the next decade. Explore how Rust is becoming the performance core for high-level languages like JavaScript and Python, why FFI matters more than ever, and how tools like napi-rs are enabling one high-performance core with many language frontends.
Directives like "use workflow" and "use step" are not JavaScript features, they're compile-time execution boundary markers. This post explores why they exist, how they differ from function wrappers, and why determinism requires explicit boundaries.
Server Actions feel like local function calls, but they're actually network requests. This deep dive explores what really happens under the hood: the client proxy, the RSC payload format, POST-only semantics, and the trade-offs that shape developer experience.
Exploring Cloudflare's Durable Objects — a carefully constrained coordination primitive built to work within the hard limits of V8 isolates and edge security. Learn why they're imperfect but fascinating, and how they solve distributed state problems differently.
Exploring React Server Components (RSC) and the new mental models in React and Next.js. Learn how RSC transforms the traditional client-server architecture and enables modern UX with a server-driven approach.
Bun is a fast and comprehensive toolkit for JavaScript and TypeScript development. It is designed to handle various tasks involved in the development process, including running, building, testing, and debugging applications
Let's talk and discuss more about my project and my experience on farming the modern technology
