Hacker Newsnew | past | comments | ask | show | jobs | submit | robmay's commentslogin

You don't consider Neurodoping a form of this? https://pubmed.ncbi.nlm.nih.gov/23504390/

I agree. The tech industry prides itself on "easy UX" but in reality they make it easy to do the actions they want you as the user to do, not the actions you really want to do. They optimize for revenue, not for user happiness.


You're spot on.

It's actually not really difficult (in theory) to engineer good UX, you simply have to look at the decision tree representing the application's state space and re-balance it according to actual usage intents.

Meaning, you make the most frequent goals need fewest clicks.

Clearly, practically nobody does that. Why?


IDK though - this is how Office ended up with its ribbon. They realised Paste was the most common action so they gave it a big button right at the left side, and then cut and copy got smaller buttons next to it. And similarly they reordered all the buttons according to frequency of action.

Result? When you have an intent in mind, it's hard to find the right button! In office 2003, you could click on the "insert" menu and every item there was something that would go into your document. If you're thinking "I want to add a picture" you can click on "insert" and scan through for picture-related items. (Blender does this too). In the 2007 ribbon model it would - well that one would probably be on the default visible ribbon because it's a frequent action - but what if you want to insert a table of contents? Who knows where that button is.


In hindsight, the horrible ribbon was really the first big sign that our industry had completely lost the plot with UI design.


:-)) Yes, Microsoft Office is actually a perfect example for how not to do it and why:

What they do wrong is, how they partition the "state space" in the first place. They employ utterly absurd abstractions that fly in the face of rational usage. Then that "ribbon" nonsense observes the user stumbling though that mess and changes the arrangement on the fly, maximizing the confusion.

In other words, they have never conceptualized what it is their users actually want to do and why. Now they're "stuck" with "what users are habituated to" and each "optimization" makes things even more worse in other places.

To get a "fluid" interface right, you need to know that it makes sense only when there are distinct use cases. You then have to detect (or perhaps better: let the user decide) what use case you're in and shape the interface according to that. Making the user chase buttons certainly isn't the right way.


But now you're describing a system that looks and acts differently every time you use it.


No, then I didn't make myself clear. That's what a "ribbon" does when it's chasing a confused user.

When you have a good tool, it has a clear purpose, a well-defined domain of applicability it is optimized for. Software tends to be "multi-tool"-like and that poses problems obviously.

When you let the user choose what his purpose is and adapt the interface accordingly, that's not "different every time you use it", it acts as expected for that present use case.

It's maybe like a workbench, where you have multiple tools available in their appropriate and known positions. Each tool has its place and native interface, optimized for the narrow job it does.

Office is like a workbench that gets rearranged randomly and each tool is weird with unclear purpose and scope.


We've been building SLMs for enterprise customers for over a year, and in almost every case it's pretty easy to beat a frontier model on price and performance, so we decided to put our tech behind a broader router. Plug it in, we start with a frontier model but then constantly test on other inference configurations and start routing certain workloads to those. You can see on the "Task Explorer" page a few hundred comparisons of various models on common enterprise workloads.

It's new so, we need people to test it out and tell us what doesn't work. Appreciate any feedback you can send.


Definitely - when you consider how varied inference workloads will be, and the different ways to minimize costs - better prompting, SLMs, different chips, batching, etc, there will be tons of opportunity


Best HN comment in a long time.


Most people don't have the team and time to do heavy token efficiency engineering. But that's all we do. marketplace.neurometric.ai has a bunch of task specific small models, and we charge flat monthly fees. We bear the token risk.


Lemurian Labs is working on this https://www.lemurianlabs.com/


Don't you think Elon Musk and his influence on Twitter counts as an elite? I'd argue the elites are the most followed people on social


Fair point. I guess elites positioning themselves as downtrodden underdogs ("it's so unfair that everyone's attacking me for committing crimes and bankrupting my companies") is a great way to get support.

Everyone loves an underdog, even if it's a fake underdog.


TL;DR - There is no one size fits all, It's a massively underexplored space, and it may end up being more important than the training side of AI.


Explore Apple's Illusion of Thinking paper on your own.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: