Ovalleaf
The Ovalleaf Weekly

What our engineers
learned this week

A weekly note from the Ovalleaf engineering team — what we built, what broke, and what we learned about AI engineering, DevSecOps and cloud-native delivery.

Get it in your inbox every week

One email a week. No spam, unsubscribe any time. See our Privacy Policy.

Latest Issue

The Technical Debt Payoff Calculation—When to Refactor and When to Move On

Issue 012 · 22 August 2026 · 5 min read

Issue 012

The Technical Debt Payoff Calculation—When to Refactor and When to Move On

Just pay down the technical debt - easy to say. Knowing whether to spend 3 weeks refactoring or 3 days building the next feature is the hard part.

engineeringarchitecturedecision-making
5 min read

Archive

Previous issues

Every issue we have published, newest first.

engineering6architecture3infrastructure3frontend2ai1cloud1data1decision-making1design-systems1machine-learning1mlops1operations1tailwind1tooling1
Issue 011

Designing Data Pipelines That Won't Break at 2 AM

Real-time ETL pipelines sound great until you are debugging why 500k records disappeared. We share the principles that make data pipelines reliable, observable, and survivable.

engineeringdatainfrastructure
3 min read
Issue 010

MLOps for the Impatient—Getting Models to Production Without Losing Your Mind

ML workflows are chaos. We share the minimal MLOps stack that actually works—experiment tracking, automated retraining, model versioning, and monitoring in 48 lines of Python.

engineeringmlopsmachine-learning
2 min read
Issue 009

Multi-Cloud Architecture—Patterns, Pitfalls, and When to Go All-In

The multi-cloud dream sounds great until you are debugging a network issue that spans three continents. We share patterns from enterprises running production systems across AWS, Azure, and GCP.

engineeringcloudinfrastructure
5 min read
Issue 008

Building Agentic AI Systems at Scale

From proof-of-concept to production—how to architect multi-agent AI systems that reason, integrate with enterprise APIs, and deliver explainable results.

engineeringaiarchitecture
3 min read
Issue 001

The Tailwind class that silently does nothing

A hover state on one of our tables had never rendered — not because it was wrong, but because Tailwind quietly refused to generate it. Here is how the whole class of bug works, and the check we now run.

frontendtailwindtooling
3 min read
Issue 002

What a design system is actually for

A design system is not a colour palette. It is a set of decisions you agree to stop re-making. Notes from consolidating one across twenty pages.

design-systemsfrontendengineering
4 min read

What our engineers learned this week

One email a week from the engineers doing the work — what we built, what broke, and what we would do differently.

One email a week. No spam, unsubscribe any time. See our Privacy Policy.