[ijidak]

But is it an informed opinion?

Every human has an opinion on practically everything. But has that human put in the effort to justify pushing that specific opinion?

In this case, is the opinionated engineer humble enough to realize that using software in their day to day life does not equal using software in our customer's context?

[rcfox]

Ultimately, you need to decide who your target user is. Do you want to cater to the lowest common denominator, or do you want to want to make something power users can customize to fit their workflow?

Neither answer is necessarily wrong, you just need to make a choice.

[AnthonyMouse]

> you just need to make a choice.

This fallacy is at the heart of the failure of modern software.

Making things work for the median user is almost entirely about defaults and intuitiveness. If everybody is sending messages all the time, there should be a conspicuous button for sending messages.

Making things work for power users is about allowing those defaults to be changed. It's fine if this is five deep in a menu somewhere. It's fine if there is an option for "advanced mode" that opens up a bunch of menus that are otherwise hidden. It's fine if this requires you to write your own filter rules etc., as long as that's available. What's not fine is to make the limited interface the only interface.

Simple things should be easy and complex things should be possible.

[koliber]

> Simple things should be easy and complex things should be possible.

I love this.

Building on this thought: When you are starting to build something, you have very limited resources. Focus only on making simple things easy and forget everything else. Once you have product market fit expand into making complex things possible. This applies to 90% of all products.

[thfuran]

Those goals are far less at odds than you seem to be implying.

[gattilorenz]

One of UX principles is exactly trying to do both.

My mom can use gmail, but she doesn’t even know about its hotkeys and accelerators, or Labs and whatnot

[sillywabbit]

If I use the product, I'd expect that feedback to get the same weight as any other customer. And not be dismissed because it came from a 'technical' person.

[spacecadet]

Using? Are you paying?

[sillywabbit]

If you're building a website that is accessible to the public at no cost, I don't see the distinction.

[spacecadet]

The issue is that software engineers most often strike a balance between passive aggressive and overly opinionated... Its a shit mix if you ask me- very frustrating personality to work with.