Mindsets and attitudes.

Always keep a positive mindset that oneself is accountable in not just answering but also questioning. Try to be professional in your question if you want professional answer. (of course understanding this is not a real professional programming forum but at least, lifting up the image is better than pulling it down?)



This post has been edited by anthony_yio: Jun 19 2007, 07:49 PM

Know the technology and the terms use.

Say if you are asking VB question. Specify what version, what component you are using, what DBMS, how do you connect and other details.

E.g

OS Environment: Win2k
OS Language Version: English (standard)
Language: VB6
Visual Studio Service Pack: SP6 <-- might not be necessary. Just an example.
Component: ActiveX: ADO, ActiveX: Windows Media Player
DMBS (if any): Oracle
SQL: PL/SQL


If possible, use the term that commonly been used. Like DBMS, MFC, Win32, ADO, ActiveX, Javascript, socket, client side scripting (vbscript/javascript), Java Bean, EJB, J2EE and etc.

If some of you are unsure of the terms cause you are very new,at least try to search for some in google or check the books. Knowing some commonly used terms helps to promote efficiency in conveying what you are trying to ask.






This post has been edited by anthony_yio: Jun 19 2007, 07:43 PM

For those who post the whole chunk of codes and expect people to look for what is wrong.

It would be more appropriate if you found WHERE is POTENTIAL problematic code yourself (i.e., bug), and then ask us what is wrong with it. Simply asking us to search through a bunch of codes to find out what is wrong do imply asking a BIG favor from us. Narrow your code down to just a few statements and you'll get way more help.

(even some problems do require some amount of codes to explain but I believe the extraction is ALWAYS possible. People only interested in replying from the extracted info and not from raw.)

This post has been edited by anthony_yio: Jun 19 2007, 07:40 PM

May be show some

-pre-conditions (before the action)

- post-conditions (after the action)

of the database records, program behaviour, program snapshot, or UI display



It would help in explaining the requirements/problems you need. Instead trying to describe in your own sentence in words which might sometimes be confusing.

Also, showing the codes or relavent script or setting snapshot would also help.

This post has been edited by anthony_yio: Jun 21 2006, 08:24 PM

Before asking some questions on problems that you encounter because you are not doing it in a conventional way (conventional means mostly people will have done that way), have you consider the basics that you might have neglected which could be the 'root' cause of your problem? Always having these mindset


- Proven concepts should be used no matter how basic it is and new ideas should be built on top of it. If you would create something different (groundbreaking) provided you understand what you are doing is clearly innovative. Then, you would need to back up your stuff with good reasons. Anyway, try to stick to proven concepts, this is not RFC committee. Nobody bother to debate on proven standards here.

(Majority of proven concepts can never go wrong. Not with an easy solution or workaround most of the time.)



This post has been edited by anthony_yio: Jun 19 2007, 07:38 PM