News for hackers. Stuff that matters.

A comment on The Perks of a High-Documentation, Low-Meeting Work Culture.

Re:The Perks of a High-Documentation, Low-Meeting Work Culture by bluetomcat on Tuesday November 22, 2022 @12:16PM (#33708173)
"High-documentation" isn't the cure, either. Just write quality software with well-defined interfaces, minimal dependencies and smooth building processes. I want to be able to build the thing without frustration, to start playing with it in order to learn its internals and debug it. Only then can I be comfortable enough to start implementing features and changes.
[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by giogadi on Tuesday November 22, 2022 @12:23PM (#33708284)
"Just write quality software"

That's quite a load-bearing "just" there.

[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by drewcoo on Tuesday November 22, 2022 @12:39PM (#33708475)
IMO, "quality" is going to be the sticking point.
[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by ip26 on Tuesday November 22, 2022 @02:33PM (#33710177)
No problem, we just need to hold a few meetings to define what counts as “quality”, and write it down in some good documentation.
[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by rqtwteye on Tuesday November 22, 2022 @01:24PM (#33709059)
It's devastating to learn after more than 20 years in the industry that the secret is "Just write quality software with well-defined interfaces, minimal dependencies and smooth building processes". If I and my colleagues had known only sooner about this straightforward and actionable advice...
[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by DenisM on Tuesday November 22, 2022 @01:28PM (#33709123)
That’s how I often use documentation - start documenting something, then ask myself “should the code be fixed to avoid the need to document this part? Yes, yes it should”.

A long provisioning instruction became much shorter as a result of automating it by reducing the need to document.

[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by ip26 on Tuesday November 22, 2022 @02:35PM (#33710204)
Are you pitching less documentation or none? It doesn’t seem like codebases are better when the architecture is unwritten.
[ Parent | on HN ]
Re:The Perks of a High-Documentation, Low-Meeting Work Culture by DenisM on Tuesday November 22, 2022 @03:49PM (#33711310)
As little as feasible, but no less than that.
[ Parent | on HN ]