Content Problem I
Unfinished Symphonies
How many times has this happened to you? You have an idea for a program (painting, poem, wood-working project), and think, "That would be a fun challenge". You do the difficult bits first (naturally) as a proof of concept. Then, once you've shown yourself that it's possible, you get bogged down in the details and never finish.
See, I think that your main objective in these projects is not the final result that you can use or show to people or whatever, but in proving that you can overcome the challenge that lay in the initial idea. Unfortunately, I do this all the time.
Blogging
One self-referential example is this blog. Writing the system (e.g. the program to store, retrieve, and send these thoughts that you're reading now) was the challenge, and I have a working proof of concept. It's not perfect (I need to work on some minor formatting issues, and I'm not sure if the Scheduled Task will run when I need it to), but the failure of this project (i.e. blogging regularly) will not be a failure of this system - after all, I can always blog "manually" - but from a lack of content.
I call this the content problem. I've got some solutions, which I'll list in a separate blog. (See the tricks I have to use to extend my meager portion of content?)
How many times has this happened to you? You have an idea for a program (painting, poem, wood-working project), and think, "That would be a fun challenge". You do the difficult bits first (naturally) as a proof of concept. Then, once you've shown yourself that it's possible, you get bogged down in the details and never finish.
See, I think that your main objective in these projects is not the final result that you can use or show to people or whatever, but in proving that you can overcome the challenge that lay in the initial idea. Unfortunately, I do this all the time.
Blogging
One self-referential example is this blog. Writing the system (e.g. the program to store, retrieve, and send these thoughts that you're reading now) was the challenge, and I have a working proof of concept. It's not perfect (I need to work on some minor formatting issues, and I'm not sure if the Scheduled Task will run when I need it to), but the failure of this project (i.e. blogging regularly) will not be a failure of this system - after all, I can always blog "manually" - but from a lack of content.
I call this the content problem. I've got some solutions, which I'll list in a separate blog. (See the tricks I have to use to extend my meager portion of content?)
posted by FlyingSheep @ 9:13 AM
0 Comments:
Post a Comment
<< Home