A genius developer is an experienced developer whose deep knowledge of the existing system gives them high implicit status. Teams often look to this person to lead collaborative modeling because their expertise has repeatedly helped the team. section 6.2.2
That authority can narrow collaboration. Strong attachment to how the system already works makes it difficult to discuss business needs that require change, so modeling sessions become dominated by current technical details and domain experts see less value in participating. section 6.2.2
A constraint request
When asked to add a unique constraint to the email column, the developer focuses on required data cleanup and the server’s existing request flow. The discussion centers on implementation difficulty rather than the business need. section 6.2.2
Use the pattern as a prompt for reflection:
- Notice when collaborative modeling follows existing implementation details instead of exploring the domain. section 6.2.2
- Examine assumptions attached to the image of a genius, including assumptions about gender, background, and culture. section 6.2.2
