News for hackers. Stuff that matters.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by twobitshifter on Tuesday November 22, 2022 @01:05PM (#33708768)
What is an example of that working? Just code that speaks for itself? How would you ever know why something was done?
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by DenisM on Tuesday November 22, 2022 @01:31PM (#33709163)
Turn 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.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by mobjack on Tuesday November 22, 2022 @01:42PM (#33709346)
You 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.

Re:The Perks of a High-Documentation, Low-Meeting Work Culture by Macha on Tuesday November 22, 2022 @02:11PM (#33709823)
Now 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.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by twobitshifter on Tuesday November 22, 2022 @01:45PM (#33709377)
In long running projects, the people who know the answer may no longer be around.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by koonsolo on Tuesday November 22, 2022 @03:40PM (#33711186)
After you are the 3rd person who contacted me for the same thing, the next one better read the fking documentation that I write.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by mostlylurks on Tuesday November 22, 2022 @04:58PM (#33712128)
Contrary 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.
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by hannasm on Wednesday November 23, 2022 @01:31AM (#33715913)
I have had good experiences using commit messages for documenting the reasoning behind code changes.