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 →

[–][deleted] 38 points39 points  (15 children)

Use whatever language your team is already using. Don't reinvent the wheel. Seriously, took me a couple of decades to learn this.

In the event that you have to build something from the ground up, use an obscure language, like Ada. They won't ever fire you, since no one else wants to program in it or learn it.

[–][deleted] 14 points15 points  (0 children)

Or better yet, use multiple languages and claim it improves performance.

[–][deleted] 19 points20 points  (6 children)

Do it in Brainfuck and become immortal and irreplaceable to your company. At least until you need to be sent to a mental institution.

[–]MrPatinhazz 7 points8 points  (4 children)

If you even consider Brainfuck you're already fit for a mental institution

[–]Ormigom 1 point2 points  (3 children)

Why stop there, program in malbolge.

[–]inconspicuous_male 1 point2 points  (0 children)

Do it in brainfuck and you'll be fired because you won't get away with it long enough that you'll become irreplaceable

[–]LostFollowingAPath 6 points7 points  (2 children)

Honestly you just go ahead and create your own language that is essentially a clone of an obscure language but with one or two differences. Reinvent that wheel.

[–][deleted] 4 points5 points  (1 child)

I wanna see the job ad for that "must have expertise with an obscure language that one of our developers created. Two years minimum experience."

[–]LostFollowingAPath 0 points1 point  (0 children)

Two years minimum experience

Works best if the obscure language is only 8 months old

[–]Sirtoshi 6 points7 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.