This advice has been my experience building my app. I have a CS degree, but I never did much programming after - I went more into product management.
However, now that I am building my own app, I have forced myself to learn the entire stack (from Rails to JS and beyond).
I sometimes look at other people's code and compare what they did in 1 line, to what I did in a block of 10 lines and wonder when I will be able to write elegant code like that. But I have learned to console myself, that at the end of the day, for this first release, it doesn't matter what the code looks like. Just so long as it isn't slow and the user has a good experience (i.e. things behave the way they expect it to), then I am doing a good job.
The perfectionist in me hates leaving it like that (I want to refactor every chunk until it is completely optimized), but the realist in me knows that I only have X amount of time to complete.
Thanks for posting this, because now I don't feel like I am doing a major disservice to my users by programming like the n00b I am.
However, now that I am building my own app, I have forced myself to learn the entire stack (from Rails to JS and beyond).
I sometimes look at other people's code and compare what they did in 1 line, to what I did in a block of 10 lines and wonder when I will be able to write elegant code like that. But I have learned to console myself, that at the end of the day, for this first release, it doesn't matter what the code looks like. Just so long as it isn't slow and the user has a good experience (i.e. things behave the way they expect it to), then I am doing a good job.
The perfectionist in me hates leaving it like that (I want to refactor every chunk until it is completely optimized), but the realist in me knows that I only have X amount of time to complete.
Thanks for posting this, because now I don't feel like I am doing a major disservice to my users by programming like the n00b I am.