SoenkeSchwenk,
@SoenkeSchwenk@mastodon.online avatar

Everyone wants software architecture documentation until they realize it means constant updates and carefully crafted content and diagrams.

kerfuffle,
@kerfuffle@mastodon.online avatar

@SoenkeSchwenk

It's a matter of making the required discipline part of your team's routine and, through that, culture. It's not much different than including tests.

Code review, planning, daily standup, DoD check, review: check impact on documentation, and plan the effort.

underlap, (edited )
@underlap@fosstodon.org avatar

@SoenkeSchwenk I think there's some value in keeping old architecture or design docs without necessarily keeping them up to date. The original rationale is valuable information and doesn't tend to go out of date. They just need to be treated as historical documents.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • rosin
  • thenastyranch
  • tacticalgear
  • ethstaker
  • InstantRegret
  • DreamBathrooms
  • ngwrru68w68
  • magazineikmin
  • Youngstown
  • mdbf
  • khanakhh
  • slotface
  • GTA5RPClips
  • kavyap
  • JUstTest
  • everett
  • cisconetworking
  • Durango
  • modclub
  • osvaldo12
  • tester
  • Leos
  • cubers
  • normalnudes
  • megavids
  • anitta
  • provamag3
  • lostlight
  • All magazines