Put simply, of all the research sites I’ve ever gone to for information, this site ranks up there with some of the worse. It isn’t just the poor link color choice, it is the lack of organization. The articles, while outdated are well written and thought out.
I would rather have shelled out the money for a PHP book on the topic, which is always a good idea on complex subjects such as this. Programming Patterns have been around for a long time. However, they are usually targeted to a single language and it would be difficult for a novice who doesn’t know language of choice to convert it over to their own.
Patterns For PHP
Once this site is completed, I can see it having huge popularity and a valuable resource for PHP developers. The Popularity part should probably pick up towards the middle and then die to a manageable level. Hey, there are only so many patterns! It should be more popular than PHP Patterns once all of the Patterns are finished and it has a dedicated URL. I think patternsforphp.info would be a good URL, if it hasn’t already been taken. However, .com would be easier to remember.
However, I hope it becomes more like a living online OOP and Design Pattern Book. While the designs won’t change, there will be changes to the language and the examples will have to change. There won’t be much difference between PHP 5 and PHP 6 that the examples will have to be rewritten, but there are going to be some nice additions that could be placed on the site.
Patterns for OOP
I’m not sure what the overall plan for the site. I believe the owner stated that he would place some OOP related material on the site. I would be interested in formally learning the material, even if I have a OOP programming book on my shelve that I haven’t picked up for over a year. It isn’t six feet away.
If I wrote anything on OOP, it would be laced with references to other sites and books. Not a bad thing to have, so that if they wanted to learn more advanced topic they could buy the book (have a link to amazon) or go to the reference page for more details.
References
Technically, most of the articles on the page should have references to other pages and books where the material was first picked up. It would be difficult to go through and find all of the references that I read about months ago.
Writing SPL Articles
It is a reason why I haven’t wrote anything and don’t plan on writing any articles on other SPL iterators. SPL has a lot of Iterators and it would be nice to have all of it in one place, however, contribution should probably be made on the other SPL Wiki site instead. The style of the SPL Wiki is a good one, straight to the point with good examples. The question is, should I try to beat that? I’m not sure.
The issue is not that I can’t do it, the issue is that if I did, would I draw to much from SPL Wiki in that I’m just copying over material? Not intentionally of course. I just can’t justify writing something where there is a better source out there. SPL Wiki doesn’t cover all of the Iterators and SPL objects, but SPL has a lot.
Limited Contributions
I’m quite limited on what I can contribute to Patterns for PHP, I’m not familiar with a lot of Patterns listed and would have to do a lot of research and even then I’ll probably talk out my ass on some of the parts. I have written research papers, but they were on material I already knew something about. When I try to write about something I don’t fully grasp, it comes out vague and half-assed.
I’ll probably will do some research on the ones that the others are too busy to do to get them at least somewhat finished. The MVC Pattern will be of a Huge Interest to developers and for people wanting to use Zend Framework and others that use MVC.
Possibly Related Posts:
- Game Engine Development and Open Source
- Plans for Base CMS
- Bullet: E-Book Library Management and Content Server
- Using ZendFramework 2 beta1 For Directory Project
- Project Plans
Comments are closed.