Rainer is a passionate software developer and loves to work with Angular and Spring. He is a trainer and consultant at AngularArchitects.io and runs ng-news, a weekly Angular newsletter.
I think there's some middle-ground there:
If the tests are quite complex then they should be provided at first, but they should be explained and not given as a black box.
If the tests are rather simple, I think some of them should be written to "get the feeling".
All in all, a great article and very interesting insight. I hope that this approach will be picked up by universities and coding bootcamps, though I don't think the academy will change their approach anytime soon.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my experience this is simply too much for beginners. They are struggling with the basic concepts like variable assignments or conditions.
Therefore I advise only to provide them with existing unit tests and make sure they are coding against them.
I think there's some middle-ground there:
If the tests are quite complex then they should be provided at first, but they should be explained and not given as a black box.
If the tests are rather simple, I think some of them should be written to "get the feeling".
All in all, a great article and very interesting insight. I hope that this approach will be picked up by universities and coding bootcamps, though I don't think the academy will change their approach anytime soon.