If you want something scary, go with a shirt that’s a stack trace about an error on line 9376.

If you want something funny, look at deranged as possible with a shirt that says “stakeholder” or “end user”.

Sometimes you have to do something this. Like when working with a horribly designed legacy database that put property values in a child table and you need to map those to actual properties in your API model.

Sometimes you get the opposite too. Like an 8pm slack message stating the head of engineering has “decided to step down effective immediately” (aka: forced to resign). Which is a nice surprise cause you had a meeting booked with them for tomorrow.

I love javascript and how loosey goosey it is, I must be the odd one out. Then again my apps tend to be database driven so it’s mostly just a UI and very thin API layer.

x is used for map, filter, etc. a and b are used for sorts, comparisons and merges. y might be used if I’m doing multiple lambda expressions (but that means I’m in a bad place already). I have no idea why, but these are firm rules in my brain.