> Side note: Why use a raw IP address? If anything, this screams “malware.” At least register a decoy domain like lint-checker.com or jenkins-ci-runner.net. If the threat actors who wrote this are reading: take notes people!
Maybe they don't want to give any identifying info to the domain registrar? Or just minimizing their online presence?
right, I guess what I mean is that in the past you would pick an architecture based on your data structure/flow, performance requirements, things like that. Now there is a new metric: how LLM-friendly it is. Probably it won't be a huge factor, since a properly structured REST server would also be friendly enough, and LLMs are getting better. Still interesting to consider though, IMO.
yeah it does fine with bevy. It struggles a bit to structure the components in the best way, so that still requires some human oversight if you want it to be good. It helps a lot to emphasize that you want "idiomatic" bevy code, and ofc it also helps a lot to spend a lot of tokens on design and review (e.g. "is this the most elegant way to structure these systems/components?"). There's also this feature called Bevy Remote Protocol which allows inspecting bevy state via HTTP, which really helps agents debug things. I had claude add a little wrapper that also allows injecting mouse/keyboard events and triggering a screenshot write to disk, and now claude can drive the whole game, which helps it verify things end to end.
I can't really comment on the performance. I haven't noticed any performance issues for the things I'm doing.
I have also been using LLMs (mostly claude code) to develop a game with Rust and Bevy, and it seems to work very well. The strictness of rust seems to really help them get the code right, and the ECS architecture seems to make it easy for them to reason about how things work (because they only need to hold a few systems and components in context at a time).
makes me wonder if ECS will ever catch on outside the gaming industry. not sure if it's really the right architecture for web SAAS. Might be interesting to rewrite some big piece of software with ECS.
I think they're saying that they _had_ written the copy themselves, but were using the clanker for other tasks, and it kept going off course to "improve" the copy.
Title makes it sound like a new method of generating energy was discovered, but really the article is about using geothermal in a new location.
> The development of medium-deep (>400 m) and deep geothermal reservoirs (> 1,500 m) could be a partial solution to provide renewable heat to single buildings, residential or commercial neighbourhoods, or districts of the city of Aachen via the existing district heating network.
I think "idea" is getting overloaded here. The article isn't talking about new feature/product/tool ideas, but about what concepts to use to build those features. e.g. what data structures and algorithms to use.
So your last line agrees with the article, I think. They are saying that it's still important to curate ideas, and no longer important to read the code; the time you would have spent reading the code should be spent curating ideas.
It creates a lot of perverse incentives, and is probably a bad idea in the long run. If the govt makes more money when intel is successful, then the govt is incentivized to sabotage Intel's competitors (e.g. through tariffs, export controls, and many other powers). This distorts the free market that is (allegedly) at the center of America's success
> If your job was mostly converting one well-defined input into a well-defined output — natural language to SQL, requirements to code, ticket to PR, design spec to working component, log line to incident report, customer email to ticket — your task got compressed by an order of magnitude.
All of these inputs are rarely well-defined. that's the crux of the whole agile manifesto
I watched the video, and I think the creator of the repo might be concerned about liability. Also, the perturbed plates don't look that interesting, they just look slightly dirty