| ▲ | willtemperley 3 hours ago |
| If you don't understand the code, how can you know if it's good enough? I guess you could ask the model. "Yes well done, you're a visionary software engineer". |
|
| ▲ | augment_me an hour ago | parent [-] |
| Who cares if it's good enough? Send the product, if people use it, it's good enough. If not, let users debut it and give "feedback", problem solved. You then advocate to these users, make them feel important, make them your cash cows, rinse and repeat. Every team I have been on have been more successful when they gave up on the product ideals and just ensured that the customers were hooked and satisfied. |
| |
| ▲ | bigstrat2003 38 minutes ago | parent [-] | | > Who cares if it's good enough? Send the product, if people use it, it's good enough. If not, let users debut it and give "feedback", problem solved. I care, because doing a sloppy job and seeing if people will tolerate it is not acceptable engineering practice. It's not engineering at all. More pragmatically, if you do the thing you are suggesting, you won't have users for much longer. They will abandon you and go to someone who actually makes good products. | | |
| ▲ | augment_me 32 minutes ago | parent [-] | | I don't believe this in practice. I am at a FAANG-like firm, and we are just maxxing the engagement and people use the product more and more the more we serve stuff to keep them hooked using their data and behaviour. The quality of what we provide seems to matter 0, we are up about 40% issues in prod year-to-year but the users and their engagement is also growing. I think there is a small subset of technical nerd/idealists who think that quality is all that matters but they are in their own little sandbox while 97% of users are in another one. |
|
|
