Journal
Field notes from production Odoo — the problem, the root cause, the fix.
We read our own attendance engine twice, and the second pass corrected six things
Nine things a business believed about its overtime, allowance and payroll rules — checked line by line against the code, then checked again.
Read the noteThe payroll bug that wasn't arithmetic
Half a day, a handful of people, every month — and four parts of the system with four opinions.
Read the noteA recovery secret in the database protects nothing from a database administrator
Why our security features keep their off switch in the server config file.
Read the noteLet the model fill the form, never the database
The one constraint that made an AI intake pipeline safe to ship.
Read the noteVAT carry-forward is a chain, so we made the system refuse to guess
Filing periods, reversals, and why a gap warning beats a silent credit.
Read the noteDon't fail on record 3 of 200
Flight hours, block hours, and batch operations that explain themselves.
Read the noteA no-code dashboard builder that can't leak data
Letting people build their own dashboards without bypassing access rules.
Read the noteOne punch, three records
Making biometric attendance trustworthy — and the WhatsApp flood that taught us about stale events.
Read the note