Technologies
Technology pages about what we build, and when we would not
These pages explain what we build with a technology, when it is a good fit, and when we would choose something else. They are not keyword pages with the logo swapped.
- What it is used for
- When it fits
- When it does not
- Who will operate it
How we pick
The deciding factors are the problem, the team that will own the system after us, the integrations, and how it has to be hosted. A stack your company cannot hire for is a future outage, even if it is elegant this quarter.
A stack for the people who will run it
We will say
- What the technology is for
- When it fits this product
- Who must be able to operate it
We will not do
- A rewrite for fashion
- A stack your team cannot staff
- A keyword page with no system behind it
How a technology is chosen
The estate
What you already run matters more than what is new.
The team
The people on call after handover have a vote.
The job
An API, a screen, and a document pipeline are allowed to use different tools.
What a stack conversation needs
- 01
The estate
What you already run and pay to operate.
- 02
The team
Who will be on call after handover.
- 03
The job
An API, a screen, or a document pipeline.
- 04
The constraint
A date, a skill, or a system you cannot leave.
Marks a technology was chosen for a job
- 01
The job came first
The stack follows the product, the team, and the systems already running.
- 02
Someone can operate it
The people who will own the release can read and ship it.
- 03
A second stack was refused
A tool was not added because it was fashionable.
- 04
The boundary is written
What this technology does here, and what it does not, is in the plan.
Technologies
Java
Spring Boot services for systems that must still be clear in five years.
.NET
ASP.NET systems for organisations that already run on Microsoft.
Python
Services and pipelines around data, documents, and models.
Node.js
TypeScript APIs for product teams that ship often.
Go
Focused services where concurrency and a simple deploy matter.
React
Product UIs and dashboards, with rules kept on the server.
Angular
Structured front ends for workflow-heavy business applications.
Vue.js
Approachable interfaces and incremental replacements of older front ends.
Flutter
Cross-platform mobile when the interaction can truly be shared.
React Native
Mobile apps for teams that already build in React.
AWS
Application hosting, pipelines, and a region choice you can explain.
Azure
Identity, hosting, and delivery for Microsoft-centred estates.
