←back to thread

Suffering-Oriented Programming (2012)

(nathanmarz.com)
81 points whalesalad | 1 comments | 10 Apr 25 18:11 UTC | HN request time: 0.621s | source
Show context
austin-cheney ◴[10 Apr 25 19:44 UTC] No.43647396[source]▶
I really like this but prefer to think of it in the inverse: Build new technology because you feel the pain of current alternatives.
replies(1): >>43650660 #
cryptonector ◴[11 Apr 25 05:06 UTC] No.43650660[source]▶
That's not the inverse. It's just a variant of TFA's

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

If the current alternatives are so bad that it's as if they didn't exist, then you are already at the point of wanting to build the thing you are missing.

replies(1): >>43654810 #
austin-cheney ◴[11 Apr 25 15:18 UTC] No.43654810[source]▶
No, those are very different. If the alternatives did not exist, or even if its as though they did not exist, then you are looking to produce something new for the sake or delivering any solution.

If the alternatives just suck and you realize you can do so much better then your goal is wildly different. Its not about any solution because you already know what the baseline and acceptance criteria are. Its only about not feeling the pain that other solutions provide. You are otherwise providing the same solution and just doing it in a way that's like chocolate and caviar.

replies(1): >>43654868 #
1. cryptonector ◴[11 Apr 25 15:21 UTC] No.43654868[source]▶
Either way you're taking on a big task because of the pain you were suffering, and only when some pain threshold is exceeded. That's the core of TFA. It's the same.