|
If you're talking about a big code base, odds are it requires some set up. Make the junior developer figure out how to set it up in a development environment. If the code doesn't work, have them try to figure out why. Figuring out why something doesn't work can involve reading logs, reading and even stepping through code.
If they successfully get a system to run, there is tremendous value in knowing what it took.
|
|
|
|
|
My recommendation would be to just start doing something with the code base. Perhaps you can think of a scenario where you want to design a solution to a problem, or some others start with a simple game, or the world famous 'Hello World' app. Either way once you get started you will discover working with code from the ground level and you can add supplemental reading to help reinforce what you're doing.
"If you feel the urge to add complexity, just go home early. You ain't gonna need it." - YAGNI
modified 2-Nov-16 11:22am.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
