LB1234
asked on
How to plan, organize, and systematically build a complex PHP site
I have cobbled together and bumbled my way through my first PHP site to learn the ropes and do a practice run. But the process has been haphazard and disorganized. Is there some convention, model, or method I can use to systematically think through and build the site and database, etc, so that the whole process is less painful and efficient? Additionally, any personal tips or insights would be greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Lol, only 100 Dave? Are you saying that the process just develops organically over time?
No, it doesn't develop organically, it develops from progressive challenges. Norvig speaks to this. And Dave's right - a hundred web sites will give you a breadth and depth of experience that will make the job easier.
Examples of PHP code with annotations are all around you, some good, some bad. This article will point you to good learning resources and more importantly, help you avoid the many bad examples that litter the internet. Unfortunately bad examples do not come with warning labels or expiration dates - they just lie there waiting for a novice to copy them and propagate bad programming practices. So avoid random learning and choose structured learning instead. You'll be better off for it, I promise.
https://www.experts-exchange.com/Web_Development/Web_Languages-Standards/PHP/A_11769-And-by-the-way-I-am-new-to-PHP.html
Examples of PHP code with annotations are all around you, some good, some bad. This article will point you to good learning resources and more importantly, help you avoid the many bad examples that litter the internet. Unfortunately bad examples do not come with warning labels or expiration dates - they just lie there waiting for a novice to copy them and propagate bad programming practices. So avoid random learning and choose structured learning instead. You'll be better off for it, I promise.
https://www.experts-exchange.com/Web_Development/Web_Languages-Standards/PHP/A_11769-And-by-the-way-I-am-new-to-PHP.html
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ray I did read Norvig's site. It's good stuff. I don't really love programming, but I see its usefulness and that enough for me. And I'll take your advice to heart.
I've gotten my feet wet with PHP and feel like I have a novice's understanding of it. Should I learn OOP PHP or just keep practicing and building on what I already know in the procedural style. Also wondering if it's all right to dive into JavaScript, or should I fully master PHP first?
I've gotten my feet wet with PHP and feel like I have a novice's understanding of it. Should I learn OOP PHP or just keep practicing and building on what I already know in the procedural style. Also wondering if it's all right to dive into JavaScript, or should I fully master PHP first?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
On a personal note, what keeps you guys, day in day out, helping people with annoying programming issues??? Why do you do it?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why do you do it?I was looking for help with a programming project in 2007 and found Experts-Exchange where I got some really good help - worth many times the modest annual fee. When I realized that I could make a contribution to the PHP Zone, I decided I would make it a habit to answer one or two questions a day as I had my morning coffee. Over the course of the last seven years I've handled all kinds of interesting question from the mundane to the extraordinary, and the process has helped me to build a teaching library of examples. It's sharpened my skillsets a lot and I've gotten at least as much from answering the questions as the authors of the questions have gotten from my answers. And I get consulting gigs when members of EE need a PHP developer. So it's a win-win relationship all the way.
I do it both for the recognition (which you don't get much as an independent developer) and to learn things. You can learn a Lot by trying to answer questions. Other people don't do things the same way so working thru their code and methods teaches you things to do and Not to do. I've gotten a few consulting gigs from members also.
While I focus on PHP here, I've always been a jack-of-all-trades because I've had to fix whatever it was that wasn't working. I was an electronics tech and then designer before I starting programming and web design. I read at least the title of every single question that is posted here to see if it's something I want to find out about. If it peaks my curiosity, I read the whole question. And if I think I know something about it, I try to help with an answer or comment. Sometimes I just 'monitor' the question to see what answers they come up with.
While I focus on PHP here, I've always been a jack-of-all-trades because I've had to fix whatever it was that wasn't working. I was an electronics tech and then designer before I starting programming and web design. I read at least the title of every single question that is posted here to see if it's something I want to find out about. If it peaks my curiosity, I read the whole question. And if I think I know something about it, I try to help with an answer or comment. Sometimes I just 'monitor' the question to see what answers they come up with.
ASKER