Interesting point!

Suffering-oriented programming can be summarized like so: don't build technology unless you feel the pain of not having it.

The claimed benefits are:

• you know the problem well enough to develop a solution, because you had to suffer through the problem,
• you only work on things that are important.

Definitely seems like a good way to start working on something, but I feel it'll fall short in situations where you need a compelling vision: you don't know yet how "good" looks like and the only way to find out is to do something.