282 karma · joined November 21, 2024
The resulting SIMD being illegible isn't an issue in my eyes, assembly isn't a language known for it's readability in general. If you want to really understand what the assembly is doing, ask your LLM to whip up a visualization and explanation tailored to your input data where you can see how each operation leads you to the final result.
Most robots have at least three motors, two drive sides and a weapon motor. The trick to getting away with one is integrating an impactor into the chassis of your bot, using the single wheel to spin up to ~3k RPM, then by tracking the rotation angle of the bot as it spins, you speed up a little while the wheel is pointing where you want to go, and slow it down a little when it's pointing the other direction.
Once the political climate is polarized enough, choosing to not engage in the discussion about how evil the other team is will get you lumped right in, because if the other team really is evil and you don't care, then you must be pretty bad yourself.
The "Oh, but it's your civic duty to improve your community/state/nation (which obviously means voting the way I want you to, not the way the other half the country wants you to)" tries to frame political engagement as some moral good, but if they redirected the time and energy from political engagement to working at McDonalds and funding charity with the paycheck they would have 1000x the impact, even if you assume there is a Good and Evil team and they are on the Good team.
If you just need to tweak the dimensions in the script, or are satisfied with describing the changes to the LLM and having it modify the script, there isn't much difference in practice between a generated OpenSCAD script and a Blender python script.
I'll have to add this to my backlog of experiments to try when I have unused tokens near a reset...
[1]: https://www.independent.co.uk/news/world/americas/woman-fine...
The TFR (which made it illegal to fly a drone within a bubble 1000 feet high and 3000 feet radius of a mobile asset) has been replaced by a NOTAM that basically says flying near them in a way that poses a credible safety or security threat means they can sieze or destroy your drone. I'd say this is the better resolution, and to me represents a "genuine change of heart" by the FAA, finding a way to serve the safety purpose of the TFR without overstepping.
It seems intuitive that continuing a correct output sequence is easier than the "discontinuity" of jumping from the input prompt to the output sequence.