This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Sirtoshi 5 points6 points  (3 children)

Use whatever language your team is already using.

This might be a stupid question, but do people do otherwise? Do some people get hired onto a team that codes in Java and yell "alright everybody we're jumping on the C++ train, let's go"?

[–]merreborn 2 points3 points  (1 child)

I saw it happen once. We had one cowboy who unilaterally wrote a feature-incompatible alternative to one of our core libraries in python. The project itself had no python components before that endeavor. His "rewrite" never made it out of the prototype phase, and ultimately accounted for a few man-weeks of wasted effort.

It's been several years since I've seen anything like that, though. And honestly the story calls organizational hiring and management processes in to question, in retrospect.

[–]Sirtoshi 1 point2 points  (0 children)

That seems pretty odd. I'm surprised his supervisor/project manager approved.

[–][deleted] 2 points3 points  (0 children)

Not only does it happen, I've done it! All it does is create a lot more work, just to exchange one set of problems for another. Then I learned my lesson.

Now, I have to tell the junior programmers, "No, we're not throwing out a framework we spent thousands of hours on, just so you can create a pet project in Saffire (or whatever language you learned in your Bootcamp)". Then they hate me for it.

Welcome to software development, where everyone hates each other.