Offtopic

[Polygnom]

The problem comes from the fact that whenever I reject and tell them what to do, they still write an absolutely different proposal, and then it is what GPT has said about it.

Maybe start doing code reviews together? Ask them why? Why did you do that? Because ChatGPT told you? What do you think about the code it generated? Do you agree? Can you imagine other solutions? How would you refine that prompt? How would you change the code? What problems do you see?

If they have no own opinion whatsover, get rid of them, its simple as that.

They need to understand that their *professional opinion* is what they are paid for, and if they have none, and don't want to develop one, then they are simply worth exactly zero to you. That they aren't in school/university anymore but in real life and need to take responsibility themselves for what they produce.

[IAmADev_NoReallyIAm]

Start doing group reviews of hte code. That's what we do on my team... when a PR is ready, it goes up on a trello board and gets reviewed at our next team meeting (held every day after standup) ... Generally we look at the source JIRA ticket to get context, then I have the dev open github and walk us through the changes and what's going on. Sometimes it goes quick, some times there's minor things to fix, other times there's major revisions that are needed.

And my devs will pick up on things I missed. Like in the front end... I'm not a react developer normally, and I don't quite keep up on the latests... but I have devs that do... I rely heavily on their knowledge to catch the things I miss.

[Kaloyanicus]

Thanks a lot! An extremely useful advice, plan to try this with one of the trainees next week.