News for hackers. Stuff that matters.
Re:The art of interrupting software engineers by twic on Tuesday July 30, 2019 @06:17AM (#20563469)
Having followed the process as described, i'd agree. If a project runs for more than a few months, you forget why decisions were made. I don't think XP in general has a great story about how to deal with this.
Re:The art of interrupting software engineers by technion on Tuesday July 30, 2019 @08:55AM (#20564348)
I'd be less worried about "forgetting" and forever worried about a manager just saying "you obviously forgot (something I just decided)". I mean it happens even when there's documentation I can pull up and say "well actually..", I'd hate to imagine otherwise.
Re:The art of interrupting software engineers by JustSomeNobody on Tuesday July 30, 2019 @09:11AM (#20564466)
I love email for this. That way I can always pull up the email and say, "this is what we decided." I follow up all meetings with email(s).
Re:The art of interrupting software engineers by jacques_chester on Tuesday July 30, 2019 @05:02PM (#20569132)
Yes, this is one of my pet peeves.

Pivotal R&D has struggled with maintaining context. For multi-megaSLOC codebases with many moving parts, organic memory begins to fall a bit short.

Different teams deal with this differently. Some write design notes, some keep architecture design records. But IMO it's one of our weaknesses.