I have recently been assigned as a Page Editor for the PHP TAs to provide some extra support alongside ThG.
There are various issues that I will highlight in this thread concerning the present and future state of the PHP TA's. I would like to invite all currently active PHP experts to take part in this discussion, particularly those who have an interest in the future development of the TA. I will be taking everyones thoughts, opinions and ideas into account.
The Structure of the PHP TA's
-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-
Currently we have:
- PHP
- PHP and Databases
- PHP for Windows
- PHP Installation
Many of you will be aware of the development of new version of Experts Exchange which will feature, among other things, new and restructured Topic Areas.
On the Alpha site, the PHP TAs have currently been merged into a single TA.
My personal opinion is that PHP should be reduced to two TAs (PHP & PHP and Databases) rather then one for the following reasons:
- PHP for Windows is a less active TA, the majority of questions asked here are usually general PHP questions which should be posted in the main TA. There are very few Windows specific questions asked.
- PHP Installation is also a less active TA.
- The questions that are asked in the two previously mentioned TAs could easily be addressed in the main area. Generally speaking it is the same experts that provide help in all of these areas anyway.
>>> An agreed "ideal structure" needs to be established by this coming weekend so, if you have an opinion on the structure, please speak up now. <<<
Try to think of the situation from a perspective of whats best for the PHP areas rather then points. Remember, if the TA's are merged you will not lose your earned points, they will be added to your total in the main PHP TA.
Current Issues
-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-
A minor issue that has been present as long as I can remember is users posting their question in the wrong TA, that is to say:
- Asking a PHP question that has no relation to databases in the PHP and Databases TA
- Asking a Database related question in the main PHP TA
You may argue that this is not a big problem since they are both PHP TA's, however, having the questions scattered around can cause inconvenience. For example, if a user searches the PHP and Databases PAQ for an answer to a specific question it will not help them if half of the Database related PAQs are in another area.
Further more some experts have greater knowledge in one field then the other. My knowledge of databases is less solid then my coding ability so I tend to stick to the main TA. Another expert may have very good knowledge of MySQL but a lesser ability in PHP, keeping the database related questions separate means they can still provide help.
Unless objections are made I intend to move such questions to the correct TA from here on. Please note that I have no intention of searching through the PAQ database and moving old questions, its simply an impractical task your current point standings in each TA will therefore not be affected.
I have no other plans of action at this point in time other then enforcing the MA as a PE and generally maintaining order in the TA's.
If you have anything to add to what I have said, or have any concerns that you feel need bringing to my attention then please, contribute to this thread. Your opinions will count.
Working as a Team, setting an example
-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-
This is one for the long term which I do not plan to go into too much detail at this point in time. An ideal situation for the experts in the PHP TA's is to be able to interact as part of a team and set an example to the new members. The following is some things that I would like to see happen over the course of time:
- Everyone working together with the common goal of helping the user, not scoring the points.
- Eliminate the posting of poor code. Error Notices are still errors and hiding them means, yes you cannot see them but they are- still there. This is where setting an example comes into play. If the current experts strive to write good, clean code then newbie experts will fall into line and continue the trend. The big picture here is educating the next generation of PHP developers, they learn from our comments and code. If we give them sloppy code they may not know any better and will end up inheriting the bad habit.
- Resisting the urge to score "easy points"/post tagging. It is a common occurrence for even some of the best ranked experts at EE to post a rapid reply to a question to secure points, especially on easy questions. I have lost count of the amount of time I have spent writing replies only to find out that another user has posted a one liner and rendered my post useless. Take the time to write a reply that the user will learn from, tell them something that will help them in the future, guide them to becoming a better developer. I guarantee you will feel better for sharing your knowledge then you will for bagging a few points.
- If an expert has a question covered be respectful and let them handle it. That is to say, if ExpertA has posted an answer and is capable of helping the user solve their problem, ExpertB will not help anyone by jumping in with "here is another way to do it... ". By all means contribute to a thread if you can add another angle or if ExpertA needs some extra help but don't do it JUST for the sake of "lets throw another bone and see if I can get something out of it".
If you have any comments or additional things to add to the above then... post away :)
This thread is about standing on the shoulders of the past and looking towards a better future for the PHP TA. If you have an idea about something that could help enhance the TA or have any concerns then get involved in this thread. Even if you have nothing to say at this point in time then hit the subscribe button, you might find you have something to add further down the line.
Diablo84
PHP Page Editor
Start Free Trial