问HN：建设者与雇佣兵——这个区分有意义吗？
我注意到在我参与的团队中，有两种类型的工程师，我正在试图弄清楚这是否是真实的模式，还是仅仅是确认偏误。
- 建设者关注用户和领域问题。代码只是实现目标的手段。如果能解决真实用户的需求，他们会发布一些不完美的产品。让他们花时间在不影响用户体验的优化上？那是绝对不可能的。
- 雇佣兵则专注于技术本身。他们关心干净的架构、性能和优雅的抽象。无论业务或用户是否真的需要解决这些技术问题，他们都会深入研究。工作的质量与其影响无关。
但我不确定我是否正确地框定了这个问题。有几个问题想请教：
- 这种区分与你的经验是否相符？
- 你属于哪种类型，随着职业生涯的变化，这种类型有改变吗？
- 你如何在团队中平衡这两种思维方式？
查看原文
I have been noticing two types of engineers on teams I have worked with, and I'm trying to figure out if this is a real pattern or just confirmation bias.<p>- Builders are focused on users and the domain problem. Code is just a means to an end. They'll ship something imperfect if it unblocks a real user need. Ask them to spend time on optimizations that don't affect the user experience? Hard pass.<p>- Mercenaries are focused on the craft itself. They care about clean architecture, performance, elegant abstractions. They'll go deep on technical problems whether or not the business or users actually need it solved right now. The quality of the work matters independent of impact.<p>But I'm not confident I have this framed correctly. A few questions:<p>- Does this distinction resonate with your experience?<p>- Which type are you, and has that changed over your career?<p>- How do you balance these mindsets on a team?