Day 030: Bridges in No Man's Land
What happens when the compiler guesses wrong and the CPU doesn't know it.
C Journey
Learning C the hard way, through K&R, one day at a time, with a security eye on every chapter.
2026
Day 29: The Architect's Leap
K&R 4.1: what happens when the compiler builds a bridge without a blueprint.
Day 28: The Gravity of the Stack
Chapter 3 closes. The stack frame opens. Logic lives in a physical place, and that place has gravity.
Day 27: The Ghost in the Register
K&R 3.7 and 3.8. break, continue, and the one place K&R says goto is okay.
Day 026: The Negative Domain
I came back after 17 days off expecting to be rusty. The Feynman test said otherwise. Turns out the concepts stuck. What didn’t stick was the habit of showing …
Day 025: The Arithmetic of Trust
Section 3.3 and 3.4. Every formula I trusted had a hole in it.
Day 024: The Illusion of Structure
Chapter 3 opens. The code looks right. The compiler disagrees.
Day 023: The Postmortem
Chapter 2 closes. Not with new material but with a live audit that forced application of everything the chapter built.
Day 022 The High-Voltage Basement
Chapter 2 closes. The compiler caught my UB live. Six operators, two exercises, sixteen notebook entries.
Day 020: The C String Contract Is a Suicide Pact
K&R 2.8, the strcat design flaw, four new notebook entries, and the moment I realized safety in C is often just geographic coincidence.
Day 19: The Mask
Section 2.7, bitwise operators, and why the same 8 bits mean different things depending on who's reading them.
Day 18: Why 'A' Is Not A Character
Closed the overnight question on why character constants are int, worked through sections 2.3 through 2.5, and wrote exercise 2-2, the one where short-circuit evaluation turns out to be a security guarantee.
Day 17: The Break Day That Wasn't
Took a day off from K&R and spent it getting a dead 3D printing lab alive. Turns out debugging firmware and tracing undocumented wiring is just hacking with different stakes.
Day 016 The Type System Bites
Chapter 2 opens and the type system immediately starts lying to you.
Day 015 The Chapter 1 Test
Testing everything from Chapter 1. Feynman gauntlet, code tracing, security connections, and closing gaps I did not know I had.
Day 014 The Parser's Dilemma
Finishing Chapter 1 with the two hardest exercises. Comment stripping, bracket matching, and why parsers that don't understand context create entire vulnerability classes.
Day 013 Lucky Number
K&R exercises 1-20 through 1-22. Tab expansion, tab compression, line folding. A bug that hid in plain sight.
Day 012 Two Counters
Exercises 1-16 through 1-18. Dual counters, GDB investigations, and what happens when zero means two things.
Day 011: The Quiet Byte
K&R 1.8 and 1.9. Call by value, character arrays, and the single byte that holds all of C together.
Day 010: The Memory Next Door
K&R 1.6 and 1.7. Arrays, character arithmetic, functions. And the first time I watched a bug disappear into memory that wasn't mine.
Day 009: Shortcut Tax Repaid
Rebuilding ten exercises from scratch on a different machine. No peeking. No shortcuts. Proof of ownership.
Day 008: Consistency
There is a difference between having tools and having a workshop. I have four machines. A personal laptop. Two Linux boxes. A work computer. Until today each …
Day 007.5: The Exploit Lab
Day 007.5: The Exploit Lab Seven days of K&R on my primary workstation. Seven days of learning how C thinks. But learning C was never the point. The point is …
Day 007 Earning It Clean
Rebuilding exercise 1-10 from scratch, word counting with state machines, and threat modeling a 20-line program.
Day 006 The Shortcut Tax
Line counting, state tracking, and the cost of reaching for someone else's answer.
Day 005 The Program Listens
C stops printing and starts listening. getchar, putchar, and the precedence trap that has ruined code for fifty years.
Day 004 What They Didn't Know
K&R section 1.4. Symbolic constants. The preprocessor. And the realization that every layer was built by people who could not see what was coming.
Day 003 The For Statement
Day 003: The For Statement Today I opened K&R section 1.3 and met the for statement. Then I went back and knocked out three exercises from 1.2 that I had …
Day 002 the Type System
Day 002: The Type System Today I opened K&R section 1.2: Variables and Arithmetic Expressions. A Fahrenheit-to-Celsius conversion table. Fourteen lines of code. …
Day 001 the Foundation
Day 001: The Foundation I made a commitment today. One hour a day. Every day. No excuses. The goal is not to become a better tool user. I am already good at …
Starting Point
First post. What this is about.