DISCLAIMER:** I did answer this question. I was not the person that the poster was referring to, as I did not write the code for the person, but I did add an answer which showed some basic concepts and encouraged research. So I don't know if that means I was just trying to collect rep or not.**********

While I completely agree with you that we should discourage 'do this for me' questions, I would argue that you can sometimes turn a 'crappy' question into a decent and useful answer. This is what I tried to do in my answer was to take a rather poor question, and give useful information WITHOUT doing the work for the asker. It's my hopes that it nudges the asker to apply some of the tactics I showed, combined with some research, they could take a stab at it. Also could be useful for others coming along looking for info on bulkifying trigger.

I have used this tactic in the past where I add very general high level help to very poor, and specific questions (like 'help me write test code for this class').

Here is an example of an answer I put in what I think is a similar question.

Writing a test classes

IMO, a rather poor question, and it did end up being closed. I think though that the answer I provided could be useful for people coming along looking for help writing test code.

I'm sure there are some varying opinions on here as to whether this is the right approach or not, so I'd love to hear your opinions.

My general thought is. NEVER just write code for someone asking for that, BUT I will sometimes give them very high level ideas and code, that will get them started on the right track.

Love to hear everyone else's thoughts.

DISCLAIMER:** I did answer this question. I was not the person that the poster was referring to, as I did not write the code for the person, but I did add an answer which showed some basic concepts and encouraged research. So I don't know if that means I was just trying to collect rep or not.**********

While I completely agree with you that we should discourage 'do this for me' questions, I would argue that you can sometimes turn a 'crappy' question into a decent and useful answer. This is what I tried to do in my answer was to take a rather poor question, and give useful information WITHOUT doing the work for the asker. It's my hopes that it nudges the asker to apply some of the tactics I showed, combined with some research, they could take a stab at it. Also could be useful for others coming along looking for info on bulkifying trigger.

I have used this tactic in the past where I add very general high level help to very poor, and specific questions (like 'help me write test code for this class').

Here is an example of an answer I put in what I think is a similar question.

Writing a test classes

IMO, a rather poor question, and it did end up being closed. I think though that the answer I provided could be useful for people coming along looking for help writing test code.

I'm sure there are some varying opinions on here as to whether this is the right approach or not, so I'd love to hear your opinions.

My general thought is. NEVER just write code for someone asking for that, BUT I will sometimes give them very high level ideas and code, that will get them started on the right track.

Love to hear everyone else's thoughts.