What I build with

Agents write most of my code now, under review, and one of them answers questions on this site. The skill is still the old one: deciding what they're allowed to touch, and checking what comes back before it ships.

• Claudelive: /ask
• Amazon Bedrocklive: /ask
• Claude Codelive: /fleet
• Model Context Protocol
• Tool uselive: /ask
• Prompt cachinglive: /ask

Every site and system on this page is deployed and run by me, end to end — including the one you are reading. Since October it also runs a Claude agent on Bedrock, a live visitor map on Lambda and DynamoDB, and the whole dynamic half of the site as one CloudFormation template. What each service does, and how.

• CloudFrontruns this site
• S3runs this site
• Route 53runs this site
• Lambdalive: /ask
• Amazon Bedrocklive: /ask
• DynamoDBlive: /live
• CloudFormationthe template
• IAM and OACruns this site
• EventBridgelive: the bill
• Cost Explorerlive: the bill
• CloudWatch
• API Gatewaylive: /fleet
• Amazon Pollylive: /ask
• EC2
• SESlive: /mail
• Bedrock Guardrailslive: /security
• Amazon Textractlive: /receipt
• CloudFront multi-tenant (SaaS)live: /white-label
• Certificate Managerlive: /white-label
• WorkMail
• CodeDeploy
• ccAWS CodeCommit

Card payments are the part of a build where "mostly working" is not a state. Both of these keep the card data off my servers and hand back a token, which is the only sane way to do it. How the payment and API work fits together.

• Stripe
• Square

What the operator actually touches. The same component discipline whether it ends up in a browser or on a phone.

• React
• Next.js
• TypeScript
• JavaScript
• Tailwind
• Vite
• HTML
• CSS
• jQuery
• elElectron
• pwPlaywright
• vtVitest
• rfReact Flow
• dgDagre

Field work happens where the signal does not. Native where it earns its keep, installable web where a store listing would only be friction.

• React Native
• Cordova
• Progressive web appslive: /card
• exExpo
• pnExpo push notifications
• flfastlane

The part that has to still be right at 2am.

• Nodelive: /ask
• Express
• PHP
• CodeIgniter
• PPhpStorm
• ioSocket.IO
• jwtJSON Web Tokens
• 2faTOTP two-factor sign-in
• pdfmPDF
• ocrTesseract.js

Money reconciles or it does not. These are the two I trust with a ledger.

• PostgreSQL
• MySQL
• JSON
• XXML
• sqSQLite
• n4jNeo4jlive demo
• auNeo4j AuraDBlive demo
• rdRedis

Most of my day happens in a terminal. Servers, deploys, databases, DNS, the AWS accounts, app builds and the AI agents are all driven from the command line and scripted, so every deploy is one command and nothing depends on remembering which buttons to click.

• $zsh and bash
• >_SSH
• ggit
• awsAWS CLI
• rsrsync
• myMySQL CLI
• ghGitHub CLI
• ccClaude Code
• sdsystemd
• cbCertbot
• npmnpm
• xcXcode CLI and simctl
• easExpo EAS CLI
• crcron
• GHGitHub

Boring on purpose. A deploy should be forgettable.

• Docker
• nginx
• Apache
• Ubuntu
• Let's Encrypt

The physical side: homemade 3D printers, Raspberry Pi robots programmed in Python, and trackers on expensive machinery that report power-on, run hours and location over cellular. How it plugs into AWS.

• piRaspberry Pi
• pyPython
• iotAWS IoT Core
• mqMQTT
• 3d3D printing
• lteCellular modems (LTE-M / NB-IoT)
• gpsGPS tracking
• locAmazon Location Service

Most systems earn their keep at the seams, where they meet the phone system, the inbox, the CRM the business already runs, or the carriers that ship its parts and equipment.

• Twilio
• Anthropic API
• SSuiteCRM
• WordPress
• CCanada Post
• UUPS
• FFedEx
• PPurolator
• pmPHPMailer
• ntntfy

The visual side, done in-house: brand and print, photo, video and sound, and the 3D and real-time engines.

• CcAdobe Creative Cloud Pro
• PsPhotoshop
• AiIllustrator
• InDesign
• AeAfter Effects
• PrPremiere Pro
• FcFinal Cut Pro
• LrLightroom
• GGarageBand
• MMaya
• UUnreal Engine
• UUnity

Nineteen years of this ran on Flash. The tools went away; the reasons they were chosen did not.

• AActionScript
• FFlash
• FFlex
• Corona
• Corel Draw