Timeline for Is it good practice to share your personal work after receiving the answer?
Current License: CC BY-SA 3.0
3 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 5, 2012 at 19:25 | comment | added | Andrew Stacey | @Fritz Nothing is absolute! It's always a judgement call. This case scenario seemed to be about a situation where the given solution was fairly detailed, but there were some extra bits missing, or not quite working for the specific use-case. So the original answer may be useful by itself. In the situation you outline, it's more that the original answer would be hard to do without any additional work. The bottom line is that you should always attribute your work, then if folk feel that there's an imbalance in how things look, they can vote to redress the balance. | |
Apr 5, 2012 at 15:56 | comment | added | Fritz | I don't know if this was asked before, but is point 3 an absolute statement or are there situations when accepting your own answer would actually be acceptable? For example if someone wrote a very brief answer like "You can use this package: [link]" and you proceeded to implement your complex 20 line macro that actually solves your problem, using that package. In that case, should you accept the short answer to give credit, should you accept your own answer that contains the full solution for the benefit of the future reader, or should you edit the original answer and add your solution? | |
Mar 31, 2012 at 18:56 | history | answered | Andrew Stacey | CC BY-SA 3.0 |