Mostly writing code that does stuff…
Say it out loud: aichteeteapee. Go on. Sound it out. Aitch-tee-tee-pee. Yeah. That’s HTTP. I named my Go HTTP library by spelling “HTTP” phonetically and published it with a straight …
Every service I write needs exactly one piece of information before it does anything else: is this thing running in prod, or is some poor bastard (me, at 2am, half …
x-constants: int: defaultPageSize: &defaultPageSize 20 maxPageSize: &maxPageSize 100 uint: minPasswordLength: &minPasswordLength 8 float64: requestTimeout: &requestTimeout 30.5 string: defaultLocale: &defaultLocale “en-US” bool: enableCache: &enableCache true // Code generated by oapixconstgen. DO …
Remember when software-defined radio transmission required expensive hardware, complicated software, and a PhD to configure? Yeah, fuck that. I built PIrateRF to prove you can turn a $20 Raspberry Pi …
Look, I’ve built a lot of shit in Go. Worked on microservices that were basically just glorified HTTP handlers talking to each other across Docker networks. Debugged race conditions at …
When I was building PIrateRF, I had two options. Option one: shell out to a pile of C binaries from rpitx every time I wanted to key up a transmitter, …
Look, if you’ve ever wasted more than 5 minutes trying to hunt down which structs actually implement a Go interface, you already know this pain. It’s like trying to debug …
Let’s be fucking honest here – if you’ve ever tried to do anything serious with Go’s os/exec package, you know it’s about as user-friendly as a cactus suppository. Want to stream output …
Look, I’m gonna be straight with you. Go’s error handling is fucking verbose, and debugging without context is like trying to find your keys in a pitch-black room while drunk. …
⚠️ Archived in favor of slog-configurator. Go’s standard library now ships log/slog, which covers everything logrus offered with proper context propagation and zero third-party dependencies. logrus-configurator still works and existing …