Very cool. Out of curiosity, for the retries why are the errors appended as system messages as opposed to appending to the user message? And in either case, would it help to prepend the error with something like “Be sure to avoid outputting something that would cause this error:”?
Understanding query plans is a universal skill that mostly transcends database particulars, so even this Planetscale article will serve as a good primer too.
This series of blog posts is one option. But my impression is that most of this comes simply with experience. At first the main thing you'd look for is simply whether it uses the indexes you want it to use, or if it does full table scans.
I'd also recommend to simply read the Postgres manual, at least the parts that are not entirely about the syntax of various commands. There is a lot of information in there that will help to understand how Postgres works.
I personally prefer https://explain.dalibo.com over depesz's version, both from a visualization standpoint (I can more clearly see the hierarchy of operations) but also because I've had some not great experiences with depesz the individual. Great blog, but a really soured opinion of him.
Note that the official docs are not always the best resource for a given topic (in general - I don't know about Postgres specifically). "What is the best resource" is a totally reasonable question, and general opinion may be that the answer is the official docs.
On top of that, there's a pretty strong argument to be made that Fortnite is as much about socialization and open-ended interaction as it is a game. Apple banning what's potentially a next-generation social network from their platform isn't a great look.
A counter point is that it was an extremely reckless move for Epic to risk the banning of their next-generation social network (which to my kids, it definitely is) from the largest mobile store. Epic thought they were forcing Apple's hand, but they lost in court on the points they really cared about the most. And they got confirmation that Apple was well within their rights to cancel the developer account.
I'm not sure the risk was worth it... especially since they didn't need to take that risk to file the lawsuit.
From the first moments, Epic has been running a PR campaign, which doesn't really help you in court.
As an adult who's partner plays and plays occasionally, Its honestly really about group chatting (voice comms) with friends/relatives as much as it is about the game for us. I mean the game is silly and fun, but really its a group thing. I almost never play when not with friends.
And occasionally there are group events/ a concerts and movie screenings.
We're all on PCs/ Consoles, but if your a kid a free to play game your friends are on you could join in with a tablet, would be nice.
I agree with HOCON being nice based on personal usage but I haven't seen an in depth analysis of it. This is the canonical parser for JVM based languages — https://github.com/lightbend/config, are there many other implementations that are widely used?
Interesting to see all the traction this is getting, I think that it certainly addresses a need! I stumbled upon this a few months ago when I saw this website which was made by the same folks: https://whydoiprocrastinate.com/
Buildkite (https://buildkite.com/) is so underrated and really nice! Much simpler interface than most other providers like Circle CI or TeamCity and works really well.
Buildkite is my go-to CI in my professional work as well. The hybrid model (the master is SaaS, but you bring your own agents) works so well both from a cost-efficiency perspective, and also when working with enterprises who don't like builds occurring on machines they don't control.
Thanks, this looks interesting, since it lets me build on my own machines (I really need to control the environment, eg. build and test on specific versions of macOS)
This is what the (now defunkt) Capsule project prepends to get this same effect