> I have zero knowledge of k8s, helm or configmaps.
Obviously this is not anything resembling engineering, or anything a respectful programmer would do. An elevator that is cut lose when you press 0 also works very well until you press 0. The claims of AI writing significant chunks of code come from these sort of people with little experience in programming or engineering in general, SPA vibe coders and what not. You should tremble at the thought of using any of the resulting systems in production, and certainly not try to replicate that workflow yourself. Which gives you a sense of how overblown these claims are.
> The claims of AI writing significant chunks of code come from these sort of people with little experience in programming or engineering in general, SPA vibe coders and what not.
I'm sorry man but I've been doing this for 25 years and I've worked and studied with some extremely bright and productive engineers. I vouch for the code that I write or that I delegate to an LLM, and believe it or not it doesn't take a magician to write a k8s spec file, just patience to write 10 levels of nested YAMLs to describe the most boring, normal and predictable code to tell your cluster what volume mounts and env variables to load.
> I have zero knowledge of k8s, helm or configmaps
…
> I vouch for the code that I write or that I delegate to an LLM, and believe it or not it doesn't take a magician to write a k8s spec file…
I have been writing code since 1995.
That has zero relevance to my skill at rolling out deployments in a technology I know nothing about.
One of the two things you’ve said is false:
Either a) you do know what you’re talking about, or b) you are not confident in the results.
It can’t be both.
It sounds to me like you’re subscribed heavily into a hype train; that’s fine, but your position, as described, leaves a lot to desired, if you’re trying to describe some wide trend.
Here my anecdote: major cloudflare outages.
Hard things are hard. AI doesn’t solve that. Scaffolding is easy; ai can solve that.
Scaffolding is a reliable thing to rely on with ai.
Doing it for K8s configuration, if you don’t know k8s is stupid. I know what I’m talking about when I say that. Having it help you if you do know what you’re doing is perfectly legit.
Claiming it did help when claiming you have, and I quote, “zero knowledge” (but you actually do) is hype. Leave it on LinkedIn dude. :(
> Either a) you do know what you’re talking about, or b) you are not confident in the results. It can’t be both.
You've been coding for a lifetime yet you don't seem to get that certainty in software is a spectrum? I have sufficient confidence in the output of LLMs to sign my name under the code it writes when putting up a PR for a specialist to read. That's good enough for 90% of the work that we do day-to-day. You think that's not hype-worthy?
> Doing it for K8s configuration, if you don’t know k8s is stupid. I know what I’m talking about when I say that. Having it help you if you do know what you’re doing is perfectly legit.
"Knowing" k8s is an oxymoron. K8s is a profoundly complicated piece of tech that can don insanely complicated things while also serving as a replacement for docker-compose or basic services that could have been hosted on ECR. The concepts behind basic k8s functionality are not difficult, but I saved myself two weeks of reading how to write helm spec files, a piece of knowledge I have no interest in learning because it doesn't add any appreciable value to the software I produce, and was instead able to focus on getting what I needed out of my cluster automation scripts.
This really isn't that complicated to understand. I don't care for being a k8s expert and I don't care for syntactical minutiae behind it. It isn't hype that I now I only need to understand the essential conceptual basics behind the software to get it working for what I need instead of doing a deep dive like I had to do years ago in when reading similar docs for similar IaC producs to get lesser functionality going.
> One concern was that Arenas introduced “Use-After-Free” bugs, a classic C++ problem where you access memory after the arena has been cleared, causing a crash.
In Rust, can the lifetime of objects be tied to that of the arena to prevent this?
Asking as a C/C++ programmer with not much Rust experience.
Yes, or rather, the lifetime of references to the contained objects can be tied to the lifetime of references to the arena. E.g., the bumpalo crate [0] has two relevant methods, Bump::alloc(), which puts a value into the arena and gives you back a reference, and Bump::reset(), which erases everything from the arena.
But Bump::reset() takes a &mut self, while Bump::alloc() takes a &self reference and gives back a &mut T reference of the same lifetime. In Rust, &mut references are exclusive, so creating one for Bump::reset() ends the lifetime of all the old &self references, and thus all the old &mut T references you obtained from Bump::alloc(). Ergo, once you call Bump::reset(), none of the contained objects are accessible anymore. The blogpost at [2] gives a few other crates with this same &self -> &mut T pattern.
Meanwhile, some crates such as slab [1] effectively give you a numeric key or token to access objects, and crates differ in whether they have protections to guarantee that keys are unique even if objects are removed. All UAF protection must occur at runtime.
Obviously you have no kids or live in a remote cabin isolated from society.
Banning social media in principle is like banning the sales of alcohol and other drugs to underage people. Those bans are good for society irrespective of your parenting ability. It helps that those negative things are less accessible to the vulnerable.
Now, how the social media ban is effected in practice is a different point. And people here are rightfully skeptical of ID verification and such things, since that opens the door for way more surveillance outside social media.
I do have kids and they are well adjusted individuals. I spent time parenting them and showing them how the world works.
Turns out the social media drug loses all it's power if you reveal whats behind the curtain. Just like real drugs, dont be scared to show your kids what the consequences are.
I wasn't aware that banning alchohol and drugs to minors had any positive effect tbh. If anything that in itself made them more desirable and sought after.
Of course, being able to call out a sorting algorithm is the kind of thing that makes you very "cool and in touch" in the grander scheme of things, unlike, say, playing sports or lifting 500lbs.
My masters was also on procedural generation. Now I wonder how many of us are out there.
At any rate, given that this paper divides the terrain in regions and apparently seeds each region deterministically, it looks like one could implement a look-ahead that spawns the generation on async compute in Vulkan and lets it cook as the camera flies about.
I think it's catnip for programmers, myself included. (See also: boids, path traced renderers, fluid simulations, old fashioned "generative"/plotter art, etc. - stuff with cool visual output)
Boids, Game of Life, Genetic Algorithms, Pixel Shaders...
All so satisfying to play with.
One of my favorites was when I was sure I was right about the Monty Hall problem, so I decided to write a simulator, and my fingers typed the code... and then my brain had to read it, and realize I was wrong. It was hilarious. I knew how to code the solution better than I could reason about it. I didn't even need to run the program.
Which is what a sane terrain system would do. Just beyond the far plane you would load/gen the tile/chunk and as you got closer, increase the resolution/tessalation/etc. (or you start with high and each level away you skip vertices with a wider index march for a lower lod).
In any case, like I said, I welcome any new advances in this area. Overhang being the biggest issue with procedural gen quad terrain. Voxel doesn’t have that issue but then suffers from lack of fine detail.
There's a whole genre of viral social media posts that amount to lumping anyone who appears to have cared quite a bit about something that's not obviously exciting (to most other people) into the autism spectrum. Especially historical figures. "This guy made tons of detailed beetle drawings and cataloged them in books! See, there have always been autistic folks, because he definitely was!"
Like I mean maybe, but also he was a bored rich aristocrat before TV was invented, and sometimes there are no parties going on or everyone's hiding in their country estates because of a cholera outbreak or whatever, and "making shitloads of drawings and organizing them" was like 50% of scientific work at the time. So. Maybe he just had a lot of time to kill.
Going by randos posting online, "liking things" and "knowing stuff" and "caring about things" are all autistic traits when present in any but the tiniest of degrees. It's ridiculous.
It's getting a tad out of hand. A friend "jokes" that I'm on the spectrum fairly often any time I speak with any sort of passion on topics in interested in or care about.
I feel social media has conditioned people to think of you're anything other than bland and "normal" in your personality and have any degree of uniqueness about you then you're on the spectrum.
I generally try to avoid tossing disorders around as a way of describing personality, because I don't want to trivialize somebody's experience for whom that disorder is very troubling.
Actually, I'm allowed to be persnickety about language without it implying a diagnosis of any kind.
But I thought it was kind of funny to share it the way I did, so I made an exception.
I only wish my systems to defecate its corpse soon.
reply