For the past couple of years, I've been more or less participating in project handovers where my team and I receive software delivered in an actual project — now ready for the maintenance phase.

Such handovers are not one without complexity. Sometimes there is only so much documentation to get the application barely running. Automated tests might be missing altogether. No one has thought of adding a style guide.

All in all, the developer experience could be significantly improved.

Therefore, I've recorded a set of techniques and practices that have worked for me while restoring the technical excellence to a product in its post-development phase.


In this initial version of my software lifecycle guide, I focus on automated tests and documentation. I reserve the liberty to update this guide later.

You can do it too by sending me a pull request via GitHub.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!