> accuracy has nothing to do with political spectrum and it's not appropriate I think to conflate.
When you go to college there will be plenty of coursework on identifying and correcting for your OWN biases since they affect accuracy in EVERY discipline. Taring a scale serves exactly the same function as acknowledging you grew up with a specific way of thinking about other people.
Imagine being asked to publish 'beautiful' code for an audience comfortable with doing so themselves. On top of all the theory and practice needed to produce a complete system you're expected to develop a point of view your peers want to engage with.
Another point of view is that your people are so good that their division turns a profit under mismanagement. It costs MS negative hundred mil to keep the whole thing spun up on a bad day.
From my perspective it felt like understanding that the machine has no desires helped refine my usage.
I can ask it to be curious, and it will reply with what people think curiosity should look like, but it’s a simulation of an emotion it will never be driven by.
The ramifications become apparent when you engage in activity like cross-domain discovery.
A lot of people are working on the same thing because nobody's come up with a definition of "thing" that people agree on yet. Your project would be valuable just for adding another point of view to the conversaion.
"Based on your subscription tier and local hardware here's a list of models that fit and process definitions your biggest brain will comfortably handle."
I guess that sounds a lot like moving your evals and auto tunes to a third-party, but I don't have the time, budget, or inclination to create a system like this out of whole cloth and then keep it relevant.
I could see something that provides on-the-fly routing information being useful, but actual decision-making is too dependent on context.
In my mind one of the problems is that I'm using the term 'router' to describe something more akin to a train schedule. A list of abilities, cost, and timeframe to be used by a model capable of deconstructing its own process.
> It's a disease frequently caught by software people, for whatever reason.
It's a disease spread by math and physics profs dismissing other domains, and weirdly prevalent in an industry solely concerned with gluing together different points of view. The poor kids that don't take common core seriously never pick up the conceptual framework everything depends from and are simply unable to reason about ideas that need to be connected together.
It's a service-oriented job that attracts people who like to control other people. There are only so many upsides to a situation like that. Here's my favorite take on the subject:
> "Police business is a hell of a problem. It's a good deal like politics. It asks for the highest type of men, and there's nothing in it to attract the highest type of men. So we have to work with what we get—and we get things like this."