Skip to content

Replies within one business day.

Engineering Notes & Insights

Architecture decisions, performance audits, and operational workflows from delivered systems. Written to be genuinely useful to technical teams.

4 Notes Published4 TopicsProduction Proven
Featured · Performance7 min read·2026-08-12

Why your Next.js catalogue is still slow on mobile

A 90-plus Lighthouse score on your laptop with a fast connection tells you almost nothing. Here is where catalogue performance actually goes, and the four things that usually fix it.

By Ressan engineeringRead note
Architecture6 min read

Brand as data, not deployment

How to launch a second or fourth brokerage brand without standing up a second back office — and why the decision must be made in the schema, not the front-end.

Ressan engineering ·
Product engineering6 min read

The schema decision that costs you eighteen months later

Most product rewrites are not caused by bad code. They are caused by a data model that could not express a feature the business needed later. Here are the four that recur.

Ressan engineering ·
AI & data7 min read

Automating document work without introducing confident errors

The failure mode of AI document processing is not a crash. It is a plausible wrong number delivered with total confidence. Here is the architecture that prevents it.

Ressan engineering ·
Why we write:

If an engineering decision cannot be explained simply in writing, it was a preference rather than an architecture decision.

Start a project brief