PHP the Wrong Way
&gt;&gt;&gt; The wrong way: Always use a framework on top of PHP<p>I haven&#x27;t been actively working with PHP for quite some time but... From what I&#x27;ve seen, I wish many people didn&#x27;t take this advice (including the teenager me).<p>It&#x27;s similar to ORM. Often, if you don&#x27;t use one, you end up building one, a very poor one. Yes yes I know there are exceptions and all but, in general, that&#x27;s truth. Same with frameworks. If you don&#x27;t use one, you end up writing a poor one, unless all you need is a page that outputs a result of a single SQL query, or something equally trivial.<p>I&#x27;ve seen plenty of 10k+ LoC applications with home made frameworks, poorly replicating open source ones, just because.<p>&gt;&gt;&gt; In the world of Python and Ruby building websites from the ground up is tiresome because neither Python nor Ruby was originally created to build websites. As a result general purpose frameworks such as Django and Ruby on Rails quickly became popular for building websites in these languages.<p>RoR, Django became popular because it&#x27;s so simple to build basic CRUD apps, which most of the applications are. Most of the stuff is done for you. Can&#x27;t say the same about plain PHP. The author largely ignores the reasons why the mentioned frameworks became popular.<p>Yes, you could make a well engineered solution from scratch. But chances are that you will not, time constraints being one of the reasons.<p>Sorry, couldn&#x27;t read further than that.