This is giving the same vibe as Windows Subsystem for Linux[0] - it kinda makes sense once somebody explains it, but is confusing as hell when you first see it
Not the person you replied to, but like them, I too liked to draw imaginary maps when I was a kid, mainly of medieval towns. I also tend to like the world-building aspects of strategy games, arguably more than the actual strategy parts.
Cities: Skylines have been in my wishlist since shortly after it came out but I never got around to playing it until about a month ago, and... didn't like it at all. It felt too "micro-manage-y" (for the lack of a better word) while also having the pressure of the ticking time.
Needless to say, I was very disappointed after looking forward to it for ~10 years.
Check out The Payments Engineer Playbook[0]. I don't work on financial systems but I'm subscribed and like the occasional distributed systems insights.
One of the posts turned up on HN front page a year ago[1]. Thats how I discovered it
Recently I've been wanting to build a chat server that works over ssh. And by that I don't mean it uses the ssh protocol but that you ssh into the server and the shell you get is the chat client.
Avoiding N+1 doesn't have to mean limiting yourself to 1 query. You can still fetch the posts in one query and the comments of _all_ posts in a separate query, just don't issue a query for _each_ post.
More formally, the number of queries should be constant and not linearly scaling with the number of rows you're processing.
FWIW I like Level 2 Jeff more and I would watch the videos with or without the clickbait-y titles. As you've said I've never found your titles deceptive so if they bring you more money, then more power to you
> the original/popular definitions were so incredibly abstract and disconnected from real life usage that they ended up being whatever the person implementing it wanted it to be.
This is what happened with REST too, and it frustrates me more than it probably should.
The original pattern is such a good idea and not even remotely abstract. It's a well defined architectural pattern for a well defined problem yet people still managed to bastardize it to the point that the term REST barely means anything today
0. https://www.reddit.com/r/bashonubuntuonwindows/comments/t952...