Thanks for the laughs everybody. I guess I was too concerned about what this guy thinks about "PHP programmers" to realize some of this stuff. All of that about not being specific to PHP was something I kinda forgot. I'm getting caught up too much in how to do things the PHP way I guess. I've kind been on a kick about that lately - and it's probably not a healthy kick. My background is mostly in Desktop and console applications, so I use tools like C# and Java (both force OOP to some extent on the developer) mostly and some other languages also, like Ruby, C++, and C. Each of those languages, though similar (in some aspects), have a certain way of handling their mechanics, so I learned the Java way to do things and the C# way to do things, just so that I could talk to Java and C# developers better and write code that makes more sense to them.
Maybe that's where I'm getting to - I'm working a side job right now that requires me to do PHP scripting, and I wrote a simple template system, but when my supervisor looked at it he said he wasn't sure how I was handling tamplating in my code. <pseudo-code> index.php - sets $page as page content file - require_once's the template default_template.php which checks for $page to be set and require_once's that page into the middle of the template ---maybe that's the wrong way to do it!? So should I not be so caught up in how to do things the "PHP way" as whether or not the outcome, i.e. the resulting web site, looks? Nathan On Wed, May 14, 2008 at 3:50 PM, Beau Scott <[EMAIL PROTECTED]> wrote: > >> I myself have done many sites, and very rarely use abstract and > interfaces > > Exactly. The beauty of PHP is that if you wanted to make a highly > architected, well defined application that is easy to maintain, read, etc., > you can. It gives you that ability. > > But if you're on a time crunch and have to "hack" out a site in short > notice > and don't care to make it maintainable (perhaps it's a short lived > promotional site, etc.), you can do that, too. Most often, I'd wager, sites > fall somewhere in between these two categories. > > And I think the measure of a good PHP developer is his/her ability to just > that: determine the architectural need for the project and code it > accordingly. Whether the site uses OOP or not isn't a good metric for > programming aptitude. > > Granted he did have some good generic guidelines that should be followed no > matter what aspect you take (like SQL injection protection) -- and that > does > weigh on my opinion of any developer, PHP or not. > > Beau > -- Nathan Lane Home, http://www.nathandelane.com Blog, http://nathandelane.blogspot.com _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
