I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
I love the car enthusiast analogy here. We don't really have easy access to American muscle here in the UK (certainly not with manual transmissions, and I couldn't bring myself to drive an automatic personally), so I prefer turbocharged Japanese cars from the 90s.
The reasons I like these cars, and the reason that I own two of them right now despite not "needing" to, mostly start with personal taste, but it would be easy for me to come up with a list of reasons why I now "need" to have them, and what I like about them over other types of cars.
I appreciate any car enthusiast no matter where their preferences lie, and although I may extoll the virtues of my favourite cars in conversation with them, I wouldn't tell them that their cars "suck" for not being the things that I like.
I think this matches up with programming languages very well in general. There's more to consider when you're talking about choosing languages at work, where other people are also directly impacted and need to be considered too, but certainly in multi-discipline communities I think this is a really good analogy. Great stuff. :-)
The analogy also works when talking non sports cars... I also own a Honda Civic (daily commute) and a Subaru Crosstrek (winter / snow trips). I wouldn't race either of them, but I'm glad I have them both.
I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
Yep, and plenty of people love their modern electric cars for different reasons again. There's plenty of room for all sorts of things, and there's definitely not a single "best" option for everyone.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I love the car enthusiast analogy here. We don't really have easy access to American muscle here in the UK (certainly not with manual transmissions, and I couldn't bring myself to drive an automatic personally), so I prefer turbocharged Japanese cars from the 90s.
The reasons I like these cars, and the reason that I own two of them right now despite not "needing" to, mostly start with personal taste, but it would be easy for me to come up with a list of reasons why I now "need" to have them, and what I like about them over other types of cars.
I appreciate any car enthusiast no matter where their preferences lie, and although I may extoll the virtues of my favourite cars in conversation with them, I wouldn't tell them that their cars "suck" for not being the things that I like.
I think this matches up with programming languages very well in general. There's more to consider when you're talking about choosing languages at work, where other people are also directly impacted and need to be considered too, but certainly in multi-discipline communities I think this is a really good analogy. Great stuff. :-)
Same, and IMO the Supra is a beautiful car...
The analogy also works when talking non sports cars... I also own a Honda Civic (daily commute) and a Subaru Crosstrek (winter / snow trips). I wouldn't race either of them, but I'm glad I have them both.
Yep, and plenty of people love their modern electric cars for different reasons again. There's plenty of room for all sorts of things, and there's definitely not a single "best" option for everyone.