Skip to content

Writing

Notes from the work

What broke, what it cost to find, and what we changed so it could not happen the same way twice.

31 documents · press / to search

  1. 6 min read

    Offline-first mobile: local SQLite, sync, and resolving conflicts honestly

    Designing for a connection that comes and goes — a local database as the source of truth, an outbox that survives a crash, and the conflict resolution strategies that do not quietly lose somebody's work.

    MobileOffline-firstSQLiteArchitecture

  2. 6 min read

    Writing npm packages people can depend on: exports, tree-shaking and release flow

    What separates a package that is safe to add from one that is a liability — an exports map that does not break anyone, tree-shaking you have measured rather than assumed, and a release process where the changelog cannot lie.

    npmTypeScriptOpen sourceTooling

  3. 5 min read

    Dark mode without the flash: theming across Next.js, React Native and mobile web

    The flash of the wrong theme is a timing problem, not a styling one. How to make the first paint correct on the server, keep it correct across platforms, and avoid the four traps that make a dark theme look broken.

    ThemingNext.jsReact NativeDesign systems

  4. 5 min read

    The TypeScript monorepo playbook: workspaces, project references and release flow

    When a monorepo earns its keep and when it is overhead, the two build-graph decisions that determine whether it stays fast, and the versioning choice that decides how painful releases are.

    TypeScriptMonorepoToolingDevOps

  5. 5 min read

    Event-driven backends in Node: outbox, idempotency and the failures worth designing for

    A queue does not make a system resilient by itself. The transactional outbox, idempotent consumers, ordering that is only guaranteed where you need it, and a dead letter queue somebody actually looks at.

    Node.jsBackendArchitectureMessaging

  6. 6 min read

    Moving a legacy application to AWS without downtime: a sequencing guide

    The order of operations that keeps a migration reversible at every step — what to move first, why the database goes last, and the cost lines that surprise teams after the cutover.

    AWSCloud migrationArchitectureDevOps

Start here

Tell us what you are building

Or what is breaking, or what has to go faster. You will get a straight answer from an engineer who would do the work.

Start a project