Home > Archive > PHP DB > April 2007 > Re: [PHP-DB] php portfolio
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PHP-DB] php portfolio
|
|
| Matt Anderton 2007-04-19, 7:57 am |
| awesome guys. thanks a lot. one thing I think I DO have going for me --
true I have only flown solo, never worked on a team, but my current project
was designed entirely to someone else's specs. I knew there would be lots
of changes as it went along and I think I did a decent job of working in
some basic OOP so I would only have to make changes once.
I guess what I still don't get is how do I go about "exposing" the code for
it? it is a live web site -- I don't want the average visitor to see chunks
of code all over the place. do I put up a separate copy on a separate
website? point the employer to the real deal first, then give him a link to
a "behind the scenes" version? and then what? just throw in "<pre>" tags
-- "this is how I did this part"?
~ matt
On 4/19/07, bedul <landavia81@gmail.com> wrote:
>
> nope.. nothing dumb on your question.
> ----- Original Message -----
> From: "Matt Anderton" <manderton@gmail.com>
> To: <php-db@lists.php.net>
> Sent: Thursday, April 19, 2007 8:49 AM
> Subject: [PHP-DB] php portfolio
>
>
> if
> working
> well the style of your code make how good you are...
> but remember.. if you work alone.. that's no problem.. the problem is when
> u
> work on a team
> -----------------------------------------
> from
> like
> an
> just
> get
> a
> a
> my suggestion was.. to improve your skill.. U have to be complained and
> meet
> problem during your programing. more problem will improve your prog skill.
> but don't stress because of it
>
>
>
| |
|
| Matt Anderton wrote:
> awesome guys. thanks a lot. one thing I think I DO have going for me --
> true I have only flown solo, never worked on a team, but my current project
> was designed entirely to someone else's specs. I knew there would be lots
> of changes as it went along and I think I did a decent job of working in
> some basic OOP so I would only have to make changes once.
>
> I guess what I still don't get is how do I go about "exposing" the code for
> it? it is a live web site -- I don't want the average visitor to see
> chunks
> of code all over the place. do I put up a separate copy on a separate
> website? point the employer to the real deal first, then give him a
> link to
> a "behind the scenes" version? and then what? just throw in "<pre>" tags
> -- "this is how I did this part"?
Just email him a file or two, much easier :)
--
Postgresql & php tutorials
http://www.designmagick.com/
|
|
|
|
|