And I think it is entirely feasible that at some point -- how far away, I don't know -- AI becomes superior to us in its appreciation of life and living.
First, it's a visual representation of the value, and it's easier to map "Slightly more to the right" than "an extra 0.7"
More importantly, all DAWs can map physical control surfaces to the on-screen knobs, and control surfaces all use knobs and sliders.
For example https://mackie.com/en/products/mixers/onyx-series/Onyx16.htm...
In the past, workers complained that automation took away their jobs. The (roughly) same amount of wealth was created but the income went to fewer individuals (the owners).
This was a valid criticism but at least they could move onto other jobs.
AI, if successful, is different. Combined with robotics[0], it makes all jobs obsolete. Regardless if the amount of wealth created will be less, the same, or greater than before, the income will only go towards the owners and everyone else will become a beggar. That is the endgame.
If you believe the endgame is different, please game it out in your head and share what you think. Don't just reject this idea without thinking about it.
[0]: And even without robotics, true AI (AGI) would obliterate such a huge percentage of jobs it would create a shock and massive unemployment.
That's not necessarily true. If you're a morning person managing other people that are not morning people but insist on having daily meetings in the morning, you're an asshole. I find meetings early in the morning sadistic and way more draining than reading the news, but I'm not the type that gets emotional about the news while I will react negatively in an early meeting at the drop of a pin. It's not about needing coffee nor did I get up on the wrong side of the bed or whatever demeaning quip you want to offer. I'm not up to speed until later in the day, and forcing me to pretend I am is just rude. This is the biggest downside to WFH where everyone can live in whatever timezone so someone's afternoon meeting is my morning rather than just scheduling the meeting where everyone is on the same schedule. It's one of the few things about working in an office I can appreciate. Definitely not to be misread as a vote for RTO.
I think you're the only one who wants that, though. They've tried that again and again and nobody uses it.
Though I can't quite put my finger on why, psychologically, I'm so less willing to fork over $3.99 to Amazon to watch a movie when I was perfectly happy to fork over that same $3.99 to Blockbuster for a physical block of plastic that I had to bring back in the same state they gave it to me.
The most pernicious, hard-to-find bugs that I've come across have all been around the business logic of an application, rather than it hitting into an error state. I'm thinking of the category where you have something like "a database is currently reporting a completed transaction against a customer, but no completed purchase item, how should it be displayed on the customer recent transactions page?". Implementing something where "a thing will appear and not crash" in those cases is one thing, but making sure that it actually makes sense as a choice given all the context of everyone elses choices everywhere else in the stack is a lot harder.
Or to take a database, something along the lines of "our query planner produces a really suboptimal plan in this edge-case".
Neither of those types of problems could ever be automatically detected, because they aren't issues of the programming reaching an error state- the issue is figuring out in the first place what "correct" actually is for you application.
Maybe I'm setting the bar too high for what a "bug" is, but I guess my point is, its one thing to fantasize about having zero bugs, its another to build software in the real world. I probably still settle for 0 run time errors though to be fair. . .
Issues around business logic are not failures of the system, the system worked to spec, the spec was not comprehensive enough and now we iterate.