hurry coward

they did the check-in inventory without me there before the tenancy started, which should probably be illegal

they're insisting the check-out inventory can only be done on the final day of the tenancy, which would require me taking leave from work or, they can do it without me there, seems cool

they have had two months to do their tiny amount of admin, during which time I have done little but sort out my move and find somewhere new to live

my tenancy ends on friday. today, with no weekend between now and then, they email with a ton of extra-contractual preconditions and them returning my deposit

estate agents get even a single thing right challenge

parts of it are in alphabetical order parts of it are in *reverse* alphabetical order? it's like a poorly shuffled deck of cards

why has spotify made my list of artists completely unusable

ah yes, the olympic opening ceremony, that soaring tribute to the working classes, that followed years of forced evictions of local communities to make way for construction

ah yes, 2012, when everything was perfect, and [checks notes] things were already so bad the entire stadium booed george osborne

professional satirists being fully taken in by the olympic propaganda, you hate to see it

I'm still wrapping my head around appointing dorries to the health department, that is proper gilead territory

turns out I didn't know why everyone was posting "bigger than before" because I'm blocked by the account that posted the video

remember the big cow

JS: - ascribes a non-constant boolean value to numbers - prevents NaN from yielding a numeric result in numeric concepts - allows NaN to be interpreted as boolean this is a huge design flaw

side effect of all this: I've been reminded that NaN is considered false, when it should be considered an error to use it in boolean context

make jsconfeu talk last year was all about how a lack of clear thinking about conceptual complexity in JS APIs directly leads to making change hard to manage, so I have a bee in my bonnet

so putting them in a category together and excluding other values that have the same boolean behaviour and are arguably closer to null in terms of a type theory analysis, makes no sense it is unpredictable, which I would argue means it is unergonomic

if you attempt to statically type JS, undefined and null must *necessarily* have different types because the set of computations that can eval to undefined is a strict superset of those that can eval to null