4 ms·
> Developers should be asking themselves during the development process: "Is this feature going to excite a group of users, and do we have some statistical mech
by xwdv 5y ago
> Developers should be asking themselves during the development process: "Is this feature going to excite a group of users, and do we have some statistical mechanism to predict that excitement?"
This is such a user-facing mindset. I’d say most of the development work I do isn’t even something the user will know about and definitely not get excited about. Also, I do not care about what happens after a feature gets built, my job is not to make sure the right things are being built, it’s to make sure things are being built right. Do your job and I’ll do mine.
- chadash 5y ago> my job is not to make sure the right things are being built, it’s to make sure things are being built right If you build the right things the wrong way, then you have technical debt. If you build the wrong things the right way, then you have nothing (except maybe an aesthetically pleasant code base that won't get used?). Every developer should try to have some part in making sure the right thing is being built.
- matwood 5y ago> Every developer should try to have some part in making sure the right thing is being built. Bingo. For as much as developers hate technical debt, it seems many miss the obvious way to avoid it is to not build something at all.
- Invictus0 5y agoYou're aware this discussion is in the context of a solo founder microstartup right? There is only one person/a few people doing all the jobs.
- jimbokun 5y agoI don't know, building the wrong thing in the right way, that never gets used by anyone, sounds kind of depressing to me.
- pc86 5y agoI don't think I've ever seen a more defensive comment on HN. "User" doesn't mean the person clicking around a website. Someone is using your software, I hope?