Re:Ask HN: Are you embarrassed by your failed projects?
by TamDenholm on Thursday October 28, 2010 @01:23PM
(#1843850)
I think if you're not embarrassed by the code you wrote ages ago then you're not improving.
Re:Ask HN: Are you embarrassed by your failed projects?
by mikerg87 on Thursday October 28, 2010 @02:39PM
(#1844267)
The code I wrote sucks. The code I am writing is cool. The code I am going to write rocks!
Re:Ask HN: Are you embarrassed by your failed projects?
by mrlyc on Friday October 29, 2010 @02:33PM
(#1848392)
No, I don't think so. I'm still quite proud of the Vic-20 bulletin board I wrote 26 years ago that got me my first job as a programmer.
Re:Ask HN: Are you embarrassed by your failed projects?
by alanthonyc on Thursday October 28, 2010 @08:49PM
(#1845601)
I'm embarrassed by the code I wrote last week.
Re:Ask HN: Are you embarrassed by your failed projects?
by mattblalock on Thursday October 28, 2010 @01:15PM
(#1843797)
See this is based on the assumption that "you did it for the project" or "to learn and grow", but failure (for me) is based on goals and one's inability to meet them. If your goal was to "create a project", you have succeeded even in the face of "failure", unless you never created your project. Most of us, however, have goals: get 100 users, design a great user experience, play 45 shows in a band, get a record deal, get famous.
I don't think you can repurpose your project as a learning experiment... even if you learned, what was the goal?
Re:Ask HN: Are you embarrassed by your failed projects?
by rechtaht on Thursday October 28, 2010 @02:22PM
(#1844171)
I think you're right. I also think that's where the culture of learning is really powerful. You do need to set the expectation ahead of time that the real objective is learning or validated knowledge.
I have a company and we set goals, but our overarching goal is to learn. If we fail at meeting a metric there is always something to learn and take forward to the next attempt.
The only failure we define as a company is not setting your goals high enough to push yourself, or not taking your learning forward. That's how you build a culture that is willing to take risks. Defining failure as not meeting your metrics isn't productive.
Re:Ask HN: Are you embarrassed by your failed projects?
by aaronblohowiak on Thursday October 28, 2010 @02:20PM
(#1844149)
"No failure, only feedback." Now, you have to have a retrospective and really learn your lessons for this to work but it can be a very liberating mindset.
Re:Ask HN: Are you embarrassed by your failed projects?
by mattblalock on Thursday October 28, 2010 @01:16PM
(#1843803)
PS. I'm always embarrassed by the code I wrote ages ago as well... seriously, what I was I thinking?
If the project was a success, I did it for the project.
If it wasn't, I did it to learn and grow.
Either way, nothing to be embarrassed about.
(Am I embarrassed by the code I wrote 3 years ago? Now that's another story.)