There is a time in most coders' lives when things get coded to confirm a) mastery of the implementing language b) feasibility matched estimate c) coder is worth

There is a time in most coders' lives when things get coded to confirm a) mastery of the implementing language b) feasibility matched estimate c) coder is worthy. This is a healthy thing to do, but also to grow out of. These days I work in idea rather than code. I plan things I will not execute to see what they look like on paper. I scheme on things I will not put my personal time into because I can't afford it. Some of my plans are getting good enough to try on other people or in business. But I still experiment for the learning value. This doesn't make it a waste, or make me lazy. But if I don't ever get better and get out of this mode, I am indeed wasting my time. HTH.