W.
BETWEEN 0 AND 1 · ––:––

Dawood W.Harrington Barry

Every system begins in the same place: nothing is happening. Then one decision changes the state.

This is a story about that instant — the distance between an empty screen and something alive. Keep scrolling.

Type a word. Here’s what the machine actually reads.

6 characters · 48 bits — no letters, no words: just current flowing, or not.

First, there is zero: not failure, but room. No signal. No answer. No shape yet. Then comes one: a choice made visible. A pulse. A branch. A beginning. Code is the craft of crossing that distance turning intention into a system that can answer back.

The first line never builds the whole world. It only proves that the world can begin.

  • Nothing.
  • A decision.
  • A living system.
Ready to change the state?

Type a word. Here’s what the machine actually reads.

6 characters · 48 bits — no letters, no words: just current flowing, or not.

01
DESKTOP
1440 <
991 >
767 >
478 <

The First Signal

At first, the screen is empty. Then one instruction survives the compiler. A pixel changes. The system answers. The idea has crossed into the world.

— DAWOOD W. HARRINGTON BARRY

Between the Lines

What Makes It Hold

Node.jsReactPostgreSQLWindows ServerAWSPowerShellLinuxTCP/IPAzureDockerTypeScriptRESTMySQLMFAAgileExpressFlutterMongoDBActive DirectoryIAMGPOBashDNSEC2KubernetesPythonGraphQLSQL ServerSSOScrumJavaScriptNext.jsFirebaseIntuneGitHyper-VNginxDHCPS3CI/CDC#JSONPrismaZero TrustJiraJavaHTMLRedisVMwareGitHubMicrosoft 365ApacheVPNLambdaGitHub ActionsPHPPostmanMongooseEncryptionVS CodeSpring BootCSSModelingNetwork ConfigExchangeSSHFirewallVPCTerraformSQLWebSocketETLBackupFigmaAPIsTailwindServer ManagementWSUSVLANCloudWatchAnsibleBusiness LogicRoutingJenkinsSecuritySwitchingSystem Architecture

What the Machine Hides

Why do computers only speak in 0s and 1s? Because a circuit can do just one thing: let the current through, or not. Everything else — your photos, your music, this text — is only a stack of that yes/no, repeated billions of times a second.
Binary
The Foundations
Why does turning it off and on again fix almost everything? Because a program piles up state in memory: leaks, forgotten locks, corrupted values. Restarting throws it all out and starts from a known page. You don’t fix the bug — you erase its consequences.
The Reboot
The True Myth
What is “the cloud,” really? Someone else’s computer. Your files don’t float anywhere: they sit on very real disks, in an air-conditioned warehouse, that you rent by the second. The cloud just means you’re spared the address.
The Cloud
The Vocabulary
RAM or hard drive, what’s the difference? RAM is your desk: blazing fast, but wiped every evening. The disk is the drawer: slow, but it keeps. Shutting down clears the desk — hence the eternal “remember to save.”
RAM & Storage
The Hardware
What is an algorithm? A recipe. A finite sequence of unambiguous steps that, from ingredients, produces a result. Nothing magical: sorting your feed and nailing an omelette follow the exact same idea.
The Algorithm
The Vocabulary
Why is my computer slow? Nine times out of ten, it’s not short on power: it’s waiting. Too many programs share the memory, and when it overflows it spills onto the disk, a thousand times slower. It’s not speed that’s missing, it’s room.
Slowness
The Real Answer
Zero held the possibility.
One made it real.
D.W.H.B.
Everything after is iteration.