Here is my Bœuf bourguignon recipe that I adapted from this recipe. My guests seem to have appreciated it every time I made this dish over the years.

Ingredients

For 8 servings:
- 1 bottle of Cabernet Sauvignon or Merlot.
- 2 tablespoons brandy
- 2 onions, thinly sliced
- 2 carrots, chopped
- 1 sprig fresh parsley
- 1 bay leaf
- 1 clove garlic, crushed
- 10 whole black peppercorns
- 1 teaspoon salt
- 2 pounds cubed beef chuck roast
- 4 Tablespoon of Olive oil
- 1/4 pound bacon, cubed
- 2 onions, chopped
- 3 tablespoons all-purpose flour
- 1 tablespoon tomato paste
- 2 cloves garlic, crushed
- 1 (10.5 ounce) can beef broth
- salt and pepper to taste
- 4 tablespoons butter
- 1 pound fresh mushrooms, sliced

Directions

1. In a large bowl, combine the wine, cognac, onions, carrots, parsley, bay leaf, garlic, peppercorns and salt. Mix well and add the cubed beef. Cover and marinate in the refrigerator overnight.
2. The next day, strain the meat from the vegetables and marinade; reserve marinade. Dry meat with paper towels. Heat 2 tablespoons of the olive oil in a large tall pot over medium high heat. Add the meat and saute for 10 minutes, or until browned on all sides. Transfer meat to a separate medium bowl with a slotted spoon and set aside.
3. In the same pot, add the bacon and saute until lightly browned. Transfer the bacon to the bowl with the meat. Drain the pot and return it to the heat. Pour a cup of marinade into the pot to deglaze the pot, scraping the bottom to loosen up all the little bits. Return this liquid to the reserved marinade.
4. Heat some olive oil in the pot. Add the onion and carrot from the marinade, along with the additional onion that you’ve chopped, and saute for 5 minutes, or until tender. Transfer this mixture to the bowl with the meat and bacon, again using a slotted spoon, and return pot to the heat. Add the flour to the pot, combining with the oil and stir until well mixed and brown, about 2 minutes.
5. Now add the tomato paste, garlic, beef broth, reserved marinade and salt and pepper to taste. Bring to a boil and whisk to remove any flour lumps.
6. Now pour the meat and vegetable mixture into the pot and cook for 6 to 8 hours on low heat, stirring occasionally and adding water as needed. Season with salt and pepper to taste.
7. About 15 minutes before meat is done baking, melt butter in a skillet over medium high heat. Add the mushrooms and saute for 5 to 10 minutes, or until lightly browned. When meat is done, add the mushrooms to the meat mixture, stir well and let sit for about 15 minutes.

You can reheat the stew if you don’t finish in one sitting. It only gets better over time.

Houston is a huge metropolis but sometimes, you encounter something special while cruising residential neighborhoods on the way to the morning coffee break.

Back in 1989, when I got my first PC, an 8086, I became obsessed with fractals and more specifically, the famous Mandelbrot set, along with 3D simulated mountainous range. At the time, I was programming using an OOP version of Borland Turbo Pascal and I created multiple DOS applications to generate, visualize, and marvel at those mathematic constructs. I had to take photos of my screen since my dot-matrix printer was not up to the task. When I took the computer science exam as part of the tests to enter the School of Geology, I brought with me pictures and programs on 3″1/2 floppy disks and it helped me get a good grade.

My favorite mathematician, Benoît Mandelbrot died at age 85. He was quite an inspiration and part of the reason why I am doing what I am doing today. In the video below, Professor Mandelbrot, discuss some of his work.

Tonight, I watched the documentary entitled “Babies“.

I am not into documentaries, and even less into babies. This is a departure from my usual movie watching habits. I am not a parent and this child thingy is really foreign to me. However, it is amazing to see four babies observe and discover their body, and the world around them from the time they are born to the time they reach their first birthday. It is also fascinating, to see, from a toddler perspective, four very different places on the planet: Namibia, Mongolia, Japan, and the United States of America.

Living in Houston, it is easy to forget that not every Homo sapiens have access to running water, sanitation, medicine, and all the commodities I generally take for granted.

Babies is a very refreshing documentary that does not focus, as it is too often the case, on a problem in our societies, but more on the common thread that links all members of our species.

In this short article Rob Diana argues that developers are responsible for producing working code and that to do so, it is imperative that the code gets tested and exercised through unit tests.

This is perfectly reasonable and most developers I worked with don’t have any issue with unit testing as defined by Wikipedia as long as the level of automation is low or non-existent. The Wikipedia article on unit testing explains that “[unit testing] implementation can vary from being very manual (pencil and paper) to being formalized as part of build automation.”

However, a major gap exists between exercising the code through manual or semi-automatic tests and writing automatic tests to verify continuous integration builds. Of course the latter produce higher quality software in the long run but this gap prevents some teams from reaching a higher level of code quality while minimizing rework (i.e. higher productivity).

Implementing automated unit tests is not simply a technical exercise. It is also a complex problem that requires a sophisticated and coordinated effort among developers accompanied by a culture change where developers and other stakeholders:

• treat unit testing code with the same level of respect as the rest of the application (this code may not end up on the server or the user’s desk put it is an essential element in minimizing defect escape rate);
• accept that an automated build is successful, if and only if, all the associated unit tests passed.

This combination of cultural and technical changes is essential to a successful and full-scale automated unit testing implementation.