Quote:
Originally posted by HFWang
ARGH ARGH ARGH ARGH.
HTML != PHP.
DESIGN != PHP.
Let me offer a brief example, my dad manages a team that writes code for IC layout and simulation. He knows java, c++, etc etc. But he couldn't make a table in HTML if his life depended on it. And thankfully it doesn't. He certainly has no "bad problems" because he understands programming but hasn't learned the tags that comprise HTML!
Stop thinking of PHP/(server-side language of choice) as being intricately tied to HTML. It should not be that way. Presentation and logic should be seperate. I wrote some basic roster and event calendar objects for my club for school without even having finalized the site's layout. My PHP script did not contain any HTML tags until awhile later (IE: I seperated data storage/retreival from the data "objects" and seperated that from the actual presentation. They are three seperate layers that interact through set interfaces but are distinct and if necessary could be replaced by similar layers with the same interface.)
|
When did I say that I think HTML == PHP and/or Design == PHP?