Journal
Engineering notes from our team: the API conventions, architecture, automation, and operating patterns behind the systems we implement and set up, with the diagrams and code we use to explain them.
5 entries shown
- Operations8 min read
Alerts that turn a lost day into a five-minute fix
Most long outages are failures nobody knew about. How we design alerts, heartbeats, and runbooks so problems are found by the system, not by your staff the next morning.
- Node.js
- PostgreSQL
- TypeScript
- Python
- Jira
- Delivery7 min read
Implement what you have, or set it up from scratch?
The two ways we automate a system: implementing software you already run or have chosen, or a full setup. How we decide, and what each looks like week to week.
- Node.js
- Python
- Jira
- TypeScript
- PostgreSQL
- React Native
- Architecture8 min read
Hexagonal architecture: your workflow should not know it runs on Jira
Ports and adapters keep business rules apart from the tools around them, so a database, tracker, or app can change without rewriting the workflow.
- TypeScript
- Node.js
- Jira
- PostgreSQL
- Python
- React Native
- APIs9 min read
How we design REST APIs for workflow systems
Resources over actions, idempotent writes, one error shape, cursor pagination, and versioning that does not break the apps already in people's hands.
- Node.js
- TypeScript
- PostgreSQL
- React Native
- Automation7 min read
From a Jira transition to an automated workflow
Webhooks in, a durable queue, idempotent workers, retries with backoff, and an audit trail: the pattern behind most of the automation we ship.
- Jira
- Node.js
- PostgreSQL
- Python