IMO, you need to be a domain expert in order to produce something ergonomic, easy to use. You (or the team you're part of) have to understand the topic and users extremely well. There's no catch-all design, not even a process that covers more than the most mundane cases.
But inspiration is a fickle thing. If you're going to build something, you might as well be inspired by terminal-style interaction, but it can't be the goal.
> If you're going to build something, you might as well be inspired by terminal-style interaction, but it can't be the goal.
100% agree. I believe that if we do replace the terminal, the end result will not be that much different - keyboard first, power users first, APIs that are simple to consume, platform-agnostic. What would make the key differences is letting go of 50 years of accumulated technical debt, that continues to hold back the UX - aka the ergonomics and ease of use.
> IMO, you need to be a domain expert [...]. You (or the team you're part of) have to understand the topic and users extremely well.
"Sometimes Ordis likes to assume he knows nothing. Nobody can learn what they think they already know."
But inspiration is a fickle thing. If you're going to build something, you might as well be inspired by terminal-style interaction, but it can't be the goal.