I believe all teaching using this mechanical approach will ultimately fail. I like the idea of testing how people think in a practical situation rather than fill them with knowledge and see what they remembered, but if the tests are fixed, then all they have to do is go to an Indian forum on how to get hired and learn by rote what the solution is. I don't have an alternative for you, though, other than a huge database of low level problems they can try to solve. Frankly, I would not feed them programming problems, but real problems that they need to solve. And make sure they need programming to solve them :)
i do believe it'll work out but i get your point regarding real world problems. He is currently doing his first issues in a real customer project. This approach wouldn't work without some practical task. But my job is to get him from 0 to productive and it is my believe that real world tasks are overwhelming if you are not quite familiar with the language and concepts behind development.
A thing that i hoped for and validated over the last weeks is, that writing the tests from the very beginning resulted in confidence in his code and it was fun to see how it evolved from "I have no idea what to test" to "hey i should also test this as well".
He won't do the code exercises full time but he will get a new code challenge from time to time.
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.
I believe all teaching using this mechanical approach will ultimately fail. I like the idea of testing how people think in a practical situation rather than fill them with knowledge and see what they remembered, but if the tests are fixed, then all they have to do is go to an Indian forum on how to get hired and learn by rote what the solution is. I don't have an alternative for you, though, other than a huge database of low level problems they can try to solve. Frankly, I would not feed them programming problems, but real problems that they need to solve. And make sure they need programming to solve them :)
Hi,
i do believe it'll work out but i get your point regarding real world problems. He is currently doing his first issues in a real customer project. This approach wouldn't work without some practical task. But my job is to get him from 0 to productive and it is my believe that real world tasks are overwhelming if you are not quite familiar with the language and concepts behind development.
A thing that i hoped for and validated over the last weeks is, that writing the tests from the very beginning resulted in confidence in his code and it was fun to see how it evolved from "I have no idea what to test" to "hey i should also test this as well".
He won't do the code exercises full time but he will get a new code challenge from time to time.