Recursive dogfooding
Dogfooding:
To say that a company "eats its own dog food" means that it uses the products that it makes.
This happened a few days ago, I just finished adding a new feature to SvnBridge, and I was ready to commit. Now, I am very used to Subversion, so it is fairly obvious that I like keep using that. Except that SvnBridge is on CodePlex, which uses the TFS backend.
If only someone would develop a bridge between the two...
SvnBridge is mature enough that you can use it for most operations, so I am using SvnBridge in order to commit SvnBridge.
But wait, that is not what the story is about. The commit has failed with some obscure error, and it was obvious that the fault was in SvnBridge.
What I found myself doing was debugging SvnBridge committing the SvnBridge's own source code. That was.. an interesting experience. And just a tad nerve wreaking.
And that, my friends, is what I call dogfooding.
Comments
Wow. You really like to live at the bleeding edge! :)
Dude, that's the most awesome thing I've heard all day.
Personnaly, I always use NDepend to check quality, structure and evolution of the code base of ...
...NDepend
I agree, dogfooding is an interesting experience. The more rewarding is when you add a facility requested by other users, and then you end up using intensively this facility.
Hahhaha recursive dogfooding. Good one.
I once write a C compiler specifically for the DEC Alpha "supercomputers" of their time.
Since I wrote the C compiler using C, it was very entertaining to see that the compiler could compile its own source.
The dog food is delicious.
Comment preview