Archive
Monthly
Go
|
|
DNN Blog
Jun
28
Posted by:
cathal connolly
6/28/2006 4:00 AM
Sometimes you'll see us use the phrase 'eating our own dogfood' or 'dogfooding' when we're testing a new DotNetNuke build. Odd though this phrase may seem, it's not uncommon in the IT industry, in fact Microsoft are often credited with inventing it. Wikipedia have a good description of it's purpose and benefits, but in DotNetNuke terms, it's refers to us upgrading the dotnetnuke.com site to test a proposed release.
You may be wondering how come if we have so many testers, coreteam members, project members and benefactors who've looked at a proposed release, we still need to dogfood on Dotnetnuke.com, but time after time we find issues that only show up clearly on sites with a large load e.g. lots of concurrent users, lots of files etc. We're dogfooding at the minute, and it's already uncovered effects that the average user would be unlikely to detect e.g. this describes one that became apparent with our 300,000+ users, which would have not been noticed in most dotnetnuke sites, as few have such a large membership.
Whilst in the short-term this can cause a little bit of shared pain (site slowdowns/odd issues), in the long-term it benefits us all.
|