A cautionary warning about AI I'm starting to use is, "make sure you aren't taking a forklift to the gym". Getting heavy objects of the ground is vastly easier with mechanical assistance, but doing so completely misses the point of lifting weights.
A work related example I have is using AI to generate project plans. LLMs can probably generate an ok project plan for straightforward projects with plenty of examples to be trained on. But perhaps the most important value of generating a plan is the thinking that goes into it. Considering alternatives, likely failures, unlikely failures, etc. In generating the plan you are starting to practice dealing with problem that would come up while implementing it. The knowledge in your head is more valuable than the document produced. The document is just a summary of all the thinking you have done. Essentially a collection of mnemonics. Many details in your head will never make it into the formal plan, but will be needed during implementation.
I'm curious how you are using 3-D printing for an electric motor. Most of the key components, steel laminations, copper windings, magnets, commutator and brushes (if you are going old school :-) ) don't lend themselves to 3-D printing. I just see some mounting hardware being usefully printed.
I actually did this a lot when I was designing electric motors. One detail the original article didn't note, is the 39th root of 92 is very close to the 6th root of 2, off by half a percent. This makes scaling for voltage changes simple. Going from US 120V to European 240V? Go up three wire gauges and double the number of turn.
In practice, it was not quite that simple, because of the half percent error, and wire insulation doesn't follow the same scaling pattern, but it was still quite handy, and much less trouble than metric, where you constantly had to dig out the wire gauge chart.
The classic example of this is ultramarine blue in the Renaissance. Typically cost three times its weight in gold. Painters often had to have their patrons supply the ultramarine if they wanted blue in their painting. Having a very blue painting was naturally a status symbol.
I wonder what the direction of causation is. Perhaps the issue is not the cool, thoughtful, and kind are pushed out of the forums, but they are successful in engaging people on a personal level and are less motivated to go public. The obnoxious, however, however tend to get avoided on the personal level and find it easier to get an audience in a public forum.
A while back as I was meandering through my history readings, I noticed that most of the philosophers, sages, and artists of ancient Athens weren't from Athens. I didn't actually follow that up with a study to confirm it, but I can't help but wonder if there is some deep truth hidden here.
I sculpt in stone as a hobby. I'd heard that quote, or variations of it, before I started, and just regarded it as a clever quip artists make. Not really a reflection of the process of carving, which would be much more detailed and painstaking. I was surprised to discover just how true, for me anyway, that quote is.
Well, he notes in the linked talk that "use strict;" and "use warnings;" will be the default in Perl 6. The fact that your goal is to Huffman encode the language design doesn't mean you'll always succeed. Things change over time. Initially, 15 or so years ago when Perl 5 came out, use strict was a new idea and rarely used. Over time the culture encouraged people to use it pretty much always. The Huffman encoding was right at first, but usage has changed. Changing the language to reflect currently usage is hard if you want to preserve backward compatibility, though.
To your last question, convenience. Being able to carry around in a single 10 oz device an entire library is quite handy for those of us who don't know what we want to read. Or anticipate wanting to read several books on a trip. I don't have one, and looking at the selection on the Kindle Store, I'm not sure I'm going to get one yet, but I expect I will get one eventually.
And interestingly, Apple isn't selling synchronization. They are selling products that use it, but only mention in passing the synchronization. Synchronization isn't a product, it is something you need for certain products.
A work related example I have is using AI to generate project plans. LLMs can probably generate an ok project plan for straightforward projects with plenty of examples to be trained on. But perhaps the most important value of generating a plan is the thinking that goes into it. Considering alternatives, likely failures, unlikely failures, etc. In generating the plan you are starting to practice dealing with problem that would come up while implementing it. The knowledge in your head is more valuable than the document produced. The document is just a summary of all the thinking you have done. Essentially a collection of mnemonics. Many details in your head will never make it into the formal plan, but will be needed during implementation.