I work as a developer at https://www.odoo.com https://www.odoo.com. Generally speaking, a professional software company has some kind of "style", "guideline" an

I work as a developer at https://www.odoo.com https://www.odoo.com. Generally speaking, a professional software company has some kind of "style", "guideline" and "culture" that guides developers. It's like building a house. Before you even start, you know you are going to need windows, walls, a roof... being a professional means having built so many houses that you know the order, the required components, how much time it should take and a hint of the cost. So if you have models like orders, bills, partners, contacts, you probably have a class for each and it's going to be mapped to the database tables somehow. Ýou will need to display the data and make it editable. You carefully plan and then you make space for refactoring, maybe use methodologies like Agile to decide priorities. Translate this into: authentication, authorization, data storage, algorithms, performance, user experience, import/export and ETL, documentation, tests, customer support, analytics. If you also are into product, add to that product design, marketing, hiring, supervision... If you are an expert, you may want to optimize, to make extensible components, to write a DSL, an API, to make collatersl services. "Clean architecture" is a classic go-to book. You can have a look at the QT framework docs which are very good. This is a good starting link also. https://queirozf.com/entries/how-to-structure-software-projects-python-example https://queirozf.com/entries/how-to-structure-software-proje...