Name: プログラミング言語の選び方（技術スタックのために (How to choose a programming language (for your tech stack))
Uploaded: 2021-01-14T10:49:17.000Z
Duration: 10 min 28 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

Hey, welcome back to another episode of the tech lead.

I am the tackle it and I am the tech lead.

This is coffee time with the tech lead and this is Sonny that dog.

Why don't we talk about which programming language you should learn?

For example, let's pretend that you're currently programming in Python and now you're thinking maybe it's time to add the new language to the text back.

You know, maybe Ruby on rails is looking pretty cool.

Let's ask Allah hosko and threw in er lane and elixir to Why not?

Personally, for me, since I've been learning Japanese, we're gonna throw Japanese into I think it be pretty need to just start programming and Japanese.

I find that very it's that very useful for myself, and it be pretty neat to all.

The comments will be in Japanese and anybody who wants to contribute to that portion of the code base.

I might also throw in some Chinese, Spanish and French, and we can start programming that, too.

I'm sure some developers would really enjoy these languages.

And we may even get some communities like we may be able to build up a Latin program re language group and everybody.

There would just be very enthusiastic Latin programmers.

They'd be programming and picked Latin or something like that.

This video, by the way, is sponsored by myself.

Now, I know I love you guys think that this is a joke?

Amazing value, tons of videos, Tons of great content.

I don't know why nobody has bought this yet.

Take out your wallet, pick up your credit card and go buy my stuff right now.

Do it now and I will wait for you to do it because we're not even going to continue this video until you finish your purchase.

So I would just sit here and I will wait.

And if you don't want to pay, then you can just stop watching this video right now.

But if you want to continue watching this video, then where you want to do is press the pause button right now and take out your credit card and finish the purchase by my stuff.

And then you can unpack the video, and I will wait for you to do that.

Anyway, look, I was just joking about that.

I'm not going the way and you don't need to stop the video right now.

Go ahead and washing the rest of this video.

A lot of times I see developers motivated by the wrong things and their priorities are completely messed up.

They're going to go and say that they want to start programming in list because they think it's very clean.

Be the full functional language they think that program re languages should be the clarity instead of imperative.

They're going to start adding this whole new programming paradigm into the mix.

And some programmers are going to be motivated by puzzles, challenges.

Maybe they're already programming an objective C.

Everyone thinks if the school they're going to start adding shift into the mix, they want to learn that they think it's neat.

And that's really not the right way to go about this thing.

You want to do everything in your power to avoid adding new programming languages to your mix.

The avoid adding new programming paradigms because that's just going to add a bunch more complexity that you don't need.

If you really must add a new language to your text act, it should be for a clear business need, not simply because it's some syntactic sugar, kind of like how it looks a little bit better.

That seems a little bit need, er, maybe it's a little hyped up.

Maybe you feel that says you're the developer should be up to you.

Your choice to implement that however you choose.

And a lot of people want to say to developers that the developer has the freedom to implement their code, however, where they like and they have the freedom to choose their technologies.

I was saying, though you don't have to free them to use any technology you want.

And if you do want to introduce a brand new technology, you better write up a really good business need.

Now, let me explain why the first thing is about developer ramp up.

You won't make sure that everybody in your team now or in the potential future can easily contribute to any part of your code base.

If you have a certain portion of the code base that is written in some obscure, strange, crazy language that only one guy on your team really knows how to do, then that's just going to cause a whole bunch of maintain ability issues further down in the future.

For example, if you were to look at companies like Twitter, GMO Arlington, they were using scholar just because it seemed like a cool hot thing at the time.

Now they've been pulling back on scholar and getting rid of that and comforting and back to just standards job.

Oh, simply because there's a lot of overhead in having this additional language.

You got the higher specific people to do it.

Other people can't contribute to that portion of the code.

All the tooling, the lynchers, the editors.

I think that if you were to examine a lot of these languages, that only adds syntactic sugar.

But don't add anything additional beyond that.

While these languages didn't do very well.

If you look at, for example, coffee script, which compiled down into Java script and they're essentially just made Java script a little bit prettier, a little bit nicer to write, there was no really additional business need for this thing.

Coffee script eventually died out because everybody already knows standard vanilla JavaScript and that you want to tell people that they have to learn this additional framework, this additional language.

On top of that, it's just going to be harder to get people to use that and either way you're probably going to be using standard JavaScript and other places in your coat.

Sometimes I'll see people programming and say Java, and then job is a very imperative programming language.

And then they say they want to add in a new functional language like, say, closure.

On top of that And what you really get is you just get the worst of both worlds, where you have both imperative and functional programming in there at the same time.

字幕リスト動画再生

プログラミング言語の選び方（技術スタックのために (How to choose a programming language (for your tech stack))

stuff

episode

bunch

pattern