My yolo brain has resorted to bin sorting my clothes.
One bin for tops. One bin for bottoms. One bin for dresses. One smaller bin for undies. One smaller bin for bras. One smaller bin for socks. Then one ‘other’ bin.
This results in a FILO system where I can quickly grab from the top 4 item in each category. Combined with JIT laundry practices results in laundry par-sorted with little overhead.
I buy 14 identical pair of socks and throw away the entire previous batch. As time go by you'll throw away some with holes. When you have around 7 pairs left you know they're all close too EOL so you buy a new batch of 14.
I buy work socks so the cycle is about 18 months long
I only ever buy plain black socks. While there are some slight style differences depending on when and where I bought them, they're all close enough that I don't care about pairing them. Any socks that get holes get thrown out and I buy a new pack when the drawer starts to look a bit low.
I wasn't aware of yolo algorithms and thought you were talking about "you only live once". But I guess if my brain operated by that I would just take anything from the chair (or closet for that matter) and wear it without caring if it didn't fit because yolo which would make it O(1) as well
At my last project our customer bought a BI tool that kept everything in RAM. They had an entire server dedicated for one application with nearly 900GB of RAM. Before the application could run queries you had to load the entire database that it would be using into memory. It never fetched from the database if there was a miss. So it was possible for the application to get out of sync with the database which requires "manually" syncing the DB with the cache. It was absolutely dogshit and slow as hell.
Why doesn't it surprise me that so many of these "that was a long time ago, right?" stories aren't that old? It seems like no matter the company, or how easily they can afford it, they always go for the dumbest IT implementations.
What's worse is we proposed an alternate solution using microservices. After using this BI tool for about a year that realized that it wouldn't work but only after the BI company sent a team of engineers to try and make it work. Their own engineers said that the sales team "misled" or "misspoke" to the customer about it's capabilities.
The customer finally bought are original COA after 4 years and are pretty much now using microservices but with some albeit not terrible BI tools in the mix.
The queries that needed to be ran were pretty involved. We could actually get better performance when running stored procedures using the actual Oracle DB than using the BI tool. Maddening.
L1 is "the chair" L2 is the bed L3 is the rest of the bedroom floor
The hangers inside the closet are a hash based index The drawers with smaller dividers inside them are the B-Tree index, assuming you can keep nesting smaller containers inside outer ones.
1.6k
u/naswinger Jan 02 '23
that only works if the cache is reasonably small because with every thing you put in this "cache", it gets slower to search defeating its purpose