Start a conversation.

Two kinds of message always get a reply. Principal and staff-plus roles, where the architecture and the people around it are the same job. And hard platform problems — real-time systems that disagree with themselves, rendering pipelines, compliance models that have outgrown the spreadsheet holding them together.

Short is fine. One paragraph and a link tells me more than a brief.

01Direct line
corey@spiritdevs.com

A personal inbox, read by one person — no form queue in front of it. The composer below the horizon writes into this same address.

Codegithub.com/coreybain
Based inSydney, Australia
02

Compose

Transport · convex

Message composer

Direct · stored
AttachmentsUp to 3 files · 4 MB combined

Submitting stores the message and nothing else — no queue in front of it, no autoresponder, no list to be added to.

Directory

Static
Email
corey@spiritdevs.com
GitHub
coreybain
Based
Sydney, Australia
Role
Principal Engineer, Web and Mobile Platform Architecture · Corporate Interactive

Correspondent

Snapshot
Contrib · 12 mo
10,043
Agent sessions
2,165
Platforms
5

The same three numbers the homepage opens with, read from the same snapshot. Measured, not claimed.

03Before you write

Three messages that always get an answer.

No template required — this is only what makes a reply fast.

01

A role

The team, the systems it owns, and what principal means where you are. A band and a location expectation in the first message saves us both a round.

02

A hard problem

Real-time correctness, rendering pipelines, risk modelled as a graph — the shape of the 5 platforms already carrying load. Advisory, review, or hands on the code.

03

An engineering question

Agent-assisted delivery, or anything on this site. 2,165 sessions in, the opinions come with receipts.

Ground I can cover
  • Web and mobile platform architecture
  • Shared contracts and server-owned business rules
  • Monorepos and incremental legacy migration
  • Sync engines, multi-user and real-time editing
  • Cloud migrations to AWS and Azure
  • ADRs, standards and shared tooling
  • Payments and partner integrations
  • Real-time systems over WebSockets and Ably
  • TypeScript, React, Next.js, Swift and Convex
  • Native iOS and Android with offline sync
  • Document editors and web/PDF rendering
  • Tenant-aware permissions and secure sharing
  • Agent-assisted engineering workflows
  • Technical leadership, code review and mentoring