On 26/02/2019 11:41, Wouter Verhelst wrote:
> 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.

That depends very much on the situation.  If you are employed as one cog
in a large mechanism, then it may be true.  If you are one of a small
group, and there is no external reason (such as customer requirement) to
pick a given language, then you should be free to recommend other
languages if you justify them being a better choice.  It is then up to
the manager to balance your reasoning, along with things like existing
code, other employee's skills, etc., and make the decision.  But if you
are convinced that a different language is a better choice (perhaps due
to your expertise) and you don't suggest it, you are wasting your
employer's resources.

And if it turns out that you need to learn a new language, then that is
factored into the costs.  If you have learned to program, as distinct
from merely learned how to code in Java, C, or whatever, then learning a
new programming language is usually not that time consuming.  If the
project is going to run over several months, then a few weeks to get up
to speed on the language is maybe within budget.

--- SoupGate-Win32 v1.05