just finished my first PHP book, I'm ready to jump in!

jacobjmorris

I've been designing websites for several years now with HTML/CSS. I'm now ready to begin my journey into building applications and dynamic content....so I decided to pick up PHP. I don't have a background in programming, this is my first language, so I really don't understand OOP real well.

I just finished reading Kevin Yank's book on Building Database Driven Websites with PHP and MySQL. I have a better understanding of the syntax and can now actually read some of the code and understand what it exactly does.

Having said that, I'm a little overwhelmed and still lost. It's almost as if where do I begin, what do I start on, and what's the best, most standard and scalable way to do it.

I feel like the best thing for me to do right now is start with the most basic functionality and then work my way up to the harder tasks. Though part of me says work on the harder stuff (i.e. user management) as it will impact the smaller, easier to build applications.

If there are any guidelines that should be followed, I welcome the advice.

cdwhalley_com

I think a lot of people get to a point when starting with a language like that. It's a bit hard to suggest what to do.
I think a good, substantial first project would be a guestbook with mySQL?
You would have 1 page that lets you view all the messages, and another that lets you add a new message along with your name and email address.
This would give practice with forms, passing variables between pages, data validation (eg make sure they put a message) and interaction with mySQL, as well as just general language practice.
You could add more to it if you wanted to make it more advanced (e.g. censor filter, admin functions, etc)

As for guidelines: make sure you have a plan before you start, make the code clear with lots of whitespace and comments, use the php.net manual!

jacobjmorris

Thanks CD! Yeah, I've already started the planning peice. I'm writing down what I want in wireframes and flow charts.

After reading this book though, I still feel like I don't get it. It's easy for me to cut and paste a script, but when it comes to writing something from scratch, that's where I get lost. My mind still hasn't converted over to programmer's thinking I guess.

I'm thinking I either need some more hands on experience, or perhaps do some more reading in programming.