If you can get paid for it, definitely.

You should read the basic docs for your language first, though. Find out what people consider the book and study it, then take on that project in bitesize chunks with tangible goals. See if you can refactor 5% of the functionality and still have a working robot. Then 10%. If you plan to flip a switch and go from 0 to 100 on the job you're setting yourself up for a forever project and ultimately failure

We use the big sloppy category "fish" to describe all kinds of creatures under the sea. It's like if we bundled together all the chimps and certain kinds of birds and maybe one mushroom and decided those were all called arbs because they like to live in trees. It's a useful word in the real world, but the category doesn't map cleanly to any evolutionary branch

I assume paraphyletic is a short way of saying basically the thing I just did: "there is a single fish branch if you're okay with a bunch of non-fish in it"

I was hoping people would search and find my favorite podcast. Obvs there is such a thing as a fish; for the sake of accuracy it's probably better to say for our taxonomy there is no branch that contains all the creatures we commonly call fish while also omitting every creatures we don't call a fish.

"There's no such thing as a fish"

Corvids (for example) have a variety of bright and vibrant splashes all over their body; those colors just aren't in the human visual spectrum.

First I think we'll see QaaS. I think we'll see that regardless of its potential for consumer applications, but that's where the early building and testing for those would happen.

More realistic to imagine a conventional machine with some quantum capabilities