3 ms·

Thanks! Iteratively improving and adding features seems the most natural way how a software matures or ‘becomes complex’. I guess I just have to start building

• aynyc 7y ago
  Your first step should be avoid complexity. Reject features (big or small) that don't add value to the system. And if you must add feature, try to make it as specific as possible. Generic features tend to get abused. I personally don't like it, but other do love it.
  • rochak 7y ago
    I agree. Too much generic features end up becoming abstract and make it difficult to find what the original purpose was.
  • godshatter 7y ago
    I would add to this that you shouldn't be afraid to refactor when you hit a wall where you can't add the feature you want to add because of the way the other features structured your code. Better to take the time to modify the basic structure a bit to make it work than to try to kludge something together to sort of make it work. You'll find that doing it right allows other features to be added that you haven't thought of yet. If you somehow force it to sort of work, you'll end up doing that for a lot of other features, too.
    • rochak 7y ago
      Now that I look back, that is how I have approached developing systems and it certainly makes a lot of sense.