Jump to content



Photo

Any PHP Developers Want To Team Up?


  • Please log in to reply
55 replies to this topic

#31 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 27 December 2012 - 02:25

You might be able to learn from creating the site, but you learn nothing by using a framework, all you learn is how to rely on it. If there's a job opening for a PHP coder for instance, if you've only got experiance in PHP by using a framework, unless that company ONLY uses that framework, you won't get the job. The job will go to someone that doesn't rely on frameworks.


If I have the complete experience to create my own framework for the site, then I'd be glad to switch it from Symfony to my own once it's the way I need it. Until then, I'd have to make-do. I'm hoping I gain complete knowledge to create whatever when PHP 6 comes around (god knows when that's happening).


#32 n_K

n_K

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 19-March 06
  • Location: here.
  • OS: FreeDOS
  • Phone: Nokia 3315

Posted 27 December 2012 - 02:48

Why PHP6? PHP5 is fine and it's more than likely whatever you code for PHP5 will work as-is or need very little adjustment to work in PHP6, and you can read what syntax will be removed in PHP6 in the PHP documentation.

#33 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 27 December 2012 - 02:53

True, AFAIR, PHP 5.6 is in Alpha stage and I'm just hoping I could understand most of the current by stable release. It's just that I've always been the bleeding edge type.

#34 n_K

n_K

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 19-March 06
  • Location: here.
  • OS: FreeDOS
  • Phone: Nokia 3315

Posted 27 December 2012 - 03:05

It is a VERY bad idea to use bleeding edge on a production server.
I've got bleeding edge hiphop on the site I code for but it's not really ever used.
If you expect to create and run a social networking site - you do NOT want bleeding edge.
Bleeding edge software brings bleeding edge problems and bugs with it, you're talking about PHP 5.6 now but here's the top news article on php.net; 'PHP 5.5.0 Alpha2 released: THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!'

#35 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 27 December 2012 - 03:12

It is a VERY bad idea to use bleeding edge on a production server.
I've got bleeding edge hiphop on the site I code for but it's not really ever used.
If you expect to create and run a social networking site - you do NOT want bleeding edge.
Bleeding edge software brings bleeding edge problems and bugs with it, you're talking about PHP 5.6 now but here's the top news article on php.net; 'PHP 5.5.0 Alpha2 released: THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!'


I'm not that crazy. Who said I was using dev's on production? lol I always use the latest everything personally. I already have the 5.6a2.

#36 Eddie7

Eddie7

    Hallo... www.connectw.me

  • Joined: 01-December 11
  • Location: Sydney, Australia
  • OS: Windows 7 Ultimate
  • Phone: 1-800-CALL-ME-MAYBE

Posted 27 December 2012 - 18:33

I'll help you with it if it's going to start off from scratch. :)

#37 goodbytes

goodbytes

    Just below average Joe

  • Tech Issues Solved: 1
  • Joined: 07-May 04
  • Location: England

Posted 27 December 2012 - 21:26

Surprised nobody has mentioned Laravel, it blows any other Framework out of the water.

Look up Laravel 4, and also check out the Bundles.. you'll smile.

#38 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 27 December 2012 - 21:38

I'll help you with it if it's going to start off from scratch. :)


I prefer we at least work on a framework to make a good start and then work on our own where we could clean up and provide more of the necessary. We also need to think about the attraction, so we at least need a good start til then. :)

Surprised nobody has mentioned Laravel, it blows any other Framework out of the water.

Look up Laravel 4, and also check out the Bundles.. you'll smile.


I've seen it for a while on TutsPlus. After seeing so many Frameworks, I was so unsure what to work with.

#39 Tekkerson

Tekkerson

    Droppin' them beats like hot potatoes.

  • Joined: 05-March 08
  • Location: Dallas, TX

Posted 28 December 2012 - 07:16

I really mean no offense to n_K but it seems he doesn't have experience working and maintaining large projects. Writing everything from scratch can be (and most likely be) a nightmare.

The issue is NOT that you can or can't write from scratch, the issue is (for the most part) maintainability. Frameworks (specifically MVC) are designed and teach you to decouple your code so that it maintains re-usability, ease of maintainability, stability (via the writing of tests aka unit testing) and just mostly independent of other parts of the framework.

Meaning that if you decide to move to another framework or even your own the code would already be decoupled and you'd be able to use it in many other projects just by calling the parts you need.

