Given that an md5 hash is 128 bit, by simple brute force, you would need to try 2^128 variants (in expectation) to find the matching hash. Thats rougly 10^38 combinations. That's a huge number, I can't imagine that the author simply hashed variants until one happened to match, there must habe been some other technique involved.
I currently have a full time job. There is the option of reducing to 80%, but that comes with the respective salary cut. I'm wondering if it's worth it, also the increased productivity is not accounted for from a financial perspective.
Sounds like a dream. I'd love to work in short bursts of highly productive work instead of full work weeks of mostly lingering around and wasted time to fill the hours. I wonder though, how does it work out financially?
Agreed. For me personally, commuting is a big factor - I love not doing it...
Unfortunately, permanent WFH will probably not work for me for other reasons, in particular I think that the face to face interaction with coworkers cannot be replaced...
Clever optimization engines are IMO no excuse for blindly throwing queries at it and not knowing what's going on. Every optimizer has some corner cases in which it fails and I'd argue that as a good developer you should know when they can happen.
Additionally, in this example, the rewritten query is easier to read and maintain.