Hamilton Greene
@sirhamy.bsky.social
Technomancer building Simple Scalable Systems. hamy.xyz
I scored 15 programming languages across 5 dimensions.
- C# and Kotlin tied at 4.5/5
- Rust hit 4.0
- S-tier (5.0) remains empty
- C# and Kotlin tied at 4.5/5
- Rust hit 4.0
- S-tier (5.0) remains empty
February 4, 2026 at 9:45 AM
I scored 15 programming languages across 5 dimensions.
- C# and Kotlin tied at 4.5/5
- Rust hit 4.0
- S-tier (5.0) remains empty
- C# and Kotlin tied at 4.5/5
- Rust hit 4.0
- S-tier (5.0) remains empty
In 2026.01, I started parental leave, started my Recurse Center batch, began learning Rust, released my first Rust crate, read 6 (short) books, built a web game, improved my vibe engineering workflows, and generally tried to figure out how to be a stay-at-home-dad.
hamy.xyz/blog/2026-01...
hamy.xyz/blog/2026-01...
2026.01 Release Notes
Essay - Published: 2026.02.03 | 5 min read (1,438 words)reflect | reflections
hamy.xyz
February 3, 2026 at 6:41 PM
In 2026.01, I started parental leave, started my Recurse Center batch, began learning Rust, released my first Rust crate, read 6 (short) books, built a web game, improved my vibe engineering workflows, and generally tried to figure out how to be a stay-at-home-dad.
hamy.xyz/blog/2026-01...
hamy.xyz/blog/2026-01...
When should you choose exceptions over errors as values?
Exceptions are great for cases where you can't / won't recover - like no access to your primary DB.
Errors as Values are better for basically every other case. Explicit > Implicit.
hamy.xyz/blog/2025-07...
Exceptions are great for cases where you can't / won't recover - like no access to your primary DB.
Errors as Values are better for basically every other case. Explicit > Implicit.
hamy.xyz/blog/2025-07...
5 Reasons to Stop Throwing Exceptions - and What To Do Instead for a more Robust, Composable, and Performant Codebase
Date: 2025-07-02 | create | errors | exceptions | programming | software | software-engineering | tech |
hamy.xyz
February 2, 2026 at 6:08 PM
When should you choose exceptions over errors as values?
Exceptions are great for cases where you can't / won't recover - like no access to your primary DB.
Errors as Values are better for basically every other case. Explicit > Implicit.
hamy.xyz/blog/2025-07...
Exceptions are great for cases where you can't / won't recover - like no access to your primary DB.
Errors as Values are better for basically every other case. Explicit > Implicit.
hamy.xyz/blog/2025-07...
LightClone - Compile-Time Safety for Cheap Clones in Rust
- Mark structs with LightClone
- Compile errors if don't implement LightClone
- Only implemented on types w copy or known-cheap clones
- Call .light_clone at callsite
hamy.xyz/blog/2026-02...
- Mark structs with LightClone
- Compile errors if don't implement LightClone
- Only implemented on types w copy or known-cheap clones
- Call .light_clone at callsite
hamy.xyz/blog/2026-02...
February 2, 2026 at 9:45 AM
LightClone - Compile-Time Safety for Cheap Clones in Rust
- Mark structs with LightClone
- Compile errors if don't implement LightClone
- Only implemented on types w copy or known-cheap clones
- Call .light_clone at callsite
hamy.xyz/blog/2026-02...
- Mark structs with LightClone
- Compile errors if don't implement LightClone
- Only implemented on types w copy or known-cheap clones
- Call .light_clone at callsite
hamy.xyz/blog/2026-02...
January 28, 2026 at 7:00 AM
Reasons I'm moving from F# to C#:
* Less context switching - C# is c-like
* C# has gotten good - records, linq, and unions
* Good tooling + ecosystem
* AI is great at C#
* The syntax is verbose but readable
hamy.xyz/blog/2025-11...
* Less context switching - C# is c-like
* C# has gotten good - records, linq, and unions
* Good tooling + ecosystem
* AI is great at C#
* The syntax is verbose but readable
hamy.xyz/blog/2025-11...
Why I'm Moving my Blog from F# to C#
Essay - Published: 2025.11.26 | csharp | fsharp | hamy.xyz | iamhamy |
hamy.xyz
January 27, 2026 at 3:45 AM
Reasons I'm moving from F# to C#:
* Less context switching - C# is c-like
* C# has gotten good - records, linq, and unions
* Good tooling + ecosystem
* AI is great at C#
* The syntax is verbose but readable
hamy.xyz/blog/2025-11...
* Less context switching - C# is c-like
* C# has gotten good - records, linq, and unions
* Good tooling + ecosystem
* AI is great at C#
* The syntax is verbose but readable
hamy.xyz/blog/2025-11...
Weirdest game I've played in awhile: Talk to me Human - talktomehuman.com
Get out of tricky social situations by talking to your computer.
Get out of tricky social situations by talking to your computer.
Talk to Me Human
The talking your way out of it simulator
talktomehuman.com
January 25, 2026 at 6:41 PM
Weirdest game I've played in awhile: Talk to me Human - talktomehuman.com
Get out of tricky social situations by talking to your computer.
Get out of tricky social situations by talking to your computer.
I made a little game about burning AI tokens - hamylabs.itch.io/ai-token-cli...
Built with: TypeScript, Phaser 3
Built with: TypeScript, Phaser 3
AI Token Clicker by HAMY LABS
Scale your AI usage by burning ever more compute in this incremental clicker.
hamylabs.itch.io
January 24, 2026 at 6:41 PM
I made a little game about burning AI tokens - hamylabs.itch.io/ai-token-cli...
Built with: TypeScript, Phaser 3
Built with: TypeScript, Phaser 3
AI makes you faster but it doesn't replace engineering judgment.
Use the speedup to write better code, not just more code.
1 more review / refactor / test / verification.
Use the speedup to write better code, not just more code.
1 more review / refactor / test / verification.
January 23, 2026 at 6:41 PM
AI makes you faster but it doesn't replace engineering judgment.
Use the speedup to write better code, not just more code.
1 more review / refactor / test / verification.
Use the speedup to write better code, not just more code.
1 more review / refactor / test / verification.
I tried quitting social media entirely but it didn't stick.
Instead I manage my scrolling time with:
* Access blockers
* Time blocks
* Daily Todolists
* Read later bookmarks
How I Stopped Mindless Doom Scrolling - hamy.xyz/blog/2025-07...
Instead I manage my scrolling time with:
* Access blockers
* Time blocks
* Daily Todolists
* Read later bookmarks
How I Stopped Mindless Doom Scrolling - hamy.xyz/blog/2025-07...
How I Stopped Mindless Doom Scrolling As A Chronically Online Software Engineer - Less Time Scrolling, More Time Doing Things I Enjoy
Date: 2025-07-23 | happiness | health | productivity | reflect | software-engineering |
hamy.xyz
January 23, 2026 at 6:05 PM
I tried quitting social media entirely but it didn't stick.
Instead I manage my scrolling time with:
* Access blockers
* Time blocks
* Daily Todolists
* Read later bookmarks
How I Stopped Mindless Doom Scrolling - hamy.xyz/blog/2025-07...
Instead I manage my scrolling time with:
* Access blockers
* Time blocks
* Daily Todolists
* Read later bookmarks
How I Stopped Mindless Doom Scrolling - hamy.xyz/blog/2025-07...
I use AI regularly to help code features. It's still not great at building large features but it's getting good at well-scoped tasks where examples exist.
- Don't outsource the plan
- Do outsource well-scoped tasks w examples
- Checkpoint regularly
How I actually use AI - hamy.xyz/blog/2025-10...
- Don't outsource the plan
- Do outsource well-scoped tasks w examples
- Checkpoint regularly
How I actually use AI - hamy.xyz/blog/2025-10...
How I Actually Code with AI as a Senior Software Engineer
Date: 2025-10-22 | artificial-intelligence | build | create | tech | vibe-engineering |
hamy.xyz
January 23, 2026 at 1:00 AM
I use AI regularly to help code features. It's still not great at building large features but it's getting good at well-scoped tasks where examples exist.
- Don't outsource the plan
- Do outsource well-scoped tasks w examples
- Checkpoint regularly
How I actually use AI - hamy.xyz/blog/2025-10...
- Don't outsource the plan
- Do outsource well-scoped tasks w examples
- Checkpoint regularly
How I actually use AI - hamy.xyz/blog/2025-10...
What I include in vibe engineering prompts:
• How the codebase is structured
• How the product should function
• Patterns to use and avoid
• How to verify changes
• Definition of success
Treat each AI session like a new engineer and get better results.
• How the codebase is structured
• How the product should function
• Patterns to use and avoid
• How to verify changes
• Definition of success
Treat each AI session like a new engineer and get better results.
January 22, 2026 at 6:41 PM
What I include in vibe engineering prompts:
• How the codebase is structured
• How the product should function
• Patterns to use and avoid
• How to verify changes
• Definition of success
Treat each AI session like a new engineer and get better results.
• How the codebase is structured
• How the product should function
• Patterns to use and avoid
• How to verify changes
• Definition of success
Treat each AI session like a new engineer and get better results.
Every bug, every security hole, every poor UX decision - it's got your name on it. AI wrote the code, but you approved it. You own what ships.
January 21, 2026 at 6:41 PM
Every bug, every security hole, every poor UX decision - it's got your name on it. AI wrote the code, but you approved it. You own what ships.
"When you're generating code 10x faster, you're also generating bugs 10x faster."
AI assumes success unless told otherwise. A failing test suite / type system / linter gives it immediate feedback to self-correct.
AI assumes success unless told otherwise. A failing test suite / type system / linter gives it immediate feedback to self-correct.
January 20, 2026 at 6:41 PM
"When you're generating code 10x faster, you're also generating bugs 10x faster."
AI assumes success unless told otherwise. A failing test suite / type system / linter gives it immediate feedback to self-correct.
AI assumes success unless told otherwise. A failing test suite / type system / linter gives it immediate feedback to self-correct.
AI performs better on focused tasks than 'build me this whole feature.'
Treat commits as save points. One atomic task, review, commit.
When AI goes off the rails, rollback is easy.
Treat commits as save points. One atomic task, review, commit.
When AI goes off the rails, rollback is easy.
January 19, 2026 at 6:41 PM
AI performs better on focused tasks than 'build me this whole feature.'
Treat commits as save points. One atomic task, review, commit.
When AI goes off the rails, rollback is easy.
Treat commits as save points. One atomic task, review, commit.
When AI goes off the rails, rollback is easy.
January 19, 2026 at 7:30 AM
I host my apps with 3 server roles:
* Analytics - for monitoring and admin
* DB - For my Postgres / Redis
* App - For running my apps
I set them up with Ansible and use Nomad for orchestration.
hamy.xyz/blog/2025-12...
* Analytics - for monitoring and admin
* DB - For my Postgres / Redis
* App - For running my apps
I set them up with Ansible and use Nomad for orchestration.
hamy.xyz/blog/2025-12...
January 19, 2026 at 5:15 AM
I host my apps with 3 server roles:
* Analytics - for monitoring and admin
* DB - For my Postgres / Redis
* App - For running my apps
I set them up with Ansible and use Nomad for orchestration.
hamy.xyz/blog/2025-12...
* Analytics - for monitoring and admin
* DB - For my Postgres / Redis
* App - For running my apps
I set them up with Ansible and use Nomad for orchestration.
hamy.xyz/blog/2025-12...
My spec-driven vibe engineering workflow:
• Product spec describes what exists today
• Change spec describes the outcome (not how)
• Plan breaks implementation into phases
• Each session reads the specs / plans before building
• Product spec describes what exists today
• Change spec describes the outcome (not how)
• Plan breaks implementation into phases
• Each session reads the specs / plans before building
January 18, 2026 at 6:41 PM
My spec-driven vibe engineering workflow:
• Product spec describes what exists today
• Change spec describes the outcome (not how)
• Plan breaks implementation into phases
• Each session reads the specs / plans before building
• Product spec describes what exists today
• Change spec describes the outcome (not how)
• Plan breaks implementation into phases
• Each session reads the specs / plans before building
While F# has great features, many can be replicated in other langs:
* Result/Option
* Pipes
* Expressive types
* Unions and exhaustive pattern matching
* Collection iterations
They may not be as elegant but they often can be done.
F# Sucks - hamy.xyz/blog/2025-06...
#fsharp
* Result/Option
* Pipes
* Expressive types
* Unions and exhaustive pattern matching
* Collection iterations
They may not be as elegant but they often can be done.
F# Sucks - hamy.xyz/blog/2025-06...
#fsharp
7 Reasons F# Sucks
Date: 2025-06-18 | build | create | csharp | fsharp | tech |
hamy.xyz
January 18, 2026 at 4:59 PM
While F# has great features, many can be replicated in other langs:
* Result/Option
* Pipes
* Expressive types
* Unions and exhaustive pattern matching
* Collection iterations
They may not be as elegant but they often can be done.
F# Sucks - hamy.xyz/blog/2025-06...
#fsharp
* Result/Option
* Pipes
* Expressive types
* Unions and exhaustive pattern matching
* Collection iterations
They may not be as elegant but they often can be done.
F# Sucks - hamy.xyz/blog/2025-06...
#fsharp
5 AI Coding Best Practices from a Google AI Director (That Actually Work)
January 18, 2026 at 12:25 AM
5 AI Coding Best Practices from a Google AI Director (That Actually Work)
More content -> More training data -> more AI success
Popular programming languages have a virtuous cycle and will continue to improve whereas small languages have a vicious cycle.
hamy.xyz/blog/2025-12...
Popular programming languages have a virtuous cycle and will continue to improve whereas small languages have a vicious cycle.
hamy.xyz/blog/2025-12...
January 17, 2026 at 5:45 AM
More content -> More training data -> more AI success
Popular programming languages have a virtuous cycle and will continue to improve whereas small languages have a vicious cycle.
hamy.xyz/blog/2025-12...
Popular programming languages have a virtuous cycle and will continue to improve whereas small languages have a vicious cycle.
hamy.xyz/blog/2025-12...
January 14, 2026 at 7:00 AM
January 12, 2026 at 6:41 PM
AI is killing Tailwind's business:
* Views to documentation down 40%
* Revenue down 80%
* Laid off 75% of engineers (from 4 to 1)
How AI Killed Tailwind's Business - And How To Avoid a Similar Fate - hamy.xyz/blog/2026-01...
* Views to documentation down 40%
* Revenue down 80%
* Laid off 75% of engineers (from 4 to 1)
How AI Killed Tailwind's Business - And How To Avoid a Similar Fate - hamy.xyz/blog/2026-01...
How AI Killed Tailwind's Business - And How To Avoid a Similar Fate
Essay - Published: 2026.01.09 | 4 min read (1,035 words)artificial-intelligence | business | create | profit | tailwind
hamy.xyz
January 11, 2026 at 6:41 PM
AI is killing Tailwind's business:
* Views to documentation down 40%
* Revenue down 80%
* Laid off 75% of engineers (from 4 to 1)
How AI Killed Tailwind's Business - And How To Avoid a Similar Fate - hamy.xyz/blog/2026-01...
* Views to documentation down 40%
* Revenue down 80%
* Laid off 75% of engineers (from 4 to 1)
How AI Killed Tailwind's Business - And How To Avoid a Similar Fate - hamy.xyz/blog/2026-01...
The ergonomic static rule aims to minimize movement for common actions.
Over the course of a day / year / decade these operations compound leading to stress on your body.
Place monitors to minimize neck movements and use smaller keyboards to minimize keyboard to mouse travel.
Over the course of a day / year / decade these operations compound leading to stress on your body.
Place monitors to minimize neck movements and use smaller keyboards to minimize keyboard to mouse travel.
January 10, 2026 at 11:00 PM
The ergonomic static rule aims to minimize movement for common actions.
Over the course of a day / year / decade these operations compound leading to stress on your body.
Place monitors to minimize neck movements and use smaller keyboards to minimize keyboard to mouse travel.
Over the course of a day / year / decade these operations compound leading to stress on your body.
Place monitors to minimize neck movements and use smaller keyboards to minimize keyboard to mouse travel.