Suffering-oriented programming?(http://nathanmarz.com/blog/suffering-oriented-programming.html)

1 points by majnun.abdurahmanov | | 6 comments
Log in to comment
dario.hamidi at [parent][reply]

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.

dario.hamidi at [parent][reply]
[hidden]
majnun.abdurahmanov at [parent][reply]

My takeaway from this article is "do not overengineer things/solutions in the beginning". Keep it simple. Just ship and iterate over, and follow YAGNI wherever possible.

dario.hamidi at [parent][reply]

The question is – at what point does it become overengineering?

I feel like we're quick to call things overengineering when they are outside of the topics which we are familiar with.

But I take the "suffering-oriented" bit: I feel the pain of not having notifications about new replies here, so that's what I'll be adding next.

majnun.abdurahmanov at [parent][reply]

Awesome. Notifications:party. Perhaps Emoji support too.

dario.hamidi at [parent][reply]

You can just type regular emoji characters, like here: 🎉

Also, notifications are live now! You can enable them here: https://orange.decode.ee/me