I see a lot of negative comments here. The point being missed is doing something is better than doing nothing. Yes he might not have ended up finishing with th

I see a lot of negative comments here. The point being missed is doing something is better than doing nothing. Yes he might not have ended up finishing with the web server what he started. But I'm pretty sure he did NOT set out to build something that would be a product or a startup someday. He set out to do something repeatedly, so that he becomes good at it and uncover new problems that are interesting to keep working on. None of this relates to productivity or writing the best code possible. You start out with something; end up finding pleasure in doing something else; then you keep on doing it until you've written enough code to know where you stand and keep improving. The take away for me is this. As for me it always was the chicken to the egg problem. I need to be keep working to find new problems. However, I need to start somewhere with a problem that I don't know yet. Trying to rewrite existing stuff was something I'd do to learn new tech. Now it hits me that I could use the same, to keep my fingers stuck to the keys. I'd love to read more writes like this. Sharing how you overcame something is noble. It helps more people than you anticipate.