Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 2 of 2
04-21-2013, 05:31 PM #1
- Join Date
- Apr 2013
- Thanked 0 Times in 0 Posts
OOP required for college-level social networking site?
Hello everyone. This is my first post in this forum.
I am developing a social-cum-professional-cum-academic networking site for my college. I will be using PHP for the scripting part. I shall be getting a shared hosting package (cannot afford VPS/ dedicated hosting at the moment). There are around 2500 students in my college. I'm expecting around 1200 active members.
The professional and academic parts will be fairly simple. The main resource hog will be the social section. It will have the following features - posting, uploading photos, updating profiles, search mechanism, buddy system, personal messaging and a leaderboard with points system. No chat option.
Now I am fairly comfortable with procedural programming in PHP, but I don't have any experience with object oriented programming. In fact, I have just started learning Java. My question is - do I need to implement OOP for my kind of site?
If yes, why and how?
A couple of years ago, I had developed a rudimentary social network and tested it with a couple of friends of mine. It was just a personal project, with only a subset of the features mentioned above. At that time, I had used only procedural programming. This time the user base is going to be much larger (hopefully), as mentioned above.
Looking forward to your response.
04-21-2013, 08:05 PM #2
- Join Date
- Dec 2011
- Thanked 14 Times in 14 Posts
I'm just getting the grasp of OOP myself and my answer is if you are comfortable writing PHP the procedure style then start slow with OOP. Don't try to do everything at once with OOP, take it in sections. By that I mean what can OOP do to cut the repetition of my code down or how can the code make it cleaner and modular for other programmers who might be working on the same project . I think the big break for me came when I started understanding objects and arrays, plus the relationship the have with each other. I also found myself doing little test scripts on constructors, methods, classes, etc.. and visiting php.net manual a lot reading about them and seeing examples of what other people have done in the past.
There's nothing wrong in doing the procedural way (specially if you're comfortable with it) and slowly bring OOP into the mix. You might also want to consider using some kind of framework, if it's getting close to crunch time. Just my .02 cents.
I seen a lot of posts lately with people (I include myself when I first started OOP) trying to do everything at once with OOP. Once I was straighten out by others, I learn OOP is just another tool in your tool belt to make it easier coding. Just doing OOP to do OOP is just a waste of time, if it's a small project then maybe doing it the procedural way might be the best way. It's something every programmer has to decided what is best.
Last edited by Strider64; 04-21-2013 at 08:09 PM.
Users who have thanked Strider64 for this post: