I will agree with everything except for two points.
The "stop reading code" snippet.. I think its important he continues to read code and mess around, it is what keeps passion alive and influences you. He should start building things on top of what he already doing
Another point, about "the best software is written by one person" is completely false. Any significant software project usually requires a team with good chemistry. You kind of alluded to the whole "genius programmer" myth.
I am not saying people can't write great software or build great products alone. Just that its not good to think of programming as an activity done in isolation. If not just for the fact you can get more ideas and feedback working with a team.
A lot of other stuff you said is sound advice. :-)
The "stop reading code" snippet.. I think its important he continues to read code and mess around, it is what keeps passion alive and influences you. He should start building things on top of what he already doing
Another point, about "the best software is written by one person" is completely false. Any significant software project usually requires a team with good chemistry. You kind of alluded to the whole "genius programmer" myth.
I am not saying people can't write great software or build great products alone. Just that its not good to think of programming as an activity done in isolation. If not just for the fact you can get more ideas and feedback working with a team.
A lot of other stuff you said is sound advice. :-)