I would argue that a good process always has a good self correction mechanism built in. This way, the work done by a "low quality" software developer (this includes almost all of us at some point in time), is always taken into account by the process.
I had quiet a ride myself with that topic. For years my opinion was, that I dont want to, as the auther here suggests as well, go with tdd as long as I dont know exactly what I need. Than I switched over and used tdd for everything with a more regid (interface) design upfront. Nowadays I use tdd from the integration side and only add unit tests later or case by case when I think its usefull. A really good ressource is "Growing Object-Oriented Software, Guided by Tests"
I would go a step further and dont let juniors use LLMs for code generation. The purpose and your role as a junior is to not only work but also to learn. When using genrated code, you miss a lot of opportunities to do so. Of course you could learn of some other methods or stuff from the frameworks you are using but imho thats not that big of an advantage.
Today, if someone uses LLMs for code generation, he/she will probably question the generated code and will put his own judgement above it. I am curious how fast that will change, especially for juniors. When will they start to question their own judgement and just go with the generated code becuase its "more safe"?
Yeah, kind of like that. What would be needed to get curated are the facts. Who could do it, would be the author of the original article. Maybe the author just needs to flag the wrong facts. In my, obviously very well minded view, an author has a big interest that first: his scientific article is correct - you get real bad reputation if your science is provable wrong - and that the facts others get out of it, are also correct. Of course, highly positive view :)
I kind of like your idea but in my head I always bounce back to "Is that a problem technology can or should solve?" IMHO the underlying problem is that people dont care that much anymore for each other, especially strangers. And the reason for that is, that in our society, we are not at all dependent on our surroundings. You can be perfectly fine without knowing your neighbors for example. If you dont have any sugar or salt to cook something, you can go to a close by store, order it or just order the cooked meal. You dont go to your neighbor and ask for a little bit of sugar or salt (if you ask for sugar, you probably get insulted because how bad sugar is - little joke :D ). So I guess, the only thing that truly work is to build communities that consists of interdependent people. Just my take one it :)
I am in germany, so by far not the same situation as in other areas of the world. If I would get such an assignment myself and I have the feeling that this will help the company and also me to verify, if it is a fit, I will do that 1 to 3 hour task very happily.
We did a lot of these assignments and no one assumed that they will be hired if they complete it. Its about how you communicate your intent. I always told the candidates, that the goal of the task is 1. to see some code and if some really basic stuff is on point and 2. that you can argue with someone about his or her code.
I myself just get to drink some water. If its possible I would highly recommend getting some sunlight right at the start of your day and what also helped me in the past (I know, sounds a bit strange) is to just tidy up your bed.
What is it, that sparks your interest in industrial automation?
I would recommend on focusing on the stuff you want to instead of focusing what you dont want to do. So dont think about "I dont want to stay in ML" but for example more about "I want to see a physical occurence of what I contributed to"