> “Passion” is dismissed as a veiled expectation for unpaid overtime, and “craftsmanship” is derided as an exclusionary gatekeeping term It's the hiring proces

> “Passion” is dismissed as a veiled expectation for unpaid overtime, and “craftsmanship” is derided as an exclusionary gatekeeping term It's the hiring process and interviews etc that have broke this i.e. the companies - not the developer. When you get asked questions like: - How do you keep up with technology? - Are you passionate about the work? Or do you find what we do interesting? - Would you mind doing the extra hours on the odd occasion? There's the problem. Sure developers can be passionate or enjoy their craft, but that's their problem. When one side specifically "looks for" such traits in this way it doesn't work. Most of these questions are vague, checkboxes and doesn't do anything useful in reality. It just gets on peoples nerves and turns into why they want to avoid it. And when companies stick with legacy software with claims that there is no "business reason" to upgrade, what do they expect to be "interesting" for the developer? What passion can I have working on a EOL spaghetti codebase? So what if I keep up with technology if it can't be used in practice? I'd say developers have been jaded. Fix the real problem. Get companies to care about the craft and passion before requiring their employees to and maybe something will change.