Discover and read the best of Twitter Threads about #NOFL
Most recents (1)
One like — one non-trivial tip about making quality engineering documentation. Go.
1. Value-producing systems are set up to benefit from explicit feedback loops.
[e.g. peer review, CI/CD, QA are parts of feedback loops for making quality software.]
Documentation is a process teams frequently overlook to organize feedback loops for.
[e.g. peer review, CI/CD, QA are parts of feedback loops for making quality software.]
Documentation is a process teams frequently overlook to organize feedback loops for.
2. As a ton of code doesn’t mean quality, experts call for a very light _amount_ of documentation. Otherwise the information overload and ongoing maintenance bring the costs up and usefulness down. “Just enough”, they say.
Andreas Rüping provides a scientific diagram:
Andreas Rüping provides a scientific diagram:
