Live data from Hacker News

So you want to be a PHP Developer?

dannynunez.com

21–30 of 66 posts

Re: So you want to be a PHP Developer?

#22
post #16
post #3

Betteridge's law of headlines strikes again!

I for one needed to Google it ( https://en.wikipedia.org/wiki/Betteridge's_law_of_headlines ): Betteridge's law of headlines is an adage that states: "Any headline which ends in a question mark can be answered by the word no."

Simply add "why" or "how" on the beginning of sentence i.e. Why you want to be PHP developer? In marketing they are calling them "open questions", the question to which you have to answer with more than just yes or no

Re: So you want to be a PHP Developer?

#23

Why would I want to be a PHP developer? :O

Because finding a job is incredibly easy. Because it pays well if you know your stuff. Because you don't have to work with people who will judge you based on something as in-significant as what programming language you decide to use.

Re: So you want to be a PHP Developer?

#25
post #12

I wouldn't recommend Zend (I find it rather resource heavy) - but rather Laravel or Symphony, CodeIgniter is also nice and extremely easy to learn - probably the lowest entry level that I can think of, but 2.0 is taking it's sweet time to come along so that's a huge downside, plus, Ellislab wants to sell the project... Regarding CMS work, I have personally found that Magento is one of the best things to specialise in…

There's a lot of money in Magento because it's so utterly horrible to work with.

Indeed, it has a steep learning curve. I have been working with Magento from day 1, and I'm still learning new things. But additionally, another main reason why it pays more, is that the client is willing to pay more + will actively pay for updates since it's not just a regular boring website, but an actual online business.

Re: So you want to be a PHP Developer?

#27
post #8

I wouldn't recommend Zend (I find it rather resource heavy) - but rather Laravel or Symphony, CodeIgniter is also nice and extremely easy to learn - probably the lowest entry level that I can think of, but 2.0 is taking it's sweet time to come along so that's a huge downside, plus, Ellislab wants to sell the project... Regarding CMS work, I have personally found that Magento is one of the best things to specialise in…

No, don't even think of learning CodeIgniter. Besides being pretty much dead (version 3 has been coming out for, what, about 2 years now?), it has terrible architecture. The superglobal singleton is just awful and will kill you slowly.

This. I don't understand why CodeIgniter gets mentioned in the same breath as Zend or Symphony, or any other fully-fledged framework. CI is, to start with, much smaller: it's tiny, the sort of thing you could knock out in a week. It also has deep-rooted architectural issues that are preventing some of the longest standing bugs being fixed (for example, take a look at the router). Lastly it's not anywhere near as modular as it purports to be, and the code and architecture quality is rather poor.

Re: So you want to be a PHP Developer?

#29
This is a rather low effort post. PHP The Right Way [1] already covers the basics of modern PHP, without turning into a laundry list.

Today the most important thing is Composer, not frameworks, especially to those who are just starting out. Learning a full framework is pointless if they just want to see the basics in action. Fabien Potencier's Create your own framework series [2] is really good for this: it shows how much you can do with just a couple of Symfony components and a front controller.

[1]: http://www.phptherightway.com/

[2]: http://fabien.potencier.org/article/53/create-your-own-frame...

Re: So you want to be a PHP Developer?

#30
If you're going down the Drupal route you're just as likely to need Drupal 6 - one of the challenges in this market is there is a lot of legacy work to be done, so you often have to know two or three versions of the framework.

In the "Unicorn skills" section, you're as likely to need cPanel or Plesk as pure Linux skills (although having the latter will make the former much easier). I would also say you'll probably be using SVN and not git. Lastly, add FTP and SSH to the skills you'll need.

Post reply on HN