The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
|||||||
|
#31
08-02-2005, 02:53 AM
|
||||
|
||||
Quote:
 What you are muttering about respect, I'm unsure - The message I am getting disrespects me - It disrespects my standpoint which is shared by others and it is at some points almost offensive... It does not always create high server load - With multiple queries its not a case of a standard - Simply tell the user the information is already loaded and that their queries are not needed... Jelsoft's guidelines should not be - PHP is not exclusive for Jelsoft - You are treating it as if it is or should be... Whatever happens, it will cause more problems than it's worth - The only ones who are going to moan about standards are those who can already sort the problem out themselves, but cannot be bothered, but expect others to do it for them when they may not know how... Satan |
|
#32
08-02-2005, 05:21 AM
|
|||
|
|||
|
Quote:
|
|
#33
08-02-2005, 05:22 AM
|
||||
|
||||
|
Let's get one thing straight - there's a huge difference between:
1. Badly written code AND 2. Well-written code that looks bad In case 1, the code is badly written so that there are more queries, it is inefficient etc. In case 2, the code works well, but just looks bad - ie. it's not formatted nicely in separate lines with comments. If we are talking about case 1, I say, go for it, try to optimize badly written code. If we are talking about case 2, then I would say that is up to individual preference - for example, if and when I release a hack, it's because I've usually written it for my own site, so I'm not going to waste too much time formatting it "to look nice". So let's decide - are we talking about function or about "looks". 
|
|
#34
08-02-2005, 05:24 AM
|
||||
|
||||
|
But even functionally bad code shouldn't be a hinderance to a newbie. Teaching him how to do it right is altogether different than chastising him in public with some sort of label. That will turn some otherwise good coders off from trying to learn and make it better.
|
|
#35
08-02-2005, 06:17 AM
|
|||
|
|||
|
You are forgetting possibility 3 (or 1b): Badly written code that cause either security holes or make your board disfunction to some degree.
|
|
#36
08-02-2005, 06:22 AM
|
||||
|
||||
|
Quote:
i honestly dont see it benefiting either... as someone who is just beggining to learn all this doesnt really care about neat code.. they want to learn how to code.. and so with time theyll learn, hopefully. i cant see it benefitting the community because like Satan, Amy and Boofo have previously stated this will more likely create a rift in the community between coders. so i say No to QA just my 1/2 a cent |
|
#37
08-02-2005, 06:36 AM
|
||||
|
||||
|
As a member who's only released a couple of hacks and is still a "beginner" in terms of coding for the uses of others, I know that if someone were to come along and either label my hack "inefficient", "poorly written", or "not quality assured" I probably wouldn't bother to even consider releasing hacks later down the line.
If you come across a hack that is so poor that it would harm the function of the forum, I think you should simply try and help the user who released it. Instead of "This hack is not quality assured and therefore is garbage", say "Well, around [this block], you could minimize the number of queries by doing [this]..." and the response you would receieve would most likely a thank-you. This idea comes across as egotistical and sounds to me like a way to rub skill in the face of somebody who's still learning. |
|
#38
08-02-2005, 06:44 AM
|
||||
|
||||
|
Quote:
Second, grouping me with Satan defiantely makes me never want to release another hack/mod.
|
|
#39
08-02-2005, 06:48 AM
|
|||
|
|||
|
Quote:
|
 |
«
Previous Thread
|
Next Thread
»
Linear Mode
|
|
All times are GMT. The time now is 08:16 PM.