[Request] Don't use brackets unless you're posting an actual hack

Enough of this. Before it was just petty, insignificant annoyance, now it is a full-blown, 100% pet peeve. The reason people put [Release] before the title of their post is that we know that it is actually a hack, and not a silly request. If all the requests start with [Request] then it defeats the purpose. Maybe I'm going overboard with this, but I'd rather everybody read this and think I'm an a-hole than come to this forum and see [Request] after [Request], and then bit(h about it another thread in another forum so the people who do it don't even know that they are pissing me and several other people off.

I'm sorry this is not a hack - but enough is enough, it was time for an intervention.

-jim

I don't like them here...
I don't like them there...
I don't like them [] anywhere!

I don't like them in a box...
I don't like them with a fox...
............

BITT.
(Bringing It To the Top)

can someone make this a sticky thread please, it is happening again!

Wow - I had almost forgotten about this bad boy

-jim

In my opinion people shouldn't post requests anyway. If you want something added as a hack and not a feature you should take the initiative to write it yourself. I wouldn't say PHP is that complex of a language to learn. The MySQL would probably be the hurdle anyway as it's a different kind of planned logic then most newbie coders are used to dealing with.

Here are the steps I would personally recommend anyone that wants a hack follow before posting a "request":

1) Visit http://www.php.net and give the manual a mix of reading and skimming. Pay close attention to the parts are unique to PHP and skim the similarities between it and other languages you know.

2) It's easier to learn a language if you look at real world applications of it, so open up some of the source and dive in. A good place to start might be the global.php that is 'require'd at the beginning of every script.

3) Develope a basic rough draft of a design for your hack, citing what changes will need to be made to existing code and what will have to be added from scratch. Just a cursory fly-by.

4) Then see if you can work on some of it yourself. If you have trouble I think people would be more helpful if you ask specific questions then if you request they write it from scratch.

5) Or if you find you can't write it, give someone the design you have come up with. Not just the specific feature. It is much easier to work with a plan that gives specifics then a "I would like this feature"

Anyone else agree or disagree?