Part 3: Good and bad practices at APEX! Release to production and beyond
This is a series of few articles covering good and bad practices at each stage of the application lifecycle
Part 1: analysis
Part 2: development
Part 3: release to production and beyond
Many developers forget or rather do not remember that the application is not only about analysis or a pleasant development process, but also about maintaining the application that is already in production! Here are some tips to keep in mind during this time:
Clean up after yourself!
If you haven’t yet run your application through an “Advisor”, now is the time! This is a valuable step that will highlight important aspects you may have missed during development and provide insights for improvement.
And more cleaning...
How many times have we changed a component or dynamic action to never, hoping that one day we will come back to it?
If we don't use these components during development, there's little chance they'll be useful in production.
Now comments … :
How often have we added unclear comments to SQL queries, leaving code that won't be used anywhere? While comments are important, it’s essential to write them in a way that will be useful to others in the future. Make sure your comments add value and clarity.
Again documentation …
If you started creating documentation during the development process, now is the time to complete it. At this point, the database schema is finalized and the application is working as it should, with the appropriate access granted to the appropriate users. Completing the documentation at this stage will help future developers understand the structure, functionality, and access levels of the application. This is a necessary step to ensure that anyone working on the application in the future has a clear and organized reference to build on, improving maintenance and ongoing development.
New features
It is important not to stop at the first version of the app. After the release, users will provide feedback, new ideas for functionality will emerge, and there may be opportunities for improvement or simplification. Be open to these suggestions and, in collaboration with the client, continue to develop the app. This continuous improvement will ensure that the app evolves to meet user needs, and users will appreciate the continuous improvements.
This stage is very individual and depends on the client. Some want a finished product that they will work with for years to come in the first version, others want to release a skateboard that will then become a car and finally a rocket. It is important that we as developers take care of our work at every stage.
Conclusion of part 3
Remember that none of the applications or programs you use are finished with version 1.0 !