Question on Portfoilo's

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?

This is why one should work on an open source project. Much easier to show
off legally. :-)

On Monday 09 April 2007 8:23 pm, Matt Carlson wrote:
> 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?

--
Larry Garfield AIM: LOLG42
larry@garfieldtech.com ICQ: 6817012

"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an idea,
which an individual may exclusively possess as long as he keeps it to
himself; but the moment it is divulged, it forces itself into the possession
of every one, and the receiver cannot dispossess himself of it." -- Thomas
Jefferson

Em Segunda 09 Abril 2007 22:36, Larry Garfield escreveu:
> This is why one should work on an open source project. Much easier to show
> off legally. :-)
>

You can't live for and from only open source projects...

_I_ develop web sites and show them to my clients... Well... I'm an
empoyler... =p

What about you develop your personal web log?
Later, you can develop your own personal calendar, to schelude that importante
meeting...
And going to make your own portfoilo... =]



--
Davi Vidal
davividal@siscompar.com.br
davividal@gmail.com
--

Agora com fortune:
"Al, there are plenty of good people in this newsgroup, and I would go
so far as to count myself among them. Take a moment to really ponder
why they don't come to your defence ... No, I meant REALLY ponder ...
From: Sylvain Robitaille"

On Mon, 2007-04-09 at 22:45 -0300, Davi wrote:
> Em Segunda 09 Abril 2007 22:36, Larry Garfield escreveu:

> You can't live for and from only open source projects...

Why not? I do...

--Paul


All Email originating from UWC is covered by disclaimer http://www.uwc.ac.za/portal/uwc2006/...imer/index.htm

Larry Garfield wrote:
> This is why one should work on an open source project. Much easier to show
> off legally. :-)

unfortunately we aren't all fortunate enough to work for an open source
project and earn a living, except Paul of course.



Regards,

Clive.

{No electrons were harmed in the creation, transmission or reading of
this email. However, many were excited and some may well have enjoyed
the experience.}

On Apr 10, 8:22 am, c...@rttc.co.za (clive) wrote:
> Larry Garfield wrote:
> > This is why one should work on an open source project. Much easier to show
> > off legally. :-)
>
> unfortunately we aren't all fortunate enough to work for an open source
> project and earn a living, except Paul of course.
>
> Regards,
>
> Clive.

That doesn't mean you can't do it on your own time. It doesn't take
much to browse through the "help wanted" section on sourceforge once a
month or so to see if there are any projects that you could lend your
skills to. If you find a project that sounds like you could help out,
then let the project leader know and he/she will probably be glad to
have the extra hands. No one is expecting you to commit to writing
the next great openoffice or firefox, but there are still thousands of
projects out there that are in need of help. Even if all you do is
write one function, or a fix a few bugs here and there, it's still a
nice thing to be able to mention in a job interview. Think of it as
"volunteer hours" that med students do.

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@swbell.net> wrote in message
news:740278.84425.qm@web82613.mail.mud.yahoo.com.. .
> 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?

On 4/11/07, Steve <steve@deported.net> wrote:
> 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 ______."

Think about the google Summer of Code idea, if you participated in
that, then you can add that to your portfolio ;)

Tijnema
>
> "Matt Carlson" <saryon@swbell.net> wrote in message
> news:740278.84425.qm@web82613.mail.mud.yahoo.com.. .
> > 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
>
>