3 ms·
> bring in random languages Rust is hardly a random choice. You can debate its merits for some domains, but replacing C++ in most of the places that C++ is use
by fl0ki 3y ago
> bring in random languages
Rust is hardly a random choice. You can debate its merits for some domains, but replacing C++ in most of the places that C++ is used is exactly what Rust was built for and is widely recognized as doing well at.
> just because
If your engineers are pitching a technology with no more basis than "just because", I can understand dismissing them out of hand. But ask yourself if that's actually what happened, or if they gave specific reasons justifying their proposal and you dismissed them out of hand anyway.
Even if you disagree with the reasons, or agree with them but conclude they are outweighed by other arguments, either of those is totally fine, but dismissing them as "just because" is not an effective way to make technical decisions as a team.
- wredue 3y agoThey’re not “your engineers”. This is an interview for a position listing the job requirements. You go ahead an interview however you like, but generally, giving your interviewer a feeling that you plan to shake up their tech stack because you feel like it isn’t going to go well.
- Capricorn2481 3y agoWhat is this job where the position is so high up that it can make unilateral decisions on the tech stack but also needs to be punished if they know about Rust? Would you hire a team leader that didn't know what Rust was?