Skip to content

Notes

Notes on building software

Written by the engineers doing the work. Decisions we made and why, things that went wrong, and the technology we actually run clients' systems on — with the trade-offs, not the press release.

View

What we think, and what we would do about it.

How we do it

Something we do regularly, written down.

Briefing

A summary of an external announcement, with the source linked.

View2 min read

Why we don't publish a price list

A price list filters out the exact buyer with a £1,000 fix. Here is what we do instead, and why we publish a floor rather than a range.

  • commercials
  • scoping
Team Quorix DigitalWeb development
  • How we do it3 min read

    An AI assistant that does not invent

    We built a chatbot for our own site. The hard part was not the model — it was making it refuse to answer rather than invent one.

    • ai
    • engineering
    • trust
    Team Quorix DigitalAI & automation
  • View3 min read

    How to show your work when your NDA says no

    Most of our work is under NDA. What we publish instead, why we will not use stand-in imagery, and how to tell a led build from a contribution.

    • trust
    • commercials
    • writing
    Team Quorix DigitalBug fixes
  • How we do it3 min read

    The cheapest hour is the audit

    Most rebuilds fail because nobody checked what already existed. What two days of technical audit finds, and why it belongs before the proposal.

    • scoping
    • engineering
    • cloud
    Team Quorix DigitalCloud
  • View3 min read

    The studio that fixes other people's code

    Most of our smallest engagements are someone else's codebase and a deadline they did not choose. Here is what we do in the first day, and what we will not do.

    • engineering
    • cost
    • scoping
    Team Quorix DigitalBug fixes
  • View2 min read

    An API you cannot version is a dead end

    The decision about how you change an API is made once, early, and never revisited. Getting it wrong costs a rewrite. Here is the version I default to.

    • api
    • architecture
    Team Quorix DigitalAPIs & integrations
  • View3 min read

    Your inventory number is a guess

    Stock accuracy is not an analytics problem. It is a race between one number and several systems, and the fix is usually structural rather than clever.

    • ecommerce
    • architecture
    • cost
    Team Quorix DigitalE-commerce
  • View3 min read

    Offline-first is not an optimisation

    If your field app says 'connection lost' to someone standing in a warehouse, the design is wrong. Treating offline as the normal case changes everything.

    • mobile
    • architecture
    Team Quorix DigitalMobile apps
  • How we do it3 min read

    A security review before launch, not after

    Penetration testing on a system that has not shipped is a checklist. On a live one it is an incident report. Here is what we review and why the order matters.

    • security
    • engineering
    Team Quorix DigitalCybersecurity
  • View3 min read

    Cloud cost is a design decision

    Nobody overspends on cloud by accident. It happens in the architecture, months before anyone opens a billing dashboard. Here is where it goes.

    • cloud
    • cost
    • architecture
    Team Quorix DigitalCloud

Not sure where to start?

Ask before you book

The assistant on this site answers questions about our services, process and the markets we work in, in English and Arabic. It is a faster way to find out whether we are relevant to you than reading four articles, and it costs you nothing to try.

How we write

  • Every post names a decision we actually made, or a mistake we made, rather than summarising someone else's marketing.
  • Where we summarise an external announcement we link the original and say so, so you can check it.
  • We do not publish client names, screenshots or metrics we cannot substantiate.
  • If a post turns out to be wrong we correct it and say what changed.
Book a call now