Revisions to Should we stop being so generous?

replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/

Source Link

edited Apr 13, 2017 at 12:39

Community Bot

1

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo Luis Mendo's comments on one of my most recent posts recent posts as an example.

I posted my original answer original answer
Luis Mendo commented and suggested a different approach different approach that saved 5 bytes
I found an approach an approach that saved another byte.
Luis found another different approach different approach that saved 5 bytes
Before I even responded, Luis found a new different approach different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tweeted twitter.com/StackCodeGolf/status/840789947204456448

occurred Mar 12, 2017 at 5:01

added 8 characters in body

Source Link

edited Mar 7, 2017 at 22:21

Stewie Griffin

46.5k
16
29

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then youit should be OK to post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

added 17 characters in body

Source Link

edited Mar 7, 2017 at 21:35

Stewie Griffin

46.5k
16
29

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

_{Note: This post is about site culture, not policy making.}

I'll use Luis Mendo's comments on one of my most recent posts as an example.

I posted my original answer
Luis Mendo commented and suggested a different approach that saved 5 bytes
I found an approach that saved another byte.
Luis found another different approach that saved 5 bytes
Before I even responded, Luis found a new different approach that saved yet another 9 bytes.

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post¹, but the shorter approaches are still his.

I suggest that:

We still post comments suggesting simple improvements ("you can use 1e3 instead of 1000")
We post separate answers, even if they're inspired by (and similar to) someone else's. And as always: Give credit where credit's due.

¹Of course he would, but let's pretend he wouldn't.

added 72 characters in body

Source Link

edited Mar 7, 2017 at 21:23

Stewie Griffin

46.5k
16
29

Loading

edited body

Source Link

edited Mar 7, 2017 at 21:03

Stewie Griffin

46.5k
16
29

Loading

Source Link

asked Mar 7, 2017 at 20:50

Stewie Griffin

46.5k
16
29

Loading

Stack Exchange Network

Return to Question

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then youit should be OK to post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then it should be OK to post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

Tl;dr: The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.