code every day: writers say "write every day" reduce scope: similar to "release early, release often", "iterate", it's always valuable to consider what is impo

code every day: writers say "write every day" reduce scope: similar to "release early, release often", "iterate", it's always valuable to consider what is important and what is important (how can you tell? that a feature exists is more important than some quality of that existence: being easy-to-use, fast, efficient, correct for all cases, flexible, general, reliable - all those things you care about!), how can you perfect something before you know what's wrong with it? (e.g. maybe you misunderstood the problem). I think releasing often is harder for commercial projects (who would pay for something incomplete? maybe they will if there's promise in the project, and they are really concerned about a problem it can solve: the value of code comes from user situations, not the code). I should try this. What's the worse that can happen? Nothing (i.e. it's ignored).