Patterns and antipatterns in Odoo module development

There are a number of patterns commonly found in Odoo module development. Old-time developers know them, even if they do not consciously apply them as patterns. There are also many anti-patterns that can lead to inefficient and even, sometimes, insecure code.

These are also known by old-time Odoo developers and normally only discussed in the dim-lit backrooms of a few Belgian bars close to the Odoo Experience conference center, among a handful of grizzled developers.


This year no more, and youngsters will get a chance to access this precious knowledge.

Key learnings:
After attending this talk, you will learn how to structure business models to avoid performance and security issues, ease extensibility, and avoid being flagged as a noob by code reviewers.

Target audience:
Odoo module developers with some experience in the framework, but beginners are welcome too. Prior knowledge of module development is expected.

Added value for the target audience:
- Write better-structured models.
- Gain some insights about things you may be doing wrong.
- Make your code easier to extend.
- Earn respect from your colleagues who were not lucky enough to attend the conference.

[divad]

I strongly disagree with the first 3 points: module naming, dependencies and number of line of code (juste check Odoo account module, and 15K lines of code is definitely a very small project for any project outside of a Odoo module). Some modules does not have any precise role except fitting the client's need which evolve and grow over time. Trying to find a split logic in it is a guaranty to face dependency hell or circular dependency at some point for some clients.

Otherwise, yes, no documentation, no README, long monolithic function etc is indeed bad. I just disagree with the role of a module (which is like the first slide)