> the technical implementation matters not a bit
This was the hardest lesson I learnt, it doesn't matter how polished and amazing your code is, or what technologies you use, end users really don't care at all.
This was the hardest lesson I learnt, it doesn't matter how polished and amazing your code is, or what technologies you use, end users really don't care at all.
End users care about features and code quality, but not in the way developers think.
Users deeply care when their application keeps crashing (but they don't care at all when it doesn't crash)
Likewise, users care when the app is too slow, too.
And, they care about the app having all the features they want or like (even if they don't know it and can't articulate to you exactly what they want).
Users don't care how maintainable the code base is. Whether a new feature takes 2 hours or 2 weeks to make is completely irrelevant for them. Now, they care about the second orders consequences of this: an unmaintainable mess will probably never have all the features they want, or will be too buggy, etc.
But, code quality is just a lever to achieve the things that users want. It's a means to an end. If you don't pull the lever correctly, it's wasted
At the same time, if you‘re looking to create a solution to anything beyond scratching your own itch, users are key.
The job essentially becomes dealing with irrational human wants and desires when it’s quite possible that one of the reasons you went into the profession was to precisely not having to do that.