Not really a language you would write in but WebAssembly. I have this dream of a single WASM runtime environment across web, desktop, mobile with devs writing apps once, compiling them down to WASM, distributing them over the Internet, and users running them on any platform they like.

A training montage set to music? (I'm forcing myself to not Google this first)

I hope not. I'm pretty sure me and my coworkers would be at each others' throats if it were not for some form of typed JS holding our Frankenstein codebase together.

changhsumath

I remember I clicked into one of his videos from the homepage out of sheer curiosity and ended up getting super distracted trying to solve the take-home exercise at the end

...and then there's Go who just won't let you compile at all

It's obviously:

Traceback (most recent call last): File "./main.py", line 2, in AttributeError: 'str' object has no attribute 'length'

Not programming per se but my sister thinks it's okay to have 300+ Chrome tabs open and just memorize the relative locations of them whenever she needs something. She's lucky she has a beefy computer.

inb4 senior delegates critical decision-making to juniors and only shows up once stuff is on fire

Biology teacher in HS mentioned off-hand that apparently chickens can climb trees. I searched for images online, thought they were funny, and made it my handle.

That's a weird way of writing IntelliJ

I once "biased for action" and removed some "unused" NS records to "fix" a flakey DNS resolution issue without telling anyone on a Friday afternoon before going out to dinner with family.

Turns out my fix did not work and those DNS records were actually important. Checked on the website halfway into the meal and freaked the fuck out once I realized the site went from resolving 90% of the time to not resolving at all. The worst part was when I finally got the guts to report I messed up on the group channel, DNS was somehow still resolving for both our internal monitoring and for everyone else who tried manually. My issue got shoo-shoo'd away, and I was left there not even sure of what to do next.

I spent the rest of my time on my phone, refreshing the website and resolving domain names in an online Dig tool over and over again, anxiety growing, knowing I couldn't do anything to fix my "fix" while I was outside.

Once I came home I ended up reversing everything I did which seemed to bring it back to the original flakey state. Learned the value of SOPs and taking things slow after that (and also to not screw with DNS).

If this story has a happy ending, it's that we did eventually fix the flakey DNS issue later, going through a more rigorous review this time. On the other hand, how and why I, a junior at the time, became the de facto owner of an entire product's DNS infra remains a big mystery to me.

It's starting to. I think for me at least it's because I'm missing checkpoints in life. Every year used to be its own well-defined column of paint on a canvas but ever since I started working, the last few columns have felt like one giant smear.

I don't like where I've ended up so been trying to make my own goals and hobbies but it takes so much more effort than when most goals were planned for you in school. Perhaps something to add to the New Year's resolutions...