The SpiteShow
PHP LIBS

Listen development teams working for companies that provide code LIBs to make implementation easier for your clients: DON’T USE AUTOLOAD. What if your client uses that shit too? Should we have to modify your poorly coded LIB broken up across 60 files? If you are going to use autoload, how about you use some sort of naming convention for your files? How about instead of using autoload to crawl entire directories (60 files!) looking for files that match a string you pass autoload, you just require the files the old way?

Also, let’s not leave white space after your closing ‘?>’ tags. They rape my sessions. How about instead you just don’t use ‘?>’ in your ‘all PHP’ scripts? It isn’t required you know.

I hate you guys. Seriously.

Document your code…seriously

OK Mr. Cowboy programmer. I get it. You’re special and never have to leave any amount of documentation for all your PROCEDURAL code. Yeah, yeah; I like all that SQL in there next to your massive prints spitting out HTML. What’s that? You created functions to spit out entire pages of sites? printAboutUs()? Awesome. Really. I mean it.

Honestly, not even one line at the top of your 800 files to tell me what this one script (of the aforementioned 800) does? How about a basic README file? No?

*gun blast*