Linked by Howard Fosdick on Fri 13th Apr 2012 20:21 UTC
Thread beginning with comment 514302
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
Loreia,
Your first two suggestions are strait forward.
"3. and finally, join a 'real' project (at work or by joining some open source community) to see what collaboration is, which standards and conventions to follow, to have your code reviewed and so on."
"After several years of experience doing number 3. you can call yourself an experienced programmer..."
This last one can be a catch-22 at times, since employers often don't want to give experience to those who don't already have it. Many employers are strict about counting only professional work experience too.
Lucky for me I have experience, but I face a different problem. The market segregates us into sub-categories like embedded programming, database programming, or web development. For me, it has been surprisingly difficult to transition my experience in one role into gainful employment in another role. Referrals for new work are more of the same.