Video wird geladen...
Video konnte nicht geladen werden
Load-bearing code vs drywall code 🤔👷♀️ Fast experimentation uses what we call drywall code while load bearing code is part of the system. What do you think of this concept? Learn more in the latest episode of Android Developers Backstage Podcast →
10,314 Aufrufe • vor 25 Tagen •via X (Twitter)
6 Kommentare

Which type of development work do you prefer? 🔨 Drywall code: Fast experimentation you don't even need to read; just run it 🏋️ Load-bearing code: A key part of the system, something foundational that you’ll maintain and nurture for years

Interesting way to think about code. Experimentation needs flexibility, but knowing when to turn temporary code into reliable infrastructure is what really matters.

Drywall code is where agents shine. Load bearing still needs a human who will own it for years.

Persistence and recovery are a useful dividing line. An experiment becomes load-bearing pretty quickly once a user expects it to survive a process restart without losing state or repeating an action.

drywall code needs an expiry date. otherwise someone connects billing to it and suddenly it's load-bearing 😭

Nothing is more permanent than a temporary workaround.

