PHP Best Practices: Introduction

 

I started programming when I was about 12, did so continuously until I was 18, took a couple years off to be a kid again, and recently started programming again seriously (in professional, production, multiple-developer environments).

I have a lot of standards and ideals with programming, but there are also a lot of gaps. This “best practices” series will be my attempt to explain every facet of my programming philosophy, and hopefully start a conversation.

I think this conversation is necessary because most code we see on a daily basis is bad – real bad. It’s bloated and slow when it works at all. It’s brittle and doesn’t like to change. It probably took forever to get the initial product, but it probably needs a LOT of work – and that’s unfortunate since it’s so difficult to change.

I will probably talk a lot about unit testing and MVC. The reason you should read more is because I don’t like the way those are done now, at all; I think we can do better. The reason I want you to read more is because I know you, as a programmer, are uncomfortable with a lot of what you do. There should be a better way to do things, and I intend to discover it – with your help.

 

So, before I write my next post, a note : any methods I come up with should be general enough to port to other languages. PHP is what I’m most familiar with, but I don’t intend to be exclusive.

 

Thanks for reading.

 

This entry was posted in Coding, News. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>