For React and Node.js engineers

AI writes the code. You still make the architecture calls.

Where state lives, where the server boundary goes, what to test, what to log. I'll show you how senior engineers make these calls, with the code to avoid and the code to prefer. Start with two free playbooks.

// fig 0: one feature, two versions
Looks rightAI wrote it
export function OrderSummary({ id }) {  const [order, setOrder] = useState(null);  const [total, setTotal] = useState(0);  useEffect(() => {    fetch(`/api/orders/${id}`)      .then((r) => r.json())      .then((o) => { setOrder(o);        setTotal(sum(o.items)); });  }, [id]);  return <Summary order={order} total={total} />;}
Holds upafter your review
// Server Component: runs on the serverexport async function OrderSummary({ id }) {  const order = await getOrder(id);  const total = sum(order.items);  return <Summary order={order} total={total} />;}// loading.tsx and error.tsx handle the rest
  • 30K+ read The T-Shaped Dev
  • 80K on LinkedIn
  • 8+ years building production systems
  • Author of 2 books
  • 4.9/5 from readers of The Conscious React

Spoke at GitNation, Geekle, React Day Berlin and DevTalks Romania

The problems

Sound familiar?

These four come up again and again in React and Node codebases. All four have a fix you can learn.

01

The AI pull request looks right. You can't tell if it is.

Agents copy the patterns already in your codebase, good ones and bad ones. Reviewing their code is now the job, and it takes judgment about structure.

Fixed by

The Conscious React and The Conscious Node, with AI rules files for Claude Code, Cursor and Copilot

See how the books handle it
02

Every feature makes the codebase harder to change.

Components grow a prop for every design tweak. The components/ folder turns into a junk drawer. Nobody can say where new state should go.

Fixed by

The Conscious React, chapters 1 and 2

Read 3 free tips from chapter 1
03

In the architecture meeting, you go quiet.

You ship features every week. When the talk turns to trade-offs (where data lives, query builder or ORM, when to split a service), you don't have the words yet.

Fixed by

The free React and Node.js playbooks

Get both playbooks
04

It worked in dev. It broke in production.

No timeout on the outbound call, a retry that charges the customer twice, logs nobody can search. Production problems start as design decisions.

Fixed by

The Conscious Node, plus the weekly issue

See The Conscious Node
// fig 1: where state lives

Ship features and watch the wiring.

Drag the slider to ship more features. Flip the switch to see the same app built with the book's rules. Hover or tap a component to trace its wires.

Components wired to the places their state livesIn the AI-generated version, components read and write state in several places at once, and the cart lives in three of them. In the architected version, each component reads from one home.ComponentsWhere state lives<Header /><CartBadge /><ProductList /><Filters /><Checkout /><SearchBox /><Profile /><Reviews />?search= (URL)server cacheuseStateContextRedux storelocalStorage
Components wired to the places their state livesIn the AI-generated version, components read and write state in several places at once, and the cart lives in three of them. In the architected version, each component reads from one home.ComponentsWhere state lives<Header /><CartBadge /><ProductList /><Filters /><Checkout /><SearchBox /><Profile /><Reviews />?search= (URL)server cacheuseStateContextRedux storelocalStorage

15 wires; the cart lives in 3 places

  • reads or writes state
  • the cart, duplicated
  • one home per piece of state
  • the cart's one home
  • not built yet

The path

How it works

Start free and go deeper when you're ready, with real production code at each step.

  1. Get the playbook for your stack.

    Decision trees for the calls you make every week, and the 10 rules senior engineers follow. Free, 6 or 7 pages.

  2. Read one production problem a week.

    The T-Shaped Dev covers one real problem per issue, with the code to avoid, the code to prefer and why.

  3. Go deep with the book.

    The Conscious React has 100+ tips and The Conscious Node has 157. Every tip shows what to avoid, what to prefer and the reason.

  4. Put the rules where your agents read them.

    The Complete Packages ship CLAUDE.md, AGENTS.md and .cursorrules in every repo, so Claude Code, Cursor and Copilot write code that follows the book.

A real sample

Here's what one tip looks like

That's 1 of 100+ tips in The Conscious React. The Conscious Node has 157 more in the same format.

Get 3 more tips free

The ladder

Pick where to start

Each step builds on the one before, and you pay only when you want to go deeper.

  1. Step 01
    Free

    React and Node.js Architecture Playbooks

    The decision trees for state, data, testing and logging, plus the 10 rules of senior React and of senior Node.

  2. Step 02
    From$29

    The Conscious React or The Conscious Node

    The book alone, in PDF, EPUB and MOBI. The Conscious React has 100+ tips across 6 chapters for React 19, Server Components and the Compiler. The Conscious Node has 157 tips across 10 chapters on architecture, APIs, data, errors, security, testing and performance.

  3. Step 03
    $59each

    The book plus every companion repo

    Runnable Avoid and Prefer examples, case studies, production-ready starters and AI rules files in every repo. React has 4 repos, Node has 3.

Every purchase comes with a 30-day money-back guarantee and lifetime updates.

Proof

What engineers say

"It is a fantastic and easy read with simple to follow guidelines illustrated with examples. The book has been really beneficial and practical for me from day one."

Ivan LebanovHead Of Frontend Developmenton The Conscious React

"Petar's book is excellent for React developers at all skill levels and deserves a spot on every React shop's shelf. Each page offers short, simple, and applicable advice."

Ákos KőművesSenior Software Engineeron The Conscious React

"Great newsletter to help you level up as an engineer! Petar shares very practical insights in a very detailed and understandable way."

Gregor OjstersekAuthor of Engineering Leadershipon The T-Shaped Dev

"By following the best practices mentioned, I now better know how to transform my code from being bloated, unoptimised and messy to being organised, structured and more easily scalable. And thanks to the included explanations I can understand the “why” part of the learning process."

Oliver RichardsonJunior Software Engineeron The Conscious React
// petar ivanovPetar Ivanov, smiling, arms crossed

About

Hi, I'm Petar

I've spent 8+ years building production systems at Fortune 500 companies in cloud, finance and travel, and I've been the CEO and CTO of startups. I've mentored developers from junior to senior to architect, and I wrote two books about that road: The Conscious React and The Conscious Node.

Every promotion I got came down to one shift. I stopped writing code and started solving problems. That's what I write about every week in The T-Shaped Dev, which 30K+ engineers read.

My talk at DevTalks Romania 2026 grew out of the two books and made one argument. "AI did not kill software design. It made it more important."

  1. Fortune 500 engineer
  2. Startup CEO and CTO
  3. Two books
  4. The T-Shaped Dev

Spoke at GitNation, Geekle, React Day Berlin and DevTalks Romania

FAQ

Questions

For anything else, write to info@petarivanov.tech.

Who is this for?

React and Node.js engineers who already ship to production and want to make the architecture calls with confidence. Complete beginners will get more from the official React docs first, then this a few months later.

React or Node, where do I start?

Start with the stack you work in every day. The free playbooks cover both. Working across the client and the server? The JavaScript Architect Bundle has both books for $89.

Do I still need this if AI writes most of my code?

If you review that code, yes. Coding agents copy the patterns already in your codebase, so those patterns need to be worth copying. The books cover the decisions an agent won't make for you, and the Complete Packages include CLAUDE.md, AGENTS.md and .cursorrules files so your agents follow them too.

What will you send me after the playbooks?

New deep dives as I publish them, plus an email when there's a new book, course or sale. Unsubscribe in one click.

Can my company pay for it?

Yes. Stripe emails a receipt right after checkout, and I send an invoice with your company details when you reply to the purchase email. For a team, write to info@petarivanov.tech for team pricing.

What if it doesn't help?

Use it on your real codebase for 30 days. Still no change in how you write React or Node? Reply to your receipt for a full refund.

Free, 13 pages

Make your next architecture call with confidence

Get the two playbooks free, 13 pages in all. Try one decision tree on the code you're working on today.

Ready for the full set? Get both books in the Architect Bundle for $89