3 ms·
Just because something is used internally doesn't mean the product manager is going to prioritize fixes for internal bug reports. Testing internally does not m
by jrockway 14y ago
Just because something is used internally doesn't mean the product manager is going to prioritize fixes for internal bug reports. Testing internally does not magically add more programmers to the project.
- jere 14y agoThat's certainly true, but then dogfooding seems completely pointless if you're not going to use it to make your product better.
- jrockway 14y agoIt just means that software engineering is difficult even with many testers.
- xtdx 14y agoFixing some of the bugs you find internally doesn't mean you need to fix all of the bugs you find internally.
- sliverstorm 14y agoHow about the part where you don't pay licensing to other companies? In other words, if you're developing the software anyway, may as well use it.
- jere 14y agoSure. My first instinct is to say that's a small concern, but they do have 100k employees. Sorry, I was introduced to "dogfooding" in Dreaming in Code. I believe there was even a chapter named after it and it was a pretty big deal about how you dogfood to maintain quality. So when I hear the term that's what I assume is implied.
- jmspring 14y agoWhile true, "the PM may not prioritize fixes", a big aspect you are missing is, someone internally with a problem has access to a direct communication line with said PM, his peers, superiors, etc. For most day to day usage issues, dogfooding is a great way to hammer out issues. Will they find issues with every use case? No, but they will find some. Also, generally, the more diverse and large the organization, the more use cases will be dogfooded (assuming the bulk of the org is encouraged/required to do so). When you are talking a company of 90k+, encouraged dogfooding will hit a lot of different use cases.