The normal practical version of this advice that isn't a "guy who just read about arenas post" is that you generally kick allocations outward; the caller allocates.
It's apparently lese-Copilot to suggest this these days, but you can find very good hypothesizing and problem solving if you talk conversationally to Claude or probably any of its friends that isn't the terminally personality-collapsed SlopGPT (with or without showing it code, or diagrams); it's actually what they're best at, and often they're even less likely than human interlocutors to just parrot some set phrase at you.
It's only when you take the tech out of the area it's good at and start trying to get it to "write code" or even worse "be an agent" that it starts cracking up and emitting garbage; this is only done because companies want to forcememe some kind of product besides "chatbot", whether or not it makes sense. It's a shame because it'll happily and effectively write the docs that don't exist but you wish did for more or less anything. (Writing code examples for docs is not a weak point at all.)
Idk, depends on the situation. Is he a student trying to show stuff on a resume? Is he a professional trying to sell a product? Is he a researcher trying to report findings? A startup trying to land a pitch?
The value isn't objective and very much depends on end goals.People seem to trounce out the "make games, not engines" without realizing that engine programmers still do exist.
It was just a small personal test of skill with no purpose or stakes. Not even really with intent to make a real game, just a slice of something that resembled a game to see how far I could get without help. Then, once I got as far as I could, research and see how I could do better.
American jurisprudence has the best standard for incitement in the world, the Brandenburg standard: imminent lawless action. "Imminent" is vital, and unique to America; the government is barred from constructing hypothetical situations around acts of speech to prosecute them, as is easy to do with quite a lot of speech.
And we only reached it in the 1960s! Freeing speech is always an active fight.
These days, I often just go straight to the source (when available) to clear some confusion about the library/software behavior. It can be a quite nice 10 mn break.
yeah the claim is ambiguous because the beam itself is only guaranteed soft real time, leaving it open ended might make ppl think hard real-time especially since its hardware
> Do you actually think dead simple failover is comparable to elastic kubernetes whatever?
References to "elastic Kubernetes whatever" is a red herring. You can have a dead simple load balancer spreading traffic across multiple bare metal nodes.
