Ryan is an engineer in the Sacramento Area with a focus in Python, Ruby, and Rust. Bash/Python Exercism mentor. Coding, physics, calculus, music, woodworking. Looking for work!
That sounds like an awesome way of doing it and incorporating practical things like testing and documentation! Is the apprentice already comfortable with the command-line/running tests or are you planning on covering that first?
That's the thing I've had trouble figuring out: I want to teach important things like version control, testing, etc. as early as possible, but how early is too early? I also don't want to scare the student with all of that stuff before they've gotten comfortable with basic coding concepts and gotten all fired up about it.
Anyways, you should definitely do a follow up and let us know how it goes and what you learn! :)
It is never too early i think you should just limited the things that you throw at them ;)
In case of my apprentice the project README has everything needed to install it and run the test suite described. So no googling should be necessary. As this is the first time i have tried this approach i took approximately 1 hour to get it up and running on his machine.
I explained the things i was doing and limited the information i was providing so that it was (at least in my opinion) manageable to comprehend. I will definitely keep you posted on how that experiment went.
Edit: No he is not comfortable with the cli yet... but i promised him the terminal will soon be his go to weapon for a lot of stuff ;)
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.
That sounds like an awesome way of doing it and incorporating practical things like testing and documentation! Is the apprentice already comfortable with the command-line/running tests or are you planning on covering that first?
That's the thing I've had trouble figuring out: I want to teach important things like version control, testing, etc. as early as possible, but how early is too early? I also don't want to scare the student with all of that stuff before they've gotten comfortable with basic coding concepts and gotten all fired up about it.
Anyways, you should definitely do a follow up and let us know how it goes and what you learn! :)
It is never too early i think you should just limited the things that you throw at them ;)
In case of my apprentice the project README has everything needed to install it and run the test suite described. So no googling should be necessary. As this is the first time i have tried this approach i took approximately 1 hour to get it up and running on his machine.
I explained the things i was doing and limited the information i was providing so that it was (at least in my opinion) manageable to comprehend. I will definitely keep you posted on how that experiment went.
Edit: No he is not comfortable with the cli yet... but i promised him the terminal will soon be his go to weapon for a lot of stuff ;)