Small footprint.
Static files and usage-based services keep the baseline lean. No always-on web server required.
HELLO, INTERNET
Curious by
default.
I’m a developer, tinkerer, and problem solver. This is my little corner of the internet—and a place to share the things I’m figuring out.
ALWAYS LEARNING. USUALLY BUILDING SOMETHING.SCROLL TO EXPLORE
01 / A LITTLE ABOUT ME
Complexity is
inevitable.
Complication
is optional.
I like understanding how things work—and finding a better way when they don’t.
I’m a software developer and consultant with years of experience in IT and development. I enjoy the big, complicated problems as much as the small, satisfying fixes.
I tend to favor simple, practical solutions, and open-source tools whenever they make sense. This site is a place for the work, ideas, and whatever else I decide to share along the way.
Things I’m into02 / UNDER THE HOOD
This website is
the example.
I wanted a little website, not another server to babysit. So I built around static files, a global cache, and just enough cloud infrastructure.
HOW THIS SITE WORKS DESIGNED TO DO MORE WITH LESS
VisitorsAnywhere
Route 53DNS routing
CloudFrontGlobal edge cache
Private S3Static content
LambdaOptional dynamic features
The static site uses Route 53, CloudFront, and private S3. Lambda is a possible addition; dynamic features aren’t connected yet.
Room to grow.
Edge caching is designed to serve traffic close to visitors and handle substantial demand. Real limits depend on configuration and workload.
Easy to evolve.
Simple files are straightforward to edit. Add serverless functionality only when there’s a reason.
Minimal overhead, remarkable reach. This architecture keeps costs low at rest and scales efficiently with demand—so the site can grow without paying for idle servers.
A THOUGHT ON CONTENT MANAGEMENT
Do I really need a CMS?
WordPress and other content management systems are useful, especially for teams, workflows, and frequently updated content. But for a small site like this, a database, plugins, updates, and an always-running application can feel like a lot to maintain.
With today’s capable AI assistants, editing plain HTML and CSS can be surprisingly approachable: describe a change, review the result, and publish the files. AI can make mistakes, so changes still need human review and testing—but for simple content, it’s a compelling alternative to carrying a whole CMS.
03 / THINGS I’M INTO
A few things
I enjoy.
Software development
Purposeful applications and integrations built around what people actually need.
Cloud & infrastructure
Practical, scalable foundations that make the most of modern cloud services.
Technical consulting
Clear thinking, honest recommendations, and a fresh perspective on complex challenges.
Open-source minded
Using proven, open tools where they fit—because good ideas are better when shared.
04 / WHAT’S NEXT?
Say
hello.
Have a question, an idea, or something interesting to share? I’d love to hear about it.