Aaron Munger

@amunger.bsky.social

VS code developer, mostly in the notebook UX. Father of two in the Seattle suburbs. Hobbyist woodworker. eBike commuter. Beer enjoyer.

Tying in benchmark evals into LLM RF seems to be making the latest models very good at convincing me that it was successful at completing my ask. I have to look pretty carefully to notice the logical leaps or bad assumptions.

I'm still working through the "Crafting Compilers" book. I spent at least an hour trying to figure out why my C program was returning something like 3.67e-307 for every value I was trying to store in a byte array. After adding a bunch of printf statements to debug, it just suddenly started working.

PSA - 6 years old is a great time to be introduced to Star Wars. I'm through the original trilogy and episode I with my daughter, and she is loving it. Seeing her reaction to "I am your father" was very satisfying.

I don't understand why rust gets such an exceptional amount of love in those SO dev surveys. The learning curve feels so steep with all that syntax and the ownership restrictions. I'm still willing to slog my way through as I learn it, but why does it appeal so widely?

I'm through part 2 of Crafting Interpreters and I even added arrays to the language for the jlox tree-walk interpreter as the final challenge exercise. I wasn't sure how much I was picking up while reading through, but adding my own feature really helped cement the material in my mind.

I was initially disturbed by importing functions in typescript and using them as if they were local but have grown comfortable with it. Now I can't stand seeing a class member used within the class without using prefixing with "this".

You sometimes discover that a "bad practice" in software can actually be perfectly suited for a specific case. The latest one for me was using exceptions for control flow to implement return statements while reading Crafting Interpreters.

If a command isn't doing quite what you would expect in vs code, but you can't convince the developers to change the behavior, you might be able to adjust it yourself by combining commands in a custom key binding.

A top QOL improvement for working on a11y features is NVDA's speech viewer: right click the taskbar item -> tools -> speech viewer. Not being a screen reader user myself, I find the audible narration incredibly distracting, and this way I can turn the narration volume to 0 and still test a11y.

I still remember my first post on Reddit, replying to an r/explainbothsides post about UBI. It seemed pretty innocuous, but the OP apparently looked through my profile and replied with "What a strange first post!" and I still can't figure out why.