what's your approach to bus factor when the person who owns the code can't explain it either
A developer is facing a bus factor problem with a 3,000-line billing sync code. Although they are officially the owner, they didn't write most of it and can only explain what it does, not why. The original agent who wrote the code eight months ago is no longer available to explain it. This situation highlights a common challenge in development: managing code where the knowledge isn't hoarded but was never fully documented or understood by anyone involved.
Time & source
- Published
- 09/09, 14:36 UTC+0
- Ingested
- 09/09, 17:00 UTC+0
- Source type
- Dev community
- Tier
- Community
- Source status
- Healthy
Tier is a per-source editorial setting, not a per-item score.
asking because I own a billing sync I didn't really write, an agent did most of it eight months ago, some 3k lines, and I basically just reviewed it and approved it. not by design, it kind of ended up that way. on paper I'm the one who knows it, in practice I can tell you what it does and not why. coderabbit flagged plenty going in and none of that helps me now. curious how people handle the bus factor problem when it isn't hoarded knowledge, nobody had it in the first place