I’m getting mixed messages from this. I read the thesis to be “Write code that makes customers happy instead of what makes you happy.” The rest of the article is a story about the author writing code to make himself happy, even though there are no unhappy customers. The result is happy customers.
My personal approach is “Write code that makes yourself happy as long as you are completing all work expected of you, too.” I think this article is aligned with that.
I’m getting mixed messages from this. I read the thesis to be “Write code that makes customers happy instead of what makes you happy.” The rest of the article is a story about the author writing code to make himself happy, even though there are no unhappy customers. The result is happy customers.
My personal approach is “Write code that makes yourself happy as long as you are completing all work expected of you, too.” I think this article is aligned with that.
Perhaps the lesson is “Align your happiness to those of your clients, whether they are internal or external to your organization”
looks “you don’t know what you’ve got ‘til it’s gone” hold the other way, too.
Sure, how should you know you want it, if you don’t know it. Chicken-egg paradox.
Actually it’s about short- vs. long-term benefits.