This means that all the business logic in your code isn't stuck to the framework, it's just being used by it.

Although the setup can be framework specific, the code you write can be used by many other things outside of the framework. Because again, your code will not depend on the framework and will produce results that can be used by many other services. Be it an API or library, you name it.

I do however agree that it's not a good idea to use bleeding edge on a production server. Use the version that has all the features you actually need. Even if that means to use the most stable yet reasonably up-to-date 5.3 versions.

#40 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 28 December 2012 - 07:52

What I'm really trying to provide for the UX is almost as complicated as Facebook or any of the major social networks. Features that even require the study of the user, and even the feedback of the UX itself. That's why I trust using Frameworks before I go off from doing anything from scratch as nowadays. It's best to take shortcuts before you know you're whole way around. Hope this makes sense.

#41 Tekkerson

Tekkerson

    Droppin' them beats like hot potatoes.

  • Joined: 05-March 08
  • Location: Dallas, TX

Posted 28 December 2012 - 11:57

It's all about choice really, but IMO you're making the smarter choice by sticking with Symfony2 which suit your particular needs :)

No need to write the base code from scratch, you can just start coding away on the content and processing of information right away!

#42 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 28 December 2012 - 12:06

It's all about choice really, but IMO you're making the smarter choice by sticking with Symfony2 which suit your particular needs :)

No need to write the base code from scratch, you can just start coding away on the content and processing of information right away!


Thanks. :)

Currently working on the routing and the pages to setup, all that's static before I move on to any of the pages that require the database. Once that's setup, I'm definitely going to need a lot of help with the querying, or that could all be done at the same time with the help of a few teammates. :/

#43 Tekkerson

Tekkerson

    Droppin' them beats like hot potatoes.

  • Joined: 05-March 08
  • Location: Dallas, TX

Posted 28 December 2012 - 14:00

Thanks. :)

Currently working on the routing and the pages to setup, all that's static before I move on to any of the pages that require the database. Once that's setup, I'm definitely going to need a lot of help with the querying, or that could all be done at the same time with the help of a few teammates. :/


Anyway, if you set up a private git repository on GitHub I would most likely join. Or if you don't want to pay for a private repository and or never used source control we could try it out on my private repository.

Then that way we can add other developers on Neowin that'd wish to join the project. They could easily fork the project, submit their work and merging it with the main project would be a breeze. All while it keeps track of who did what and all the wonderful tools for code collaboration.

#44 OP Mr.XXIV

Mr.XXIV

    Shine bright like Iron Man.

  • Tech Issues Solved: 1
  • Joined: 30-April 11
  • Location: Durham, North Carolina
  • OS: OS X Yosemite
  • Phone: iPhone 5s

Posted 28 December 2012 - 22:05

Not sure if technomixx is spam or just trolling considering his post count...

Anyway, if you set up a private git repository on GitHub I would most likely join. Or if you don't want to pay for a private repository and or never used source control we could try it out on my private repository.

Then that way we can add other developers on Neowin that'd wish to join the project. They could easily fork the project, submit their work and merging it with the main project would be a breeze. All while it keeps track of who did what and all the wonderful tools for code collaboration.


I'll definitely need a private repository. :) It'll help me out more when I'll need to code on-the-go.

Not only is it spam but it's bad advice.

Wordpress sucks, it's a spammers heaven and is one of the most targeted platforms, and Code Igniter, i agree is clean and easy, but it's dying a slow death.. it's well worth playing with if you are new to frameworks but the community is shrinking more every day.


And definitely not a good idea for Social Networks, even with Buddypress. Heck, I even tried to develop MyLovr with BuddyPress to see how'd it work, basically, no. Just no.

FuelPHP was what made me ignore Code Igniter.

#45 Original Poster

Original Poster

    Systems Developer

  • Tech Issues Solved: 1
  • Joined: 15-July 08
  • Location: my room
  • OS: windows 7/8, Kali, ubuntu, OSx 10.9
  • Phone: Android

Posted 29 December 2012 - 12:35

If you're writing PHP from scratch you'l failing from the start. You'll want a good framework - Symfony is what we used at my last job.


interesting opinion, but I find creating new scripts that I can use over and over again (a personal template) is much better I know how it works and I control the security... I have developed my own admin panels and CMS which is installed on every clients site :p I do see your point frameworks are good but I dont feel like im doing a job but i do see the benefits in frameworks....