8 ms·
I prefer "habitability" over either term. "This place is a mess, we're constantly tripping over things, how about we make it a more habitable codebase to work i
by tedyoung 4y ago
I prefer "habitability" over either term. "This place is a mess, we're constantly tripping over things, how about we make it a more habitable codebase to work in?"
No matter what you call it, though, if teams aren't empowered/encouraged to make the code more habitable, it won't happen. You could call it "partying" instead of "removing tech debt" and folks still won't do it if the system around them discourages it ("must work on next feature now!").
- anbvsn 4y ago
- jlongr 4y agoThat's a great one. Habitability implies that we are preventing avoidable dangers. It's also gives a connotation of positive-feeling ownership, i.e. a home, as opposed to ownership of something 'bad' like debt. I would tack on 'hospitality.' It isn't just a great place for us to stay, but an inviting and comfortable place for guests, visitors, and others unfamiliar with the layout of the property. My team recently started working on another department's codebase. It is quite habitable to the current owners but inhospitable to me and my co-workers. It's hard to learn their conventions, no matter how consistent and logical they may be.
- tacostakohashi 4y agoI've also heard this referred to as "quality of life" for developers.
- muzani 4y ago"partying" sounds like the kind of term scrum people use