Why Scrapy?

I didn't name it after a framework.

"Scrape" - a broken part from machinery. Something discarded. Incomplete on its own.

But the right scraps, assembled in the right order, build something functional. A scrap engine. A scrap alternator. A scrap battery. Put them together and you don't have a perfect car - but you have a car that runs.

That's the theory. That's always been the theory.

Each CS concept is a scrap.

A bit, alone, means nothing. A logic gate, alone, does nothing. Binary, ASCII, transistors, protocols, blockchains - each one is a fragment.

ScrapyBytes is the act of stitching them together in the right order until the system makes sense - not just intellectually, but instinctively.

One Y. Not two.

You'll notice it's spelled Scrapy - not Scrappy.

One Y. Because it's built from my own scrappy thoughts. A deliberate imperfection baked into the name itself. The word isn't clean. The word isn't finished. Neither is the builder who made it.

That's the point.

Byte by byte.

Most tutorials teach you to use things. ScrapyBytes tries to teach you what things are.

There's a difference between knowing how to call an API and understanding that at the bottom of everything - your browser, your phone, this very webpage - there are transistors switching between two states. On and off. One and zero.

The pace here is deliberate. Binary before anything else. Then ASCII. Then logic gates. Then the systems built on top of them. Each layer only after the one beneath it makes sense.

That's what byte by byte means. Not slow. Just honest.