> And then there is the situation about junior engineers. There are actually two different points in there: a) you cannot trust the effort behind your junior’s code anymore, and b) seniors have no incentive left to teach juniors.
If you are bringing in juniors with the expectation that they won’t produce any value for some time then it might be better to block them from using LLMs.
Do this and you will get a better understanding of where they are in the process and they will probably learn the ropes more quickly.
> If you are bringing in juniors with the expectation that they won’t produce any value for some time then it might be better to block them from using LLMs
A) I think many companies no longer view juniors as an investment, they want them to be productive. They view juniors as "cheaper almost-seniors"
B) Blocking them from using LLMs would mean acknowledging that there is a downside to having your employees using LLMs. If they prevent your juniors from improving, what negative effect are they having on your seniors?
If you are bringing in juniors with the expectation that they won’t produce any value for some time then it might be better to block them from using LLMs.
Do this and you will get a better understanding of where they are in the process and they will probably learn the ropes more quickly.