If you’re jumping into a new


SUBMITTED BY: tanishqjaichand

DATE: Jan. 26, 2017, 3:18 a.m.

FORMAT: Text only

SIZE: 3.1 kB

HITS: 874

  1. James Gill has a good overview of How bad features are born:
  2. Most importantly, does this feature deserve to exist? Why are you working on it?
  3. If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve. If you’re jumping into a new feature because it seems like “it wouldn’t be too hard to do” that’s great, but does it actually...
  4. [continue reading...]James Gill has a good overview of How bad features are born:
  5. Most importantly, does this feature deserve to exist? Why are you working on it?
  6. If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve. If you’re jumping into a new feature because it seems like “it wouldn’t be too hard to do” that’s great, but does it actually...
  7. [continue reading...]James Gill has a good overview of How bad features are born:
  8. Most importantly, does this feature deserve to exist? Why are you working on it?
  9. If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve. If you’re jumping into a new feature because it seems like “it wouldn’t be too hard to do” that’s great, but does it actually...
  10. [continue reading...]James Gill has a good overview of How bad features are born:
  11. Most importantly, does this feature deserve to exist? Why are you working on it?
  12. If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve. If you’re jumping into a new feature because it seems like “it wouldn’t be too hard to do” that’s great, but does it actually...
  13. [continue reading...]James Gill has a good overview of How bad features are born:
  14. Most importantly, does this feature deserve to exist? Why are you working on it?
  15. If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve. If you’re jumping into a new feature because it seems like “it wouldn’t be too hard to do” that’s great, but does it actually...
  16. [continue reading...]James Gill has a good overview of How bad features are born:
  17. Most importantly, does this feature deserve to exist? Why are you working on it?
  18. If you’re embarking on a new feature primarily because you’ve seen a competitor release something similar, then you probably haven’t thoroughly considered or even identified the problem you’re trying to solve. If you’re jumping into a new feature because it seems like “it wouldn’t be too hard to do” that’s great, but does it actually...
  19. [continue reading...]

comments powered by Disqus