[kingkongjaffa]

A happy solution is to write more tests, and more 'newbie to the codebase tests' and cookbooks to understand what the code is meant to do or how to use the API layer.

This becomes a test of the use case and can help catch regressions and highlight progressions.

Remembering to write documentation seems hard to get engineers to do.

Whereas having a test pass is still within their wheelhouse of 'I love to code' and can also help with demo'ing new releases as well, since if one of the release requirements is a demo/test case/cookbook entry then you're building in a self documentation requirement.