About

Page / 02

An engineering practice,
measured by what it hands back.

SEC AUDIOLOGY LIMITED is an independent technology company working with organisations that need software, cloud and data systems built or repaired by a small, senior team.

Overhead editorial photograph of a small technical team working together with laptops and printed diagrams

§ 01

Introduction

Who we are.

We are a compact technology practice. Our engineers, designers and operators have spent their careers inside product companies, public institutions and infrastructure teams; the practice exists so that the same discipline can be brought to organisations that do not have it in-house or that need it strengthened for a specific piece of work.

The company operates under the name SEC AUDIOLOGY LIMITED and does business in English. Correspondence is handled by email, and engagements are entered into by written agreement.

§ 02

Mission

What we are for.

Our mission is to make technology work in a way that a client organisation can continue to operate without us. That means the systems we build are readable, the environments they run in are understood, and the people who inherit them are equipped to maintain them.

We measure our own work not by how much of it we did, but by how little intervention it required six months later.

§ 03

Vision

Where we are trying to get to.

We would like to see fewer, better systems in the world — systems that solve specific problems for identifiable people, that respect the time of the users who rely on them, and that do not accumulate more complexity than they earn.

The practice is deliberately small. We grow when a good engineer decides to join, not when a pipeline forecast recommends it.

§ 04

Operating principles

Principles that guide our work.

  • — Do the smallest thing that solves the problem, and leave a note explaining why.
  • — Say what you are going to do, do it, and say what you did.
  • — Treat other people's code with the respect you would want for your own.
  • — Prefer written decisions over remembered ones.
  • — Refuse work you cannot do well, and say so plainly.

§ 05

Technology philosophy

How we think about tools.

A tool is a liability as much as an asset. Every framework, service and dependency in a system has to be operated, upgraded and eventually replaced. We choose tools accordingly: with a bias for maturity, for large user bases, and for the availability of people who can maintain them.

We are not opposed to new technology; we are opposed to adopting it without a specific reason. When we do introduce something new, we write down why.

§ 06

Client collaboration

How we work with clients.

Our default is direct contact between the people writing the code and the people whose problem is being solved. We do not insert an account layer, and we do not use engagement staffing to protect senior engineers from client conversations.

Communication is scheduled and asynchronous where it can be, and synchronous where it needs to be. Decisions are recorded in the same place the work is done.

Warm-toned macro photograph of a printed circuit board with copper traces

§ 07

Quality standards

The standard we hold work to.

Code that goes into production is reviewed by another engineer, covered by tests appropriate to its risk, and instrumented so that its behaviour in production can be observed. Documentation for the system is written before the system is considered delivered.

When a defect is found, the fix is accompanied by a test that would have caught it, and by a short written account of what happened.

§ 08

Security & responsibility

Security is part of the job, not a separate one.

Every engineer in the practice is responsible for the security of the code and infrastructure they touch. Threat modelling, access review and dependency posture are part of the engineering workflow rather than a separate audit performed afterwards.

Client data is treated as belonging to the client. Access is minimised, logged and revoked on completion of the engagement.

§ 09

Team culture

The way we work with each other.

Engineers in the practice work with a high degree of autonomy and a low tolerance for meetings. We write in complete sentences, disagree in writing, and record what we decided. New members are paired with a colleague on their first engagement.

We treat rest as part of professional practice. Tired engineers make worse decisions, and the practice is not built to require them.

§ 10

Long-term perspective

A long view of the business.

SEC AUDIOLOGY LIMITED is structured for continuity rather than growth targets. We prefer repeat clients over a wide funnel, and long-lived engagements over short bursts of activity. Where a client's needs are better served by a different provider, we say so.

§ 11

Contact

How to reach us.

Enquiries about the practice are handled by email. Please describe the shape of the problem, the constraints, and the timeframe you are working within.