Skip to content
Arun Arivanandam

Three books · One route · #codetrailseries

You are not bad at this. You were given the wrong picture.

Most programming confusion is a modelling problem wearing a syntax costume. Three books that correct the models, so the documentation becomes readable and the features stop feeling arbitrary.

Get all three $49 Read a chapter free
  • Instant download
  • PDF, EPUB and Kindle
  • Free updates for life
  • Full refund if it does not land

The route: jump to any book

Series elevation profile Pitch 01 – 03

The premise

Nobody lied to you. The model just had a boundary nobody mentioned.

A mental model is the picture in your head of how something works. You carry thousands without noticing. Most are simplified. Many are slightly wrong. They work perfectly until the day they do not.

Programming depends on models you were never explicitly handed. Each of these books corrects one that almost everybody arrives holding.

  • A webpage is a picture you assemble.

    It is a document a browser reads and then builds, on a screen you have never seen, at a text size you did not choose.

  • A variable is a box that stores a value.

    A name refers rather than contains. The box story collapses the day two names point at the same object.

  • The screen is a thing you change.

    You describe what it should be given what is true, and something else works out the difference.

Why the order matters

Three books. One question each. They stack.

Each question only becomes answerable once the previous one is. That is why React feels like a set of rules when the ground beneath it is shaky, and like an obvious consequence when it is not.

  1. 01 What is this?

    Every element makes a claim. Every box owns a piece of space. Naming what something is, before deciding how it looks, is the habit the whole trail rests on.

  2. 02 What is true right now?

    What this name refers to at this moment. What has already happened and what has merely been scheduled. Most impossible bugs are a disagreement between what was true when you wrote a line and what is true when it runs.

  3. 03 Who owns this?

    Who owns this information, who decides when it changes, who needs to know and who only needs to be told. Most architectural regret traces back to a moment when nobody could answer it.

CODE TRAIL SERIES PITCH 01 / 03 HTML & CSS Establishing the Basecamp

Available now

HTML & CSS

Establishing the Basecamp

Nothing ever fails outright. You write a page and it appears. And yet you spend an hour moving a box eight pixels to the left, and when it finally looks right you could not explain what fixed it.

So you conclude, privately, that CSS is just like that. That conclusion is the most expensive one in web development, because it teaches you to stop asking why. CSS is not arbitrary. If the result surprises you, something is happening that you are not looking at.

After this book you can

  • Predict what a layout will do before you reload the page
  • Know which box moved, and which rule moved it, without guessing
  • Read an unfamiliar stylesheet without opening thirty dev-tools panels

Twelve chapters · 42,000 words

  1. The Web Is a Document System
  2. Structure Before Style
  3. Content Comes Before Markup
  4. Navigation Is a Concept
  5. Forms Are Conversations
  6. Semantic HTML Is About Intent
  7. How Layout Really Works
  8. The Box Model as Boundaries
  9. Selectors as Relationships
  10. Units, Size, and Context
  11. Responsive Thinking
  12. Reading and Debugging CSS

$24 Buy HTML & CSS Or get all three for $49

CODE TRAIL SERIES PITCH 02 / 03 JAVASCRIPT The Core Ascent

In progress

JavaScript

The Core Ascent

You finish a course. Every line makes sense as it appears on screen. Then you open an empty file to build something of your own, and nothing comes. Not because you forgot the syntax, but because you have no idea what the first line should even be about.

In your first week somebody said a variable is a box that stores a value. It is a helpful picture, and it is the source of confusion that surfaces three years later when the box story quietly collapses.

After this book you can

  • Start from an empty file without freezing
  • Tell the difference between what has happened and what has merely been scheduled
  • Debug async code by reasoning about it, not by adding logs until something shifts

The route

  1. Values as snapshots
  2. Names as labels
  3. State as a condition in time
  4. Decisions as forks
  5. Loops as contracts
  6. Functions as boundaries
  7. Structures that hold information
  8. Events from outside
  9. Effects on a world you do not control
  10. Time, and why JavaScript will not wait
  11. Reading somebody else's code
  12. Working out why it broke

$29 Tell me when it lands Included in the $49 bundle

CODE TRAIL SERIES PITCH 03 / 03 REACT Forging the Ridge Line

In progress

React

Forging the Ridge Line

You can write components. You can ship a feature that works. And yet you hesitate before touching code you wrote last month, and when someone asks why the screen behaves a certain way the honest answer is a shrug dressed up as an explanation.

You believe the screen is a thing you change. React inverts that, and until the inversion lands, hooks feel like rules to obey rather than consequences to expect.

After this book you can

  • Decide where a piece of state belongs, and defend the decision
  • Expect what a re-render will do instead of being surprised by it
  • Open an unfamiliar component and find the answer in minutes

The route

  1. The problem React exists for
  2. Describing instead of changing
  3. Components as boundaries
  4. Props as a one way street
  5. State, and where it should live
  6. Rendering as a consequence
  7. Effects and the outside world
  8. Identity, keys and lists
  9. Memoisation and what it costs
  10. Reading an unfamiliar component
  11. Debugging what you cannot see
  12. Who owns this

$29 Tell me when it lands Included in the $49 bundle

The complete trail

All three books. One continuous route.

Most developers learn this material as three unrelated subjects taught by three unrelated people, then spend years wondering why the pieces never quite lock together. These three were written as one argument.

  • All three books, in PDF, EPUB and Kindle formats
  • Book 1 downloads the moment you buy
  • Books 2 and 3 arrive the day each one ships, at no extra cost
  • Every future revision, free, forever
Get the bundle $49 Read a chapter first
Bundle price compared with buying each book separately
HTML & CSS: Establishing the Basecamp $24
JavaScript: The Core Ascent $29
React: Forging the Ridge Line $29
Bought separately $82
Bundle price save $33 $49

This is the pre-release price. It goes up when Book 3 ships — buying now locks in the lower one.

If a book does not change how you see the material, email me and I refund it. No form, no questions, no need to explain yourself.

Who wrote this

Arun Arivanandam

Seven years on the MERN stack, mostly on the unglamorous half: sync engines, background jobs, database migrations that run at 3am without waking anyone. I care about systems that fail quietly and recover on their own, and about frontends that stay usable on a bad connection.

These books are the explanations I ended up giving the same way often enough that writing them down became the obvious move. You can read the rest of what I write, and check my work, without paying for anything.

Read the blog See what I build

Fit

Worth being honest about who this helps.

Read these if

  • You can build things, but cannot always explain why they worked
  • You debug by changing values until the symptom goes away
  • You have finished tutorials and still freeze in front of an empty file
  • You joined a team and their codebase feels opaque despite every line being familiar
  • You are self taught and suspect there are foundations you skipped
  • You want to stop relearning the same lesson in each new framework

Skip these if

  • You want a syntax reference. The documentation is better and more current
  • You want a step by step build of one particular app
  • You want the newest features catalogued as they ship
  • You have never written a line of code. Start with any good beginner course, then come back
  • You are happy with how you work and are not looking to rethink it

Free chapter

Read the box model chapter before you buy anything.

Chapter 8 in full, the one that reduces every spacing problem to a single question. If it changes how you look at a layout, the rest will too.

Browsers do not see cards, heroes or sidebars. They see rectangles, and every layout is resolved by answering questions about those rectangles.

So when a layout looks wrong, the useful question is not why is my card broken. It is which box moved, why did it move, and which rule moved it.

Chapter 8 · The Box Model as Boundaries

Readers

What it changed for people who read it.

This platform completely transformed our development workflow. We went from deployment bottlenecks to seamless daily releases within a single week.

Sarah Jenkins — Director of Engineering at CloudScale

The intuitive interface and powerful automation tools saved our design team over twenty hours of manual formatting every month. Essential software.

Marcus Vance — Lead Product Designer

I was skeptical at first, but the data analytics dashboard provided insights that helped us increase our conversion rates by nearly forty percent.

Elena Rostova — VP of Growth at ApexMedia

Proof

This page is the sample chapter.

A book about semantic markup and layout should be able to survive its own sales page being inspected. So inspect it. View source and read what is actually there.

Then turn the stylesheet off and read it again. It still makes sense from top to bottom, in the right order, because the structure was decided before any of the appearance was.

Semantic landmarks and one clean heading outline
yes
Readable top to bottom with the stylesheet disabled
yes
Keyboard reachable, focus always visible
yes
Honours reduced motion and your dark mode setting
yes
Scales with your own font size, not just the window width
yes
Analytics, trackers and cookie banners
none
JavaScript required to read the page
none

Questions

Before you decide.

Books 2 and 3 are not finished. What am I buying?

Book 1 is complete and downloads immediately. Books 2 and 3 are being written. Buy the bundle now and you get Book 1 today plus the other two the day each one ships, at a price that will rise once all three are out.

I already know HTML and CSS. Is Book 1 too basic?

It is not a beginner book. It assumes you can already build a page and asks why the page behaves as it does. If you have never been quite sure why a margin collapsed, or why one rule beat another, there is something here for you. If you can explain both without hesitating, start with Book 2.

Why not just read the documentation? It is free.

You should read it. These books exist to make it readable. Documentation answers what a thing does, and assumes you already know why it exists and when you would reach for it. That assumption is exactly where most people get stuck.

Will this be out of date in two years?

The specific properties will keep moving. The models will not. Understanding that a selector is a test rather than a search, or that a value is a snapshot rather than a living thing, does not expire when a framework does. That is the whole reason the books are written this way.

What formats, and can I read on a Kindle?

PDF, EPUB and a Kindle friendly file, all included with every purchase. No account, no expiry, no streaming platform. Download them and they are yours.

What if it does not land?

Ask for a refund and you get one, no questions and no need to explain yourself. If a book does not change how you see the material, it has not earned your money.

Not fewer surprises. A better next move.

You will spend the rest of your career being surprised by systems, and anybody who tells you otherwise is selling something. What changes is what happens next. Where a surprise once produced a sinking feeling and a round of random edits, it starts producing a question, and then a better one.

Get all three $49 Read a chapter free

$49 All three · save $33

Get the bundle