Standard Odoo first
If the framework already does it, the module does not. Every line I skip is a line that cannot break on upgrade.
Uses
The kitbehind it
What an Odoo day actually runs on — versions, database, editor and the tools in between.
13 tools
Odoo4
- Odoo 16 – 20
- Every version I build and upgrade against.
- Odoo.sh
- Staging and production deploys.
- OWL
- Client actions, widgets and dashboards.
- QWeb
- Reports and templating.
Backend3
- Python
- Business logic and the ORM layer.
- PostgreSQL
- Schema work and query tuning.
- XML-RPC / REST
- Integrations with outside systems.
Editor & shell3
- VS Code
- Primary editor, Python and JS extensions.
- Git
- Feature branches, reviewable commits.
- pgAdmin
- When a query needs looking at properly.
Day to day3
- Odoo debug mode
- First stop for anything unexpected.
- Postman
- Poking API endpoints before wiring them up.
- WhatsApp / LinkedIn
- Where clients actually reach me.
Choosing
A short stack is a feature, not a shortcut.
Boring where it counts
Python, PostgreSQL and Git are the whole backend story. Novelty belongs in the problem, not the stack.
Whatever the client already runs
Odoo.sh, a VPS or on-premise — I work in the environment you have rather than moving you to mine.
See it applied
Browse the workThe same stack, on fifteen modules published to the Odoo Apps store.