Lab notebook
I keep learning in public
Outside client work I keep a public notebook of hands-on builds. Many start from NextWork's guided project library, and every write-up covers what I built, the choices I made and what broke along the way. It is how I stay sharp on services I do not touch every week.
Featured builds
Two that grew into full repositories
The notebook
41 write-ups, 9 topics
Pick a topic to narrow it down. Every card opens the full write-up on GitHub.
- ServerlessWebsite delivery with CloudFrontRead the write-up
- ServerlessAPIs with Lambda and API GatewayRead the write-up
- ServerlessFetching data with AWS LambdaRead the write-up
- ServerlessBuilding a three-tier web appRead the write-up
- DevOps & IaCA web app on EC2 with VS CodeRead the write-up
- DevOps & IaCConnecting GitHub to AWSRead the write-up
- DevOps & IaCSecuring packages with CodeArtifactRead the write-up
- DevOps & IaCContinuous integration with CodeBuildRead the write-up
- DevOps & IaCDeploying with CodeDeployRead the write-up
Writing
Notes from the build
A four-part series on Dev.to that walks through the serverless app from the notebook, including the parts that went wrong. Part four is mostly about a CORS bug, because the mistakes are usually where the useful lessons are.
- Part 1Read on Dev.to
How I delivered a static website globally with S3 and CloudFront, and the security mistake I almost made
- Part 2Read on Dev.to
Building a serverless REST API with Lambda and API Gateway
- Part 3Read on Dev.to
Least-privilege IAM for Lambda: why I replaced the AWS managed policy with my own
- Part 4Read on Dev.to
Wiring together a three-tier serverless app, and the CORS bug that broke everything
Next step
A role to fill, or a platform to fix?
Either way, a short email is the best place to start. Tell me what you are working on and I will reply with honest first thoughts.