rand_r

Which part? Hard to have a discussion without specifics.

The honest way to handle this, which hopefully your therapist does, is not to claim that you can magically retrieve perfect memories from before 5 because you thought about it hard. What matters is what your impression is of what happened and what messages your subconscious is sending you. Whether or not it literally happened isn't that important and it's impossible to know.

The therapeutic relief comes simply from listening to your gut/subconscious and feeling the emotions that that brings up. Being a loving friend and parent to that part of yourself. You can do that effectively without pretending that you can know if the impressions are literally true or if that message your getting is simply the best way for it to express the emotions it's holding onto.

Again, you can maintain your integrity while being empathic and loving and listening to the message.

"Trauma" is a very bad name because it sounds violent and extreme, so you can easily think it doesn't apply to you. In actual fact, it can be caused by something as routine as "sleep training" where infants are left to cry themselves to sleep, or being snapped at for expressing emotion, all before the age of 5. The years before 5 are foundational, but you usually no not have memories earlier than 5 so it's very hard to say definitely what happened especially when causes for trauma are relatively routine.

You need a trusted therapist to guide you into exposing what the subconscious mind is holding onto from infancy. It is subtle, deep, difficult, rewarding work. But I do think people discount trauma because it sounds scarier than "someone snapped at me in frustration as an infant for expressing some emotion and I learned to disconnect from myself."

The end game is adaptive query plans.

A big reason the initial plan isn't guaranteed to be optimal, even with all the right indexes, is that table statistics aren't perfect. For example, you might track a column's correlation (how closely the column's logical ordering matches its physical ordering in the heap), but that won't be broken down at a per value level. Postal code X might be very correlated, while postal code Y that is used in your query is completely uncorrelated.

The ideal solution is to pick one plan initially, and then update a temporary query-specific statistic model based on the data you actually read while executing the query. Then periodically re-evaluate if an alternative plan would be faster, switching to it in a way that doesn't throw away the current partial result.

Of course switching plans mid flight is very complicated, but Oracle and SQL server both support this feature, so hopefully it lands in Postgres at some point.

It's been quite helpful when your project needs expertise from other people, and you want them to vet your approach and find gaps. Doing the up-front work of explaining the context and structuring the project in an easy to understand way makes it more likely for busy people to engage with it and help you out. Of course, it's helpful as a rubber-duck exercise on its own, so I would err on creating one, even if just for myself, for anything high-risk or hard to change later.

That's fine, but rate limiting is a solved problem at this point. They need to rate-limit free accounts and be realistic about their limits instead of letting the system fail.

> all viewpoints covered from you populace

This is the core of the issue. We don’t actually want all viewpoints represented because that wouldn’t by itself produce any value.

You want someone to come up with the fundamental theorems of Calculus, linking the area of a curve with its anti-derivative, because that’s incredibly useful. Generically grabbing everyone’s view isn’t a competitive strategy. You need to be selective on things that are intrinsically useful and promote that.

> When I watch a movie, I don't care about the artist's life. I care about character life, that's very different.

It may seem like this, but up to now, you haven't been able to divorce a story from its creator because every story has an author, whether it's a novel like Harry Potter or a movie that has a writer and director. When you're experiencing the story, in the back of your mind, you always know that there is someone who created the story to tell you some kind of message. And so you can't experience something like a movie without trying to figure out what the actual message behind the movie was. It is always the implicit message behind the story that makes it valuable versus just the elements of the story.

The story has more weight because it is the distillation of somebody else's life and most likely, if it's a successful story or book, it is the most important lesson from that person's life and that's what makes it more valuable compared to the random generation of words from a computer.

The food analogy is that a cookie baked and given to you by a friend is going to taste far better than anything you buy in a store.

Only in as much as their product is a pure commodity like oil. Like yes it’s trivial to get customers if you sell gas for half the price, but I don’t think LLMs are that simple right now. ChatGPT has a particular voice that is different from Gemini and Grok.

There is no difference between “def f(x={})” and “def f(x=dict())”, unless you have shadowed the dict builtin. They both have exactly the same subtle bug if you are mutating or return x later.

You can use “set()”. Introducing more weird special cases into the language is a bad direction for Python.

This is something you see in movies. Cash is by nature not traceable, so invalidating notes after issue would make it impossible to trust any cash transaction.

> to see if the serial numbers are out of circulation.

Cash cannot be invalidated like this. It would ruin the value of all cash since you could no longer trust cash from anyone. Only damaged notes are taken out and replaced by the government.

Not sure what you mean!? Locks, at their core, are not implemented by languages. They’re feature of a task runtime e.g. Postgres advisory locks or kernel locks in a Posix OS.