On 26/02/2019 01:02, Ahem A Rivet's Shot wrote:
> On Mon, 25 Feb 2019 19:20:50 +0200
> Wouter Verhelst  wrote:
>
>> On 25/02/2019 17:05, Ahem A Rivet's Shot wrote:
>>>  Q: Which is the right language to program professionally
>>>  A: The one your employer tells you to use
>>
>> Actually, if that happens, either convince them otherwise or quit.
>>
>> Q: Which is the right language to program professionally?
>> A: The one you're fluent in and that seems a good fit for the task at
>> hand.
>
>  If you're not fluent in the language of choice at your place of
> employment then you are either in the wrong place

Yes, that was my point.

> or you have some learning
> to do.

If you're starting a job and *then* start learning the language, you're
wasting your employer's time.

>> If you've got a job to do, it doesn't really help if you need to learn
>> the language first.
>
>  If there's an established code base and in-house expertise in a
> language then you need a *damn* good reason to use anything else.

Sure.

But if there's an established code base and in-house expertise and it's
so far away from what you understand that you have to learn the language
first, you're not in the right place to begin with, is my point.

> Making
> everybody else learn your favourite language will not go down well even
> when there is a good reason.

Right.

And not knowing the language that's in use locally when you begin the
job seems like a waste of everyone's time.

If you see a job posting for "C programmer" and you come along and say
"I'm not really a C programmer, but I've been doing a lot of BASIC these
past few years so I'm definitely a programmer", then you're not doing it
right...

--- SoupGate-Win32 v1.05