3 ms·

Another gent who asserts that languages he likes to use are better for "senior developers" while those he doesn't are better for "junior people". Don't hire an

Another gent who asserts that languages he likes to use are better for "senior developers" while those he doesn't are better for "junior people". Don't hire anyone who makes such insulting remarks.

jondubois 8y ago
Why is it insulting? I didn't say that using the language means that you're a junior. I just said that it was designed for juniors. Just like there are adults who wear diapers, it doesn't mean that they're juniors. In fact, most of them are very senior. They just like to be on the safe side.
- PointersAreFun 8y ago
  Oh, you need dynamic typing? Why? Can’t you do without types? You need a language to hold your hands for you? I program in B, I don’t need a language, compiler or runtime to hold my hands. The CPU word is all you need, and if you can’t do with that, then you are a toddler who wears a diaper.
- GenericsMotors 8y ago
  Gents, this ^ is what "full retard" looks like.
  - jondubois 8y ago
    Sorry for the confusion, next time I will try to dumb it down further... Maybe I need to start using static type annotations to indicate sarcasm.
majewsky 8y ago
I have to side with jondubois on this one, and I don't think it's an "insulting remark" to make. According to my experience, there is clearly a spectrum of language difficulty. Go is on the one end, being easy to pick up and use productively by design, and e.g. Haskell is more on the other end, where you have to take a lot of time to learn the underlying concepts before you can use them really effectively. Languages like Haskell are clearly aimed at "senior developers" in a way that Go is not, where "senior" doesn't necessarily mean "min. X years of industry experience", but "min. X years of category theory experience". And this difference is important to keep in mind. When I work on a really difficult problem, it's probably a good idea to choose a powerful language to help me solve the problem, but it means that only sufficiently senior developers can work on the program. On the other hand, a run-of-the-mill CRUD application should probably be written in something like Go or JavaScript because it's way easier to hire developers for these languages. If I write a dumb CRUD application in Haskell, it means that my experts can probably never hand this over to junior developers. That's not a productive use of their time.

Another gent who asserts that languages he likes to use are better for "senior developers" while those he doesn't are better for "junior people". Don't hire anyone who makes such insulting remarks.

jondubois 8y ago

Why is it insulting? I didn't say that using the language means that you're a junior. I just said that it was designed for juniors. Just like there are adults who wear diapers, it doesn't mean that they're juniors. In fact, most of them are very senior. They just like to be on the safe side.

PointersAreFun 8y ago
Oh, you need dynamic typing? Why? Can’t you do without types? You need a language to hold your hands for you? I program in B, I don’t need a language, compiler or runtime to hold my hands. The CPU word is all you need, and if you can’t do with that, then you are a toddler who wears a diaper.
GenericsMotors 8y ago
Gents, this ^ is what "full retard" looks like.
- jondubois 8y ago
  Sorry for the confusion, next time I will try to dumb it down further... Maybe I need to start using static type annotations to indicate sarcasm.

majewsky 8y ago

I have to side with jondubois on this one, and I don't think it's an "insulting remark" to make. According to my experience, there is clearly a spectrum of language difficulty. Go is on the one end, being easy to pick up and use productively by design, and e.g. Haskell is more on the other end, where you have to take a lot of time to learn the underlying concepts before you can use them really effectively. Languages like Haskell are clearly aimed at "senior developers" in a way that Go is not, where "senior" doesn't necessarily mean "min. X years of industry experience", but "min. X years of category theory experience". And this difference is important to keep in mind. When I work on a really difficult problem, it's probably a good idea to choose a powerful language to help me solve the problem, but it means that only sufficiently senior developers can work on the program. On the other hand, a run-of-the-mill CRUD application should probably be written in something like Go or JavaScript because it's way easier to hire developers for these languages. If I write a dumb CRUD application in Haskell, it means that my experts can probably never hand this over to junior developers. That's not a productive use of their time.