6 ms·
1) You just start coding. 2) You code everyday. 3) All the other things you did? You do those after your prototype is done. After you have this rhythm you rea
by 4ydx 12y ago
1) You just start coding.
2) You code everyday.
3) All the other things you did? You do those after your prototype is done.
After you have this rhythm you realize you start to need goalposts. Make them small. Don't think for hours about how it might affect the rest of your code. Just find a goalpost (as small as possible without making it trivial) and do it.
Really the things you listed in your blogpost are totally unnecessary and are, frankly, severely minor in comparison with the actual doing-of-the-project in the larger scope. It doesn't matter what language you use as long as you are familiar enough with it to get-stuff-done. So just stop trying to build a new project with multiple sets of new tools. At most have one new tool when starting a new project. Any more is really counterproductive. As a side note, the fact that you installed linux and described it as being "for the coolness factor" really makes me wonder though. There, quite seriously, are no other options for a small company/individual developer.