| This is an incredibly broad question and touches on many aspects of software engineering, devops and operations. For operations, I would recommend having the team read the google SRE book https://sre.google/workbook/table-of-contents/ it has everything one would need to setup a modern operations infrastructure and associated best practices.
https://sre.google/workbook/table-of-contents/ Sounds like you are unhappy with the quality of code and error handling. Seems like it was written by junior devs? I would recommend having the team read the usually recommended books if they haven't. At the bare minimun: * Refactoring by Fowler * Clean Code by Robert Martin If you are using an OO language: * Practical Object-Oriented Design in Ruby The book has "in Ruby" in the title but it's a general purpose book on what make OO design "good" Then follow it up with * Patterns of Enterprise Architecture * Clean Architecture These books are not perfect or the be all end all, there are parts of them that might be slightly dated but they get you to a large chunk of the way to the promised land. Lastly, if the application is working, the users are happy, there is no bug infestation and you are not having issues with releasing new features, don't feel the pressure to immediately "fix" the code. |