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.)
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.)
I don't think you can repurpose your project as a learning experiment... even if you learned, what was the goal?
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.