> the priority should be to make them evolve toward more detachment from their work and acceptance that what they design "can" (actually will) be imperfect In

> the priority should be to make them evolve toward more detachment from their work and acceptance that what they design "can" (actually will) be imperfect In an ideal world, sure, but I've worked with enough people varying from professional-but-proud[1] to emotional-maturity-of-a-child to understand that this _shouldn't_ be prioritized, on grounds of feasibility. You may as well say "we don't need reasonable workdays, we need to teach employees to jettison their biological need for sleep". I don't think it's _impossible_ to get people to be fully detached from their code, but I think that it's only possible in fairly narrow situations (perhaps in a small, tight-knit, talented team culture). Trying to get it to work in a general context is usually much more effort (and lower chance of success) than meeting it halfway with tweaks to communication style and process. [1] To be fair, I'm quite sure I've slipped into this mode on occasion myself