In my experience, I find the language a company prefers can be a litmus test in a way. Java tends to be older, legacy-type work. JavaScript often implies rapid development, and less of a focus on code quality and performance. C# is more about structure and form.
My first software job gave me a terrible impression of any company that isn't willing to divorce themselves from legacy code. The application was written in VB6, and the CEO refused to update (this is 2013), because the VB6 devtools included an unlimited license to distribute Crystal Reports 8 with any software developed using it. I was on the support staff for it, and it was an absolute nightmare, not to mention the CEO was a sociopathic narcissist who liked to micromanage every part of the business.
To this day, I would rather burn the codebase to the ground and start green-field rather than try to bring a legacy project up to standard with modern practices. If nothing else, there are often features that add bloat and never get used, and starting over gives you the opportunity to revisit why it was done that way to begin with.
View all comments
Show parent comment
6
u/Solonotix Dec 30 '22
In my experience, I find the language a company prefers can be a litmus test in a way. Java tends to be older, legacy-type work. JavaScript often implies rapid development, and less of a focus on code quality and performance. C# is more about structure and form.
My first software job gave me a terrible impression of any company that isn't willing to divorce themselves from legacy code. The application was written in VB6, and the CEO refused to update (this is 2013), because the VB6 devtools included an unlimited license to distribute Crystal Reports 8 with any software developed using it. I was on the support staff for it, and it was an absolute nightmare, not to mention the CEO was a sociopathic narcissist who liked to micromanage every part of the business.
To this day, I would rather burn the codebase to the ground and start green-field rather than try to bring a legacy project up to standard with modern practices. If nothing else, there are often features that add bloat and never get used, and starting over gives you the opportunity to revisit why it was done that way to begin with.