5 ms·
What about the low doc, low meeting culture
by oxff 4y ago
What about the low doc, low meeting culture
- willcipriano 4y agoI'd like a read the code culture. For me documentation is harder to read than code and so inaccurate that you end up reading both anyway.
- twobitshifter 4y agoWhat is an example of that working? Just code that speaks for itself? How would you ever know why something was done?
- DenisM 4y agoTurn around and ask. For small teams it might work well. Larger teams require more overhead, hence why hiring more people does not produce linear productivity growth.
- mobjack 4y agoYou ask someone in slack. If that isn't sufficient, set up a small 1 on 1 meeting to discuss. You can't avoid all meetings, but you can keep them few and small.
- Macha 4y agoNow my ability to find something is limited by someone else's availability, and everywhere I've seen this culture it's devolved into the same 1-2 people answering all the questions as not everyone has a built up map of who knows what.
- twobitshifter 4y agoIn long running projects, the people who know the answer may no longer be around.
- koonsolo 4y agoAfter you are the 3rd person who contacted me for the same thing, the next one better read the fking documentation that I write.
- mostlylurks 4y agoContrary to popular belief, it is almost always possible to express the 'why' (not just the 'what') via code, even if comments and/or external documentation are sometimes cleaner, simpler alternatives.
- hannasm 4y agoI have had good experiences using commit messages for documenting the reasoning behind code changes.
- aliswe 4y agoit's a good start but it doesn't scale