Zorn of the Dead ๐ŸŽƒ

Zorn of the Dead ๐ŸŽƒ

@mikezornek.com

Developer and Teacher. Working day-to-day programming in Elixir and LiveView. Learning CRDTs, Rust, Svelte, and DevOps automation in my free time. Looking for part-time Elixir contracts. Video gamer and Phillies fan. https://mikezornek.com

178 followers220 following665 posts

Zorn of the Dead ๐ŸŽƒ reposted

An #ElixirLang package to check your `@spec` annotations against the types the compiler infers. Definitely the sort of thing with a limited shelf life (assuming we eventually get the ability to write our own compiler-checked types), but in the meantime, seems super valuable. hex.pm/packages/spe...

hex.pmspec_lintChecks Elixir @spec declarations against compiler-inferred signatures

๐Ÿ‘จโ€๐Ÿ’ป Doing Erlang version bumps to address the latest advisories. If you don't increase your update frequency to match the faster reporting, you could be at risk. I think bad actors are probably just cataloging known tech stacks and watching these announcements day by day at this point. #ElixirLang

github.comBuild software better, togetherGitHub is where people build software. More than 225 million people use GitHub to discover, fork, and contribute to over 800 million projects.

๐Ÿ‘จโ€๐Ÿ’ป Looking forward to a relatively quiet week ahead. I have some client hours to kill, but otherwise I'm continuing my deployment and exploration of Prometheus and Grafana for my side project Flick. Got the basics working last week; next up: alerts, tracing, and SQL-sourced dashboards.

๐Ÿ‘จโ€๐Ÿ’ป AI is constantly pushing me to resolve race conditions related to real-time LiveView pages (assume multiple people editing the resource), time zone concerns related to Havana transition day `AmbiguousDateTime`, and database `FOR SHARE` locks to help with data integrity.

In one breath, these are great observations that will make more resilient software. In another breath, I feel like I know how my software will be used, and this extra code/complexity feels like an unnecessary weight.

โœ๏ธ My pull request for a refund feature grew past 3,000 lines. At that size, a code review can't do its job: reviewers miss things or rubber-stamp it. So I stopped adding to it and started extracting the unrelated fixes and tests into their own PRs. mikezornek.com/posts/2026/9...

mikezornek.comWhen a Pull Request Balloons, ExtractMy refund feature's pull request grew past 3,000 lines. Instead of shipping it whole, I've been pulling out the bug fixes and tests into their own PRs.