Skip to main content
11 events
when toggle format what by license comment
Jun 16, 2020 at 10:01 history edited CommunityBot
Commonmark migration
Sep 5, 2014 at 0:05 audit First posts
Sep 5, 2014 at 0:06
Sep 3, 2014 at 23:24 vote accept Philipp Claßen
Sep 3, 2014 at 23:23 comment added Robert Harvey Yep, that's how you get them done: by requiring them.
Sep 3, 2014 at 23:22 comment added Philipp Claßen Thank you. "... we do our best to create these artifacts. They are, in fact, required elements of the overall software product". I think that is a crucial aspect. It has to be a natural part of the development. Otherwise, you will feel the pain when you working on unfamiliar code bases, but the ones that work on them regularly do not feel this pain. Often they do not see the need to document the "obvious" things.
Sep 3, 2014 at 23:21 history edited Robert Harvey CC BY-SA 3.0
added 12 characters in body
Sep 3, 2014 at 23:20 comment added Robert Harvey @Telastyn: I could probably write a few pages about that, under the banner of "sensible architecture." That said, I added a little clarification to my answer.
Sep 3, 2014 at 23:17 comment added Telastyn One missing point that I've found to be key is consistency. I don't need to know how a part of the system works if I can trust that it is implemented in a sane manner, consistent with what I expect. The problem isn't that people don't know the details of a system, it's that they guess (very) wrong about its details. This separation of sub teams with communication between also helps communicate culture and standards across the group.
Sep 3, 2014 at 23:06 history edited Robert Harvey CC BY-SA 3.0
added 2 characters in body
Sep 3, 2014 at 23:00 history edited Robert Harvey CC BY-SA 3.0
deleted 62 characters in body
Sep 3, 2014 at 22:52 history answered Robert Harvey CC BY-SA 3.0