Hacker News new | comments | show | ask | jobs | submit login

I think that even at the 90% mark, there's value in giving what I would call "craft-work feedback": the type of feedback one craftsman gives another.

First, you tell them that, from the perspective of the end-user, their craftwork is done, and nobody will notice anything wrong with it. It's shippable. It's usable. They probably won't hear one complaint, and sales will be good.

Then you point out the little things. The things that only other craftsmen will notice, but that end-users, despite not knowing to look for them, would still appreciate if you changed. The things that would take the thing from "done" to "perfect." The things that are, to most craftsmen, "just a matter of pride."

But you must finish off by reminding them that since they have a deadline (and they do, even if they call it "runway"), it's not even a matter of fixing all the little things. They don't have time to fix all the little things. Instead, it's a matter of picking the highest-impact ones they can fix in the time available, fixing those, and then shipping.

I think the key insight from such an explanation is that there are always some issues you point out that they must simply "accept": it's wrong, and now they're aware it's in there, but it's not going to get fixed, and it's going to ship like that, and everyone is going to see it (though only other craftsmen will notice it.) Tell them that they can't be paralysed by this thought: instead, they must accept it, learn from it, and do better with the next one.

Engineering, to some extent, requires mastering the art of knowing when to temporarily abandon a project in the intest of shipping. A mature engineer has gone through this cycle multiple times to the point that the "abandon to ship" concept becomes part of his/her normal process. It's far too easy to keep at it and never ship anything.

Absolutely spot on about the "craftsman advice". It's something I've really striven for, because while much of what we do requires that you just put in the time (structuring things well, designing robust systems, etc), "craftsman advice" can be used pretty much immediately.

Great insight. An analogy I've heard that echoes the same sentiment: you don't buff a diamond, you cut it.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact