Sharp: Closing a door

> We can all feel wonderful about ourselves, and put out a worthless project.

You can keep repeating that to yourself louder and louder but it still isn't true, being an a**hole to people does not bring the best work from people, or attract the most competent people, what brings quality is competent people who are invested in a goal, projects with a**holes operate in spite the productivity drain, drama and distraction from the goal they cause and not because of it. It is in fact possible to be highly critical and demand quality without either being an a**hole or being crippled with an inability to give feedback due to fear of other peoples egos, it's not being an a**hole to reject a patch due to it not meeting the quality standards or pointing out the problems with a design.

> But the code comes first. It has to.

You act as if there is some absolute quantifiable rank that every other consideration is subservient to, but that is not how anything in life works, there are always multiple competing factors and trade-offs to be made between them, and every priority is only the "first" priority to a point.