2 ms·

But what we do is not the same as medicine, which is highly regulated and has implications for life and death. Nothing stops us from learning any new technical

But what we do is not the same as medicine, which is highly regulated and has implications for life and death. Nothing stops us from learning any new technical thing we care to.

coldtea 4y ago
>But what we do is not the same as medicine Doesn't mean it's "whatever need there is and whatever I ask you to do, and forget the role you applied for, to and was hired to do". >Nothing stops us from learning any new technical thing we care to. Nothing should stop us from focusing on the kind of programming layer/expertise we want to do, either, be it systems, backend, front-end, data science, If people WANT to change layer/role, they can do it themselves. And hopefully at a better company, where they can focus on their desired role, and aren't asked to also write front-end code when they were hired as systems engineers, or perhaps mop the floor because "you surely can learn that too, it's not like moping the floor is like medicine".
- VBprogrammer 4y ago
  I'm not the cleaner in my office but I still take my cup to the dishwasher and put my litter in the bin when I leave. I'm not sure what I'd have done in the OPs situation but it wouldn't have been going round and round in circles slowly improving my own work in isolation.
tomrod 4y ago
My thoughts: > But what we do is not the same as medicine It is extraordinarily similar from a systems aspect > which is highly regulated Some areas of software development are highly regulated, and this is an environmental constraint instead of a work methods outcome > has implications for life and death. Much of software has implications for life and death, especially at firmware level or medical device & AI/ML. If your experience is only with FAANG or web front ends, then sure, this statement has teeth. But software automates processes, and a lot of processes can end in death, either by intent (military) or accident (health, law enforcement, manufacturing)

But what we do is not the same as medicine, which is highly regulated and has implications for life and death. Nothing stops us from learning any new technical thing we care to.

coldtea 4y ago

>But what we do is not the same as medicine Doesn't mean it's "whatever need there is and whatever I ask you to do, and forget the role you applied for, to and was hired to do". >Nothing stops us from learning any new technical thing we care to. Nothing should stop us from focusing on the kind of programming layer/expertise we want to do, either, be it systems, backend, front-end, data science, If people WANT to change layer/role, they can do it themselves. And hopefully at a better company, where they can focus on their desired role, and aren't asked to also write front-end code when they were hired as systems engineers, or perhaps mop the floor because "you surely can learn that too, it's not like moping the floor is like medicine".

VBprogrammer 4y ago
I'm not the cleaner in my office but I still take my cup to the dishwasher and put my litter in the bin when I leave. I'm not sure what I'd have done in the OPs situation but it wouldn't have been going round and round in circles slowly improving my own work in isolation.

tomrod 4y ago

My thoughts: > But what we do is not the same as medicine It is extraordinarily similar from a systems aspect > which is highly regulated Some areas of software development are highly regulated, and this is an environmental constraint instead of a work methods outcome > has implications for life and death. Much of software has implications for life and death, especially at firmware level or medical device & AI/ML. If your experience is only with FAANG or web front ends, then sure, this statement has teeth. But software automates processes, and a lot of processes can end in death, either by intent (military) or accident (health, law enforcement, manufacturing)