If you're working under an NDA or on code that doesn't belong to you, you'll most likely need to hit up the hobbiest side of programming to build your portfolio. Sit down, plan some app that would make your life easier (or someone else's), go through the design process, and then code it to implementation. It doesn't have to be perfect, but it has to be good enough to show off your abilities. It really doesn't matter if the app already exists, you're doing this simply for the sake of self improvement and to build your portfolio. That's where open source comes in nicely. You don't need to make it a full time job, but actively contributing to a project will allow you to say "I played a good sized role in ______." "Matt Carlson" <saryon@xxxxxxxxxx> wrote in message news:740278.84425.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > So i've been meaning to start a portfolio of some code, so that when I > apply for a job, and they want code samples, I have something to show > them. Unfortunately, at this time, most of my work is inside of a much > larger application, or in code that belongs to my current employer (not a > php job, just misc. things i've made). > > What kind of things do you guys have in your portfolio's/code samples that > your provide to a potential employer? What things do you feel I should > avoid when putting this kinda of thing together? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
