Best Solution vs Right Solution

A few days ago, I read a post from a friend who was having trouble creating a Kubernetes cluster and installing some related tools on the Apple MacBook M1 due to the tool's compatibility with the ARM processor.

That left me thinking about a common and everyday need in engineering, not overanalyzing problems and providing technical solutions that must be correct and not necessarily the best. Obviously, if the solution accomplishes both purposes, great, but at some point, the "right solution" is what the customer needs, and the "best solution" is what the engineer wants.

For example, what is better? Spend millions of dollars developing a pen that could function in space, or just use a pencil??

Right, this never happen, is not true that NASA spent any money on it but is a funny fiction to example the idea, full history down here.

We, as always, could reduce the discussion to a single phrase, Best Solution vs Right Solution.

This is why is very important to understand and have a very clear idea of who is your client and to whom are you creating solutions.?

I think this is an example of when using the best thing, is not the better option. Because of course, ARM64 processors are better (arm was always a better architecture than x86). But do we really need it??

What do you prefer? Spend a weekend trying to make an, rather basic, setup of Kubernetes work, or just do the work?

Also, as customers, we need to identify when a tool could be a driver or a killer to our necessities.

In the end, it sounds like just the beginning of another OLD flame-war, or have you guys already forgotten about Macintosh PowerPC, CISC vs RISC, x86 vs Itanium?