Here’s a conceptual framework to help keep your no-code and low-code effort simple, but comprehensive. By Joe Procopio.
The main points captured in the blog post:
- Yes, you need to document code you didn’t write
- Create a single, central document
- Document before you act
- Be verbose but direct
- Document not just what you did, but why
- Be judicious about what makes a release
- Don’t rely on the platform’s versioning
Some platforms allow you to create save points and restore to previous versions like I mentioned above, but most don’t do it well, and some don’t do it at all. Make your own backup copies of text, scripts you’ve modified, settings you’ve changed, anything that would require a lot of rethinking to to re-do. Good read!
[Read More]