in reply to Learning PHP

As an art director and graphic designer I always followed the advice of other professionals I admired who said "Never put anything in your portfolio that you wouldn't want to do every day. Somehow, someway that's what you will most likely be asked to do." It's the same for skills, I never liked working in Flash or Quark so I never stated them on my resume. Do I know how to work and design with them — yes, but I would be miserable working in Flash on animated banner ads for soap every day no matter how much they paid me.

What's that have to do with php? If you like it, learn it and look for projects that require php. I would strongly suggest that if you're looking to add it to your toolbox because "There's a lot of work out there for it." don't. You'll regret it. Good luck.

"...the adversities born of well-placed thoughts should be considered mercies rather than misfortunes." — Don Quixote

Replies are listed 'Best First'.
Re^2: Learning PHP
by aquarium (Curate) on Oct 20, 2010 at 22:28 UTC
    i agree but it's not always that simple. sometimes you need PHP to do 5% of a job, and the rest is LAMP or other. in which case I'd learn PHP even if it's not my thing, so i could get the job that pays the bills. you can't always have the whole cake.
    PHP is pretty old, one of the original languages to add dynamic content to html. it was not very popular until a couple of things happened: a whole lot of extensions (including lots of http and database handling) became bundled in standard PHP, and some people wrote mediawiki and drupal etc, which wikipedia and other high exposure projects exemplified. PHP also only fairly recently became part of standard install for unix and linux variants.
    perl community confusion with the version 5 to version 6 debacle, has also helped PHP proliferate in favor of perl.
    the hardest line to type correctly is: stty erase ^H
[reply]

In Section Seekers of Perl Wisdom