Q: Should I eat all my bacon at once, or should I space it out during the day?
A: Different programmers have different reactions; Some people require quite a lot of bacon to get the initial bacon rush, but once they get it, it lasts all day. Others get a short rush from a few bites of bacon. Experiment to see what works best for you.
Q: I’m a vegetarian. Can I use vegetarian bacon?
A: No. Bacon driven coding only works on real bacon. It’s not called tofu driven coding.
Q: What about sausage?
A: Some people are experimenting with sausage to see if they can produce similar results. If you have any success with this, let us know.
Q: Don’t the two answers above kind of contradict eachother?
Q: Can you use bacon driven coding in a non-object oriented framework?
Q: Can I use bacon driven coding with legacy code?
A: Yes! Unlike other strategies, you can gain the benefits of bacon driven coding on your existing code base. No more clunky test retrofits and refactoring, or building UML Models to match the existing system — Just add bacon and go.
Q: What about the health risks?
A: Eating large quantities of bacon can pose health risks. Weight gain is the most likely, but other problems have been reported. Overall, however, we believe that the stress reduction gained by all the time saved through bacon driven coding should mitigate the risk for most people. After all, when you finish a week’s worth of work on Monday afternoon, you have lots of time left in the week to spend exercising to reduce your health risks.
Q: Does bacon driven coding work well with pancake driven design, orange juice driven requirements, or toast driven testing?
A: Some practitioners have reported success with this combination, leading them to laud the virtues of a whole-lifecycle process of “breakfast-driven development”. While we are excited about the possibilities of this development, we don’t want to overpromise, so we stick to the reliable formula that so many have had success with: bacon leads to better code.