Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Bad code in all languages looks like crap. PHP just makes it easy for you to write such and provides visual clues when you have. </p> <p>The general recommendation is : <strong>learn php before using frameworks</strong>.</p> <p>They all are flawed so , you might learn bad practices from them. Plus, you would be placing all your eggs in single basket - bad long term strategy, especially if you are gonna work in php side of development.</p> <p>When you have learned php, try to make <em>your own php framework</em>. This is almost as a rite of passage. You cannot call yourself a "php developer" with a straight face if you have not written at least 3 of them. That would give you at least some understanding of what you want in a php framework.</p> <p>Oh .. and stay away from framework CakePHP and CodeIgniter which others will no doubt advertise. They are horrible, filled with bad practices. If you <em>must</em> choose a framework, then look at Symfony2 or Kohana (with huge reservations). They both have flaws , but at least they have heard about some of "best practices". Bottom line is : <strong>all php frameworks are bad. And some are worse then others</strong>.</p> <p>And learn difference between classical MVC , Model2 MVC and MVP. Most of php frameworks are willfully ignoring the distinction.</p> <p>So .. in conclusion, some thing you should learn about:</p> <ul> <li>writing a proper Model2 MVC</li> <li>Law of Demeter</li> <li>SOLID principles</li> <li>what is global state and why it's bad</li> <li>Dependency Injection</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload