English / 한국어
정진호 · TypeScript developer
Author of 『모던 리액트 디자인 패턴』
I turn complex development problems into small, predictable interfaces. My work spans React applications, state and form libraries, and standard-first backend architecture.
I care about the decisions behind the code: where state belongs, how responsibilities are divided, and what makes an API easy to understand. I build tools to explore those questions, then share what I learn through open source and writing.
Read my journal · LinkedIn · My book
Modern React Design Patterns
Wikibooks · July 2026 · Written in Korean
React is easy to start with; designing an application that remains easy to change takes more thought.
In this book, I explore component structure, state management, reusable logic, asynchronous UI, and TypeScript patterns through practical code. The focus is not on memorizing patterns, but on understanding the problems they solve and choosing the right approach for your application.
Small tools that compose, with a core that stays independent.
ilokesto means “toolbox” in Esperanto. I build it as a collection of focused TypeScript libraries for recurring frontend problems, rather than one library that owns the whole application.
The design starts with plain TypeScript cores and thin framework bindings where they are needed. Packages keep their own responsibilities and versions; shared conventions come before shared abstractions. The goal is to make state, forms, and UI behavior understandable on their own and reusable across projects.
Packages are published under @ilokesto/.
| Package | Responsibility |
|---|---|
| store | Framework-independent state storage, updates, and subscriptions. |
| state | State composition and thin bindings for multiple frameworks. |
| form | Form state, field metadata, and Standard Schema validation. |
| utilinent | Small declarative React components for recurring rendering patterns. |
| overlay | Overlay state and lifecycle management. |
| modal | Modal interactions. |
| toast | Toast notifications. |
| fetcher | Fetch-based networking utilities. |
Standards first. Explicit composition. Clear boundaries.
fluo is a TypeScript backend framework built on TC39 standard decorators and explicit dependency injection. I want application structure to be visible in the code: which modules own a feature, which dependencies they use, and where their responsibilities end.
Instead of relying on legacy decorator metadata, fluo declares dependencies explicitly and composes capabilities through packages. The framework core stays separate from host adapters, and runtime support is defined per package rather than assumed. Predictable contracts, testable behavior, and documented limits matter as much as a convenient API.
Package names use the @fluojs/ scope.
| Area | Packages |
|---|---|
| Core | core, di, runtime, config, i18n |
| HTTP & APIs | http, validation, serialization, openapi, graphql |
| Auth | jwt, passport |
| Data | prisma, drizzle, mongoose, redis, cache-manager |
| Messaging | microservices, cqrs, event-bus, queue, cron |
| Realtime | websockets, socket.io, notifications, email, slack, discord |
| Operations | terminus, metrics, throttler |
| Adapters | Fastify, Express, Node.js, Next.js, Bun, Deno, Workers |
| Tooling | react, cli, testing, vite, studio |
Projects I've contributed to through code, documentation, and proposed fixes.
| Project | Focus |
|---|---|
| stableref | React hooks |
| zustand-middleware-pipe | Zustand middleware |
| senpi | Coding agents |
| oh-my-openagent | Agent orchestration |
| open-code-review | AI code review |
Frontend architecture
Component boundaries, state ownership, and structures that stay understandable as applications grow.
Library design
Small APIs, useful type inference, and cores that are not tied to a single framework.
Developer experience
Tools, documentation, examples, and naming that make the next person's work easier.
AI-assisted development
Coding agents and review tools that fit into real development workflows.
I write to make the reasoning behind software easier to follow — not just how to use a tool, but why it was designed that way.
My journal covers frontend architecture, state management, dependency injection, TypeScript library design, and the trade-offs behind technical decisions.
| Area | Technologies |
|---|---|
| Languages | TypeScript · JavaScript |
| Frontend | React · Next.js |
| Backend | Node.js · Express · NestJS |
| Testing | Jest · Vitest |
| Infrastructure | AWS · Vercel · Netlify |
| Development | Git · GitHub · pnpm |
AWS Certified Solutions Architect