3 ms·

Maybe you should step back from the code and let people who do want to dig in do it??? strange you seem to not appreciate quality and definitely have a chip on

Maybe you should step back from the code and let people who do want to dig in do it??? strange you seem to not appreciate quality and definitely have a chip on your shoulder. sounds like you should maybe stay out of the code and recoup? maybe management is your calling? or you have the personality for it? many projects need people who actually care about improving the product performance because they realise the magnitude of benefits that come not just technically, but across the board. people tend to be happier when they get more done with less effort.

ravenstine 3y ago
Strange that you think I have a chip on my shoulder. I'm far from having a chip on my shoulder, actually. I enjoy writing software and my career is good (despite my criticisms of the field). I'm simply pushing back on the idea that software developers need to be passionate, and am pointing out that the word "passion" can be used against developers. When you hear the word "passion" or any positive sounding word or phrase emitted from the mouth of a business, you have to remember that a business has incentives that are not necessarily in the favor of the individual. > many projects need people who actually care about improving the product performance I object to the idea that this requires passion. A person who is not passionate can still be competent at their work and solve problems like product performance. It just doesn't mean that they're going to care as much about things that satisfy developers but don't actually improve the end product, like toolchains, design patterns, the latest and greatest frameworks and transpilers, the "correct" way to do OOP, etc. > people tend to be happier when they get more done with less effort. That is true, but it doesn't necessarily follow that a team of passionate developers equates to less development effort. It certainly can, but it's not a guarantee. If you get people who are so passionate that they must die on every hill when it comes to a the team not agreeing over something as simple as tabs-vs-spaces (just an example), that can result in more effort that an individual developer needs to make in order for their code to be approved. Developers who care to the point that every rule needs to be carried out to a tee, even when it sacrifices code clarity and developer happiness, can make everyone including themselves miserable. That's the point I was attempting to make, not that developers should work hard a few years and then kick back and stop caring at all, like a certain other individual in this thread (not you btw) believes. > maybe management is your calling? Good heavens, no. lol But the suggestion is appreciated.

ravenstine 3y ago

Strange that you think I have a chip on my shoulder. I'm far from having a chip on my shoulder, actually. I enjoy writing software and my career is good (despite my criticisms of the field). I'm simply pushing back on the idea that software developers need to be passionate, and am pointing out that the word "passion" can be used against developers. When you hear the word "passion" or any positive sounding word or phrase emitted from the mouth of a business, you have to remember that a business has incentives that are not necessarily in the favor of the individual. > many projects need people who actually care about improving the product performance I object to the idea that this requires passion. A person who is not passionate can still be competent at their work and solve problems like product performance. It just doesn't mean that they're going to care as much about things that satisfy developers but don't actually improve the end product, like toolchains, design patterns, the latest and greatest frameworks and transpilers, the "correct" way to do OOP, etc. > people tend to be happier when they get more done with less effort. That is true, but it doesn't necessarily follow that a team of passionate developers equates to less development effort. It certainly can, but it's not a guarantee. If you get people who are so passionate that they must die on every hill when it comes to a the team not agreeing over something as simple as tabs-vs-spaces (just an example), that can result in more effort that an individual developer needs to make in order for their code to be approved. Developers who care to the point that every rule needs to be carried out to a tee, even when it sacrifices code clarity and developer happiness, can make everyone including themselves miserable. That's the point I was attempting to make, not that developers should work hard a few years and then kick back and stop caring at all, like a certain other individual in this thread (not you btw) believes. > maybe management is your calling? Good heavens, no. lol But the suggestion is appreciated.