Hull and Minkowski operations sort of allow one to do this sort of thing, but add to the mathematical complexity in what is probably the worst-possible way....
I've had better luck telling it to use CadQuery. Here's an example where I stumbled around a bit, but was successful in creating a cat food container (Sheba Perfect Portions) dispenser
I don't think "obvious" is the right word here. It makes perfect sense when you understand it, but it's not a conclusion that most people could come to immediately without detailed, assisted study.
True, but I think there's another dimension implied: how many devs are left that understand the code? Being able to start at zero is a fascinating surprise (compared to five years ago).
At least with a person, you can say that there's one person in your org that understands the code after they write it and submit it for review.
Maybe they stick around for a while, maybe they move on to another job, but they were THERE at some point. They have a name. You can ask them questions about what they did. And hey, they still exist in the real world too, so you can get in touch with them even after they leave if you need to.
AI powered development is like a guy shows up, gets hired for 90 seconds, writes part of a feature, and dies instantly once the code hits the screen.
a comment I cannot stop thinking about is "we need to start thinking about production as throw away" Which is a wild thought to think about when I think about on my career. We had so many dbs or servers that we couldn't touch because they were a special snowflake
Well whatever the zero means, it can't be the number of days that the bug has been present, generally. It should be expected that most zero-days concern a bug with a non-zero previous lifespan.
It's not really a good thing for technical discussion and support topics though. Information that others might hope to find by searching the web is no longer discoverable that way.
reply