1)programmers are suppose to code well, using some std's, 
giving meaningfull names to the variables etc.... which 
also lead to Quality Assurence.And ofcourse team-work is 
required thw most...

2)Quality Assurence is responsible for the quality of the 
product. quality team is responsible for burst testing of 
the product.A tester must have the ability(inter personal 
skill) to impress the devloper and make him/her to sit and 
fix the bug.

programmers develop the application where as QA  is 
responsible for improving the quality of process in making 
a quality application.

QA is responsible for "Process Quality" and Programmers are 
responsible for "Product Quality".

Both work hand in hand where QA would be working to ensure 
that the processes used for developing the product ensure 
that the developed products are of high quality. 
Programmers have to used these processes effectively so 
that they end developing a high quality product.

Processes are the "ways" to produce a quality product. 
Processes are owned by QA.

Programmers are supposed to "implement" 
the "processes/ways" objectively so that they can produce a 
high quality product.

Any issues/area of improvement found during execution 
of "process" by the programmers should be communicated back 
to the QA so that they can improve/fine tune the process 
for future use

Development is the process of creating a product.  QA is the process of inspecting a product to see if it meets a standard.

Specifically it is the job of development to produce a product; it is the job of QA to inspect that product to determine if it meets a pre-defined standard.