Engineering notes
Articles for people who
ship the stack
Rewrites on React, Node.js, TypeScript and AI. A translated body is shown when it exists. If it does not, you see the English text and a note that says so.
Tagged: Code Organization
Building a Feature-Based React Module: Posts CRUD with TanStack Query
Organize a React app by feature, not file type, then wire full posts CRUD with TanStack Query and axios, and see exactly where that pattern stops scaling.
10 min readFeature-Sliced Design for React: Layers, Import Rules and When to Stop
Learn how Feature-Sliced Design's layers, one-way import rule, thin public APIs and @x cross-imports untangle React codebases, and when to adopt only part of it.
7 min readA Practical Comparison of React Folder Structure Patterns
Feature-based, layer-based and domain-based React folder structure compared side by side, with a plain rule for when to switch as the codebase keeps growing.
5 min read
FAQ
About these articles
Yes. Each piece is an original English rewrite prepared for this site. Structure and code examples follow the source material; prose is rewritten and checked for overlap before export.
English is the source. Another language is shown only when that translation body exists. A missing or empty translation stays in English, including on a localized URL.
New drafts land in the publish queue as they pass editorial checks. Running the site import picks up only new or changed slugs — nothing is duplicated.
Treat samples as illustrative. Validate against your stack and licences before production use. For delivery work, contact us with the brief.
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.