I know what you're saying about their perspective, but the real equation does include the workers. One possible result of being ignorant of that fact is there could be blood on the streets.
I'm not sure that "a majority of American voters selected them" is true. Gerrymandering and other corrupting influences are a serious problem in America.
That's not what's happening. Using your analogy, you're reading the book, remembering it, and then making N more books (maybe for commercial purposes) by using what you remembered to create something very similar in terms of style, prose, plot, and so on. As a result, the person who you learned from can't get a job writing anymore because their work has been commoditized. Also, they're feeling lost because the work they devoted their lives to is now awash in a sea of similar work.
Just a thought: avoiding political bias could it's own form of bias. I would think the goal is mostly to get "correct" answers based on facts, logic, and so on. If a "correct" answer can be computed (what does that mean with an LLM?), then it might be biased, but still desirable.
If others are having this issue, I deleted all forms of local storage (cookies, IndexDB, etc.) for the mail.google.com site, and that seems to have fixed the issue. It might be relevant that this happened after I upgraded Firefox.
FYI: the Linux installation script for Ollama works in the "standard" style for tooling these days:
curl https://ollama.ai/install.sh | sh
However, that script asks for root-level privileges via sudo the last time I checked. So, if you want the tool, you may want to download the script and have a look at it, or modify it depending on your needs.
If we're going to talk about construction as the metaphor, then it's done by the computer (e.g. compilation), and it's so cheap or trivial on many projects that developers will ask the computer to build the software hundreds or thousands a times a day (e.g. via test-driven development). In this metaphor, I think the developer would be more akin to a designer or architect, but where the building in question is at least partially novel. If it's not novel in product, people, process, etc., then the client could just go out and buy or use one that has already been produced. The developer wouldn't be necessary.
I think the fundamental misunderstanding is that we aren’t building a product. We are doing research and development. We are figuring out how to build something novel, otherwise the customer could just go out and buy it already. Once we’re done with discovery, the computer builds it. So, the customer is like any other who is paying for research and development. It’s not a blank check, but they should go into it without the expectation that something new will be discovered on some accurate schedule.
No one is suggesting that we just pause and that's it. The pause is to give safety researchers time to do their work. Since progress is outpacing safety research, if we don't pause, we will eventually reach the cliff without a way to protect ourselves, for better or worse.