Post History
This feels very opinion based (maybe the bulk of my time spent on scifi.se has conditioned me to cringe at opinion, not fact based responses :) - however, as a software developer, there is some pre...
Answer
#3: Attribution notice added
by
System
·
2019-12-08T05:09:19Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/21477 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
NKCampbell
·
2019-12-08T05:09:19Z (almost 5 years ago)
This feels very opinion based (maybe the bulk of my time spent on scifi.se has conditioned me to cringe at opinion, not fact based responses :) - however, as a software developer, there is some precedent for this practice in what is called a "[spike](http://www.scaledagileframework.com/spikes/)" - which is thought of as an experiment or proof of concept. With a true 'spike' - you always throw away what you write because it wasn't intended to be the final product, but a learning experience. From the experience gained in the spike, you can then start over and construct the code properly and using best practices. If we take this idea to the writing world, you could 'spike' on thought experiments, writing prompts, etc... with no pressure other than to gain experience and learn. I don't know if I would recommend a set of rules though that demanded you throw out work on actual projects though.
#1: Imported from external source
by
System
·
2016-03-25T15:37:52Z (over 8 years ago)
Original score: 1