Reading the article, you can sense the author's sheer feeling of incredulity rising by the second. (the link in the skeet is a share link)

‘You Can’t Let This Happen,’ Says Fundraising Email From Sitting U.S. Congressperson

‘You Can’t Let This Happen,’ Says Fundraising Email From Sitting U.S. Congressperson

On Misery Not every fun activity or moral good is a waste of time.

Wrote about the irrationality of the boss revolt mcfunley.com/on-misery

Ah, yeah. Sounds like a problem for a (static) callgraph analyzer (and probably visualizer). I haven't played with the Go callgraph tooling at all, I'm guessing the static analysis is unsatisfactory?

Definitely not a panacea, but this sometimes helps: change a datatype and/or manually change a field name near the area being worked on, such that the compiler fails out at places that stuff gets used. Then just keep fixing each compile problem until you've visited all the affected sites.

This is a humorous diagram depicting common elements of cloud architecture, drawn in a casual sketch style. It's organized into several sections: At the top: "Global Assumptions" contains various services connected through a "Frickin' Slick Reverse Proxy" with "CIDR Shenanigans" and a "VPN of Sadness." Middle section: Features "CONTAINERS!!!" with stylized container icons and includes: "Cool Databases" "Event Bus" flowing directly into someone's "RÉSUMÉ" "Real Database" with "Midnight Heroics" and a complex pipeline labeled "The Data Engineers Got Very Excited Here" Bottom section: "Blame Radius" showing different service categories: "Services that Start Stuff" "Services that Stop Stuff" "Services that Like to Watch" "One Tiny Cron Job that Keeps Everything from Failing Apart" Ends with "Data Lake" flowing into "Data Swamp" The image is credited to @forrestbrazeal and uses a light-hearted tone to poke fun at typical cloud architecture complexities.

good morning and welcome to 2025