Technology, AI & ERP — explained in plain English
Odoo 20, unveiled 24 September 2026, brings AI agents that create and update records, a bank consistency rule in accounting, offline mode, and the end of the Field Service app. This app-by-app tour covers what changed, what was removed, and what it costs.
Beneath every git commit lies a content-addressable object database of blobs, trees, and commits linked into a directed acyclic graph. This walkthrough unpacks the four object types, SHA hashing, the .git layout, refs, packfiles, and the plumbing commands that expose it all.
A developer-level walkthrough of the TLS handshake — asymmetric vs. symmetric crypto roles, the certificate chain of trust, cipher suite anatomy, the message-by-message TLS 1.2 flow, the one-round-trip TLS 1.3 redesign, forward secrecy, session resumption, and how to inspect it yourself with openssl s_client and browser devtools.
Beneath the familiar exposure triangle lie three very different processes: aperture controls how much light a lens gathers, shutter speed controls how long the sensor counts photons, and ISO amplifies the signal after the fact. Rebuilt from first principles: the stop as a unit of energy, the f-number as a ratio, reciprocity — and where it breaks.
The camera histogram is a measurement, not a judgment: how to read its axes, why clipping is asymmetric, the JPEG pipeline trap, luminance vs RGB graphs, and why exposing to the right works — with a field workflow that takes seconds.
Every digital photograph begins as a storm of photons striking silicon. This article follows the full chain — photoelectric conversion, full-well capacity, the Bayer filter and demosaicing, CCD vs CMOS, ADC bit depth, and what a RAW file actually holds versus a JPEG.
Terraform, Ansible, and Pulumi are not three flavors of one thing — they are three answers to how you tell a machine what your infrastructure should look like. This article breaks down how each tool actually works, where the trade-offs really bite, and gives a scenario-based decision framework so you can pick on evidence instead of hype.
From ir.actions.report to wkhtmltopdf: this article walks Odoo’s full report pipeline — report actions, QWeb templates, paper formats, and a layered debugging workflow for when PDFs render wrong. Grounded in the official Odoo 17 documentation, with code examples for each stage.
WordPress stays as the editorial backend while Next.js renders the frontend — this guide covers the WPGraphQL API layer, static rendering and ISR caching strategies, draft previews, and the production traps that catch headless projects.
Odoo is a monolith made of plug-ins — every app, including Settings, is a module. This guide builds a complete minimal Library Management module for Odoo 17: directory layout, __manifest__.py key by key, security CSV, views, actions, menus, and the load-order rule that trips up every first module.
Odoo security is two mechanisms in a strict order: access rights grant model-level CRUD to groups, record rules narrow access to rows with domains. This guide walks through the evaluation algorithm, a worked fleet example, and the mistakes that break real deployments.
Liveness, readiness, and startup probes each trigger a different Kubernetes reaction — restart, traffic removal, or a startup grace period — and confusing them is one of the most common sources of avoidable production incidents. This article explains what each probe checks, exactly what the kubelet does on each failure, and the misconfigurations that cause the most damage.
Multi-stage builds separate compilation from the final runtime image, letting you ship only what the application actually needs to run. This article walks through the mechanics, realistic Node.js and Go examples, layer-caching pitfalls, and minimal base images — with a security-first checklist.
The Terraform state file is the JSON map between your configuration and real-world infrastructure — and the thing most likely to ruin a team week when shared carelessly. This article covers remote backends (including S3 native locking via use_lockfile), lock-conflict recovery, why workspaces aren’t environment isolation, and the HCP Terraform managed option.
Strapi and headless WordPress both decouple content from presentation, but they optimize for different teams: Strapi for JavaScript-native builders who iterate on structured content models, headless WordPress for editorial teams that already live in the WordPress workflow. This article compares content modeling, developer experience, and true cost of ownership — including Strapi’s restructured 2026 Cloud pricing.
WordPress caching is not one thing but five layers — browser, CDN, page, object, and opcode cache — each short-circuiting a different stage of the request. This article walks through every layer in request order, with production configuration, measurement advice, and the pitfalls that catch even experienced site owners.