Pay your damn employees

My most recent complaint is about index mappings. I have 2 types in 2 different indexes that each have a field with the same name. One index has a hand written mapping. The other index is currently under active development and doesn’t have a mapping for it yet so it’s built automatically. When I insert into the index WITHOUT a mapping, the index WITH a mapping changes the field into a keyword and no further queries against the index WITH a mapping work. This also happens if I insert into the index WITHOUT a mapping before the other index is created. Why does the index WITH a mapping change?!? WE WROTE THE MAPPING FOR A REASON BUT ITS IGNORED!?!

ElasticSearch would make me drink if I drank

I wish more people knew about dtrx (Do The Right eXtraction).

I still blame Jeep for thinking a rotating selector was a good idea for a gear shifter. RIP Anton Yelchin.

I used to maintain a wordle clone. I was meticulously making sure that any changes in the NYT word list would be reflected in my app as well, the goal was synchronization because the secret to wordle is that we’re all playing the same game… until we’re not. I haven’t touched that repo in months. The NYT can suck it.

Without the only app store that matters, this was dead on day 1 for me.

Sticking your head in the sand is a great alternative /s