ReactBook -  The React.js book I wish I had (and it’s free!)

ReactBook - The React.js book I wish I had (and it’s free!)

Hi everyone,

I remember when I started learning React, back in 2015/16, it was really really hard to understand most of the concepts because of the lack of proper documentation/tutorials. Yeah react docs were there but they were more of a "reference" than something someone new to React would need.

Now, we have immense quantity of tutorials, great react docs, AIs to help us with teaching, but I still think - it’s much easier to learn how to use React than to understand why React behaves the way it does. Yeah, not everyone might be interested in learning this but it's for people who want to learn more deeply about React.

For example, even having around a decade of experience with react, I still end up in situations wheere I have no idea why did this component render 2 times, or why did the useeffect run multiple times? Why did some state disappear? A lot of times I'd look for an answer and end up asking an AI to find those (nothing wrong with it though!)

And I really hated that gap between "yeah, I can build this in React" and actually understanding what React was doing under-the-hood?! That's pretty much why I thought about writing something like ReactBook.

It actually starts with the browser itself, and then slowly builds from there into rendering, component identity, state, effects, and eventually how all of this behaves in a production app. I didn't want random tips or another bunch of "just do this" rules.

Basically, I wanted to write the React explanation I wish I had when I was learning all this. I've completed the first volume, and all of it is free to read online.

And now with AI making it ridiculously easy to generate code, I feel understanding the code you're running has become even more important.

thereactjsbook.com Github

u/m_null_ — 4 days ago
▲ 7 r/TrueCarEnthusiasts+1 crossposts

I made an interactive site to help people get into cars from scratch

I've been into cars for years, and the thing that always annoyed me is how hard it is to learn this stuff as a beginner. Most of what's online is either a top 10 list or a forum thread where everyone already knows the lingo, and asking a basic question feels like a quick way to get roasted.

So I built Carcademy. It starts at the very beginning -

  • How an engine works, explained like a normal person would
  • What all the drivetrain, suspension, and transmission jargon means
  • Why two cars with nearly identical specs can feel totally different to drive
  • How to read a spec sheet and tell what's marketing from what matters

From there it gets into the deeper tech and the history. I wasn't trying to make people memorize a pile of facts. I wanted it to click why cars ended up the way they did. The rough idea is - start with zero knowledge, end up being the friend people text before they buy a car (heh, don't blame me if they don't).

There's no signup or paywall. I made it mostly because I wanted something like this when I was starting out and couldn't find it.

I'd really appreciate feedback from people who know this way better than me - tell me what I missed or got wrong.

thecarcademy.com
u/m_null_ — 2 months ago
▲ 68 r/node

[NodeBook] Volume 2 has been released!

Hi all,

Nodebook's Volume 2 is now available to read online.

There have been a couple of changes to the curriculum. I've pushed the chapters on worker threads and child processes down to Volume 3, and moved the networking chapters - Networking Fundamentals, TLS, HTTPS & HTTP/2, and Realtime Streaming - up into Vol 2.

I've always wanted to keep this book targeted at intermediate-level Node/JS devs, but I added a networking fundamentals chapter because I feel many devs who work with Node don't really understand the underlying networking stuff.

As always, feedback is welcome.

thenodebook.com
u/m_null_ — 2 months ago
▲ 83 r/node

NodeBook Volume I is done now!

Hi r/node,

I've (finally) finished Volume I of NodeBook - 46 chapters. This took way more time than I thought it would.

For those who haven't read it yet - it covers the lower-level Node stuff, and everything you'd need to know to become a better backend dev (or even build libraries using node). If you're using other runtimes, like Bun/Deno, you'll still learn a lot about backend development. Give it a go.

It's not for beginners. You should at-least know Javascript and somewhat comfortable with node ecosystem.

There are tons of beginner level tutorials for Node out there, many good, many bad, but they're there. If you are new, you can still read it, but it assumes you have written some Node before. My recommendation is to go through some beginner level Node tutorial, build a couple of dummy scripts, and you'll be good to go.

The chapters are public here: https://www.thenodebook.com

The book will forever stay free online. I have some plans for a digital edition, probably by the end of next month.

GitHub repo: https://github.com/ishtms/nodebook

thenodebook.com
u/m_null_ — 3 months ago