Medium Density is more sustainable. The reason is ROI on shared infrastructure. More density means more value from infrastructure unit. I think this holds true in many systems at scale: * Cities (city vs suburb) * Software Architectures (monolith vs micro)

The Creation Cycle: * Observe * Create * Reflect hamy.xyz/labs/2022-12-t…

Serving Tailwind with ASP.NET: * Tailwind step - Compile and output CSS * App Step - Build dotnet app * Output Step - Place CSS in static folder, start app hamy.xyz/labs/2024-06_s… #tailwind #dotnet

Updating my projects list to surface all my projects that are still online (regardless of whether I'm actively working on it or not) 15/49 still running - hamy.xyz/projects

HTMX is not a silver bullet. It is not great for: * Offline interactivity * Low latency interactivity Luckily few webapps need that. But if you do, maybe reach for something else. HTMX in Production: hamy.xyz/labs/2024-04_h… #htmx #webdev

CloudSeed (my F# project boilerplate) is 92.4% F#

Context switches come in many forms: * A chat ping / email * A 30 minute meeting * People being loud / distracting It's bad for focus and focus is necessary for effective software engineering. hamy.xyz/labs/2024-06_r…

I made a podcast! HAMY LABS POD is (probably) available wherever you listen to podcasts. All episodes: hamylabspod.buzzsprout.com Why I made it: hamy.xyz/labs/hamy-labs…

Result types are a useful construct for representing common logic answers. * Was it successful? * Why/why not? * Adding additional metadata hamy.xyz/labs/2024-06_p…

Why Zig is migrating from AWS to Self-Hosted * Old: AWS S3 + CloudFront * New: 36 EUR / Month Hetzner Server w Torrent secondaries hamy.xyz/labs/2024-09_z…

I like containers. They're a Simple Scalable System for declaring Infrastructure-as-Code for projects large and small. I find this removes a lot of the pain of sharing project code - to other people, deploying to clouds, running on different computers.