Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

Profilbild von Android Developers
Android Developersvor 25 Tagen

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

Profilbild von Muhammad Naveed
Muhammad Naveedvor 25 Tagen

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

Profilbild von Mobile Dev
Mobile Devvor 25 Tagen

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

Profilbild von Citrine Edge
Citrine Edgevor 21 Tagen

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.

Profilbild von satvik
satvikvor 25 Tagen

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

Profilbild von Android Developers
Android Developersvor 20 Tagen

Nothing is more permanent than a temporary workaround.

Ähnliche Videos

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,073 Aufrufe • vor 5 Monaten