Go event-ingestion + on-chain/off-chain reconciliation for a Solidity prediction market: append-only ledger, checkpointed backfill, idempotent writes
ethereumevent-sourcingfinancego
Go 2updated last week
Founding Engineer @ sprintworks
Hi, I'm Aidan.
I build the whole thing.
The screen you see, the API behind it, the infra underneath. Right now: building sprintworks from zero.
Pixel-art avatar
me, in 16×16 pixels
Open to interesting problems
- front end
- back end
- TypeScript
- Java & Go services
- APIs
- databases
- infra as code
- design systems
- CI/CD
- threat models
- the occasional 2am deploy
Three layers, one engineer
Product & interface
The part people touch. Fast, accessible, fun to use.
- React & Next.js
- Design systems & Storybook
- Accessibility & Web Vitals
APIs & data
Typed contracts and schemas that stay sane as things grow.
- TypeScript, Java & Go
- GraphQL & REST
- PostgreSQL & DynamoDB
Cloud & delivery
Ship it, then keep it boring. Alarms before users notice.
- AWS (2× certified)
- SST v3 & infra as code
- CI/CD & observability
Things I've shipped
Straight from my pinned GitHub repos, as current as my last push.
Interactive terminal AWS profile switcher: curses TUI over ~/.aws/config with region, SSO and account preview
awsclipythontui
Python 1updated 2 weeks ago
The one stop app to help students with learning difficulties
accessibilityhackathonnextjstypescript
TypeScript 1updated 2 weeks ago
The short version
I'm the founding engineer at sprintworks, which means I own features the whole way down: React at the top, TypeScript in the middle, AWS underneath. I like types that make bad states impossible and deploys boring enough for a Friday. And the security habit from my pentesting days never left: I threat-model in the design review, not after the incident.
Come say hisprintworks, from zero
First services, product architecture, delivery habits.
Type-safe data access
Drizzle helpers so schema and queries stop drifting.
A design system that survives contact
Storybook, visual review, a11y tests in CI.
Threat modelling upstream
STRIDE in the design review, before the PR.
Notes from the build
Things I learned the hard way, written down while the bruise was fresh.
2 min read
Hello from the new site
A short note on rebuilding dev-aidan.com from scratch, what changed, what didn't, and why I'm off AWS.
metanextjsvercel
2 min readinfo
Getting comfortable with Burp Suite
A practical first-week-with-Burp post, what to set up, what to ignore, and how I'm building a workflow.
securityburpweb
2 min read
Why I left AWS for a personal site
An honest, slightly sheepish accounting of paying for infrastructure I didn't need, and what I switched to.
awsvercelinfra