[Info-vax] Rust as a HS language, was: Re: Quiet?

[chris]

On 04/08/22 01:07, Arne Vajhøj wrote:
> On 4/7/2022 5:50 PM, chris wrote:
>> On 04/07/22 19:59, Dan Cross wrote:
>>> In article<t2n1o9$1fjb$1 at gioia.aioe.org>,
>>> chris<chris-nospam at tridac.net>  wrote:
>>>> I don't apologise for that. Those who are not prepared to make
>>>> the effort to learn their craft and accept substandard should
>>>> not be in the business, no excuses...
>>>
>>> I think it's odd that people reject better tooling while they
>>> assert that programmers should "make the effort to learn their
>>> craft."  Why are these things perceived as mutually exclusive?
>>> Indeed, why isn't part of learning the "craft" adopting better
>>> tooling?  And who suggested accepting substandard results?
>>>
>>> On the other hand, those who stick their collective heads in the
>>> sand and pretend that the same old techniques using the same old
>>> tools in the same old way should consider leaving the business.
>>
>> There you are again, another dig at others suggest insecurity, but
>> I digress. Fortunately, people like you don't get to decide who
>> works in the business and who doesn't.
>
> "And why beholdest thou the mote that is in thy brother's eye, but
> considerest not the beam that is in thine own eye?"
>
>> That's decided by project
>> managers and engineers who look for the right kind of experience
>> and attitude for the work they are trying to get done...
>
> Hopefully project managers are never involved in making
> decisions about tech stack as it is not a project management
> matter.
>
> Decisions about tech stack is an architecture matter and
> architects should be the primary decision makers. They
> can solicit input from software engineering to verify
> that would should work actually does work in practice.
>
> Arne
>

Nit picking semantics there. The project manager / team leader
is usually at least as technically aware and switched on as
the rest of the team. Also, "tech stack" may be initiated by
one of two people, but that is usually discussed and often
changed once it reaches peer group review. Shared responsibility
and many eyes helps build better product...

Chris