Skip to content
||RSS

Uses

The hardware and software I actually open every day, and why.
Reviewed 06 09 2026|No affiliate links

Desk

  • MacBook Pro 16″ M3 Max
    36GB. The RAM matters more than the cores when you keep four Chrome profiles and a Docker stack open.
  • LG UltraFine 27″
    Single display, not two. Fewer places for a Slack notification to hide.
  • Keychron K3 — brown switches
    Low profile, quiet enough for a call I forgot to mute.
  • iPhone 15 Pro
    The on-device test unit. A simulator will lie to you about haptics, camera, and real network conditions.
  • Pixel 8
    Kept next to the iPhone for the same reason — Android is where React Native's cross-platform promise actually gets tested.

Editor

  • VS Code
    Vitesse Light, JetBrains Mono at 14px, line height 1.7. Format on save, no exceptions.
  • Biome
    Replaced ESLint and Prettier on new projects. The speed difference is not subtle.
  • Ghostty + Fish
    Starship prompt, trimmed to branch and node version only.
  • Xcode + Android Studio
    Open for the simulators and native build tooling, not for writing code in either.
  • Expo CLI / EAS
    The actual dev loop for the React Native work — prebuild, dev client, and OTA updates without a store release.

Measuring

  • Chrome DevTools
    Performance and Coverage panels. Almost everything I've written about performance started in one of the two.
  • WebPageTest
    Throttled mobile, Cape Town test location. Lab numbers from a fast desktop are a story, not data.
  • CrUX + Vercel Analytics
    Field data settles arguments that lab data starts.
  • React Native DevTools
    Replaced Flipper in the stack. Component tree, network, and the profiler in one place, without a separate app running.

Shipping

  • This site
    Next.js, self-hosted fonts, deployed on Vercel. No client-side framework on article pages.
  • Storybook
    With visual regression. The subject of one of the more useful things I've written.
  • EAS Build + Submit
    Cloud builds for both platforms from one config, then straight to store submission without touching Xcode or Android Studio's own release flow.
  • TestFlight + Play Console
    Where a build actually lands in front of a client before it reaches the store.