Andri Braun πŸœ¬πŸ’»πŸŒˆ

@neonbinary.com

Web developer, emigrant, nerd, pun-creator. Bleeting about code and miscellaneous distractions I find while I'm building internet things. Probably more optimistic than I should be, but I don't think that's a problem πŸ—© they/them 🌐 https://andribraun.dev

Shopify just auto-migrated my app to some "next-gen developer" thing, so now my apps need emergency reconfig. Of course, this happened right while I was trying to do ANOTHER emergency fix. Like, maybe give me 10 warning emails and let me migrate on my own time instead of randomly dropping this?

Part of my job is now reviewing and correcting AI-generated code, and while it has quite a few issues, the most annoying one is that it apparently just refuses to use SCSS. It can be working on an SCSS module with established nesting, and it decides to add its own unnested class right at the bottom.

TIL that JavaScript primitives are passed by value whereas objects and arrays are passed by reference. So a = 1 will always be 1 if you pass it to a function, but a = { value: 1 } can be updated. I don't often have to track state in vanilla JS, so this just somehow never came up before!

Pro(grammer) tip: naming all your variables in complex functions with just one letter is super cool and will make other programmers respect you. Why name something "indexOfSymbol" when you could instead name it "p"? Assigning the value of an input? How about "nm" instead of "inputValue"?

This season of the show is getting a little out of hand. Like, really, "the global resurgence of fascism" again? I was already having trouble following the "big war", "AI revolution", and "intentionally ignored climate disaster" storylines. At least we mostly wrapped up "weirdly political pandemic"