A Texan Ex-Pat’s Brisket Rub

Unable to find decent Texas BBQ in Washington that was not outrageously expensive, we bought an electric smoker. Why electric you ask? Its easier to operator and doesn’t require constant attention. This makes us much more likely to use it. Already I’ve smoked three briskets and two pork picnic roasts for pulled pork. While the rub for the picnic roasts we’ve been perfectly content with Mike Mills’s Magic Dust Rub, brisket has taken some experimentation.

We started with a rub created by Dr. Jeff Savell, of Texas A&M’s Meat Science Department and organizer of the Texas A&M BBQ Camps.

However we found the amount of Cayenne to be overpowering and the brisket’s flavor to be lost in the hear. So we did some experimentation and found a rub we absolutely love.

Paul’s Brisket Rub


  • Kosher Salt – 4 tbsp
  • Paprika – 6 tbsp
  • Coarse Ground Pepper – 2 tbsp
  • Fine Ground Pepper – 1 tbsp
  • White Pepper – 2 tbsp
  • Onion Powder – 2 tbsp
  • Garlic Powder – 2 tbsp
  • Brown Sugar – 2 tbsp (packed)


  1. Combine all ingredients into a reusable storage container. Close and shake until combined.
  2. Dry brisket with paper towel and place in a baking pan (I prefer glass) large enough for the brisket to sit flat with fat side down.
  3. Shake about half the rub on the brisket.
  4. Rub spices into the meat, making sure to get the edges.
  5. Flip the brisket so the side with the fat cap is up.
  6. Shake remainder of run on the brisket.
  7. Rub spices gently into the meat, making sure to get the edges. The fat area will require less rubbing than the muscle itself.
  8. Cover in plastic wrap and refrigerate for 8-12 hours.
  9. Place fat cap side up in smoker with temperature probe in middle of meat.
  10. Follow smoker directions to smoke at 225F until internal temperature reaches 190F (On our smoker we have to set it at 240F to maintain the 225F temperature).
  11. Remove and place on cutting board for 30 mins.
  12. Slice Brisket against the grain.

Paul’s Texas Chili

I made Chili tonight and it is pretty awesome. I based my recipe on Christine Knight’s award-winning recipe. The major difference is I used two kinds of Tabasco instead of the whole Jalapenos and I forego the Sazon Goya (it is chock full of MSGs and only really added Coriander to this mix).


1 lbs 80% Beef
1 eight oz can tomato sauce
1 tsp Beef Base
1 tsp Jalapeno Tabasco
1 tsp Chipotle Tabasco
6 tbsp Chili Powder
2 tbsp Onion Powder
1/4 tsp Cayenne
1 beef bullion cube
1 chicken bullion cube
2 tsp Granulated Garlic
1 tbsp Cumin
2 tsp Paprika
1/2 tsp White Pepper
1/2 tsp Coriander
1 tbsp Crushed Red Chili


  1. In a chili pot over medium heat, sear meat.
  2. Add tomato sauce, beef base, and about cup and a half of water. Pour in Tabasco sauces.
  3. Cover and cook for 30 minutes, adding water as needed.
  4. Add 3 tbsp. chili powder, granulated onion, cayenne, beef bouillon, and chicken bouillon. Stir, cover, and simmer for 1 hour, adding water if mixture gets too thick.
  5. Add remaining chili powders, granulated garlic, cumin, paprika, pepper, coriander, and more water if necessary. Cover and simmer for 30 minutes.

Serves 8.

Why should we teach CS to middle schoolers?

This is kind of a rhetorical question as I really am not asking it as I think we should. Computer Science Education research has shown that early exposure to computational thinking can affect long term student career choice. While this can be positive as shown by work by the late Randy Pausch, this can also be a negative. If good, interesting instruction such as Pausch’s work with Alice, the excellent work on Robotics in CS0, and those who do mobile dev with App Inventor then students leave excited about Computer Science and hungry for more. But imagine a CS0 or CT class where the instructor is dry, disinterested and assigns boring assignments. You could hurt the outcomes more than a good class improves them. This says to me that the real issue is not coming up with pre-packaged courses as is common in the CSE literature, but to actually get the teachers excited and interested in the material so they can share their enthusiasm in their classes. Building teacher buy-in and commitment to creative education is the missing link in the CS0/CT movement.

So how do we train the teachers?  I’m proposing to the NSF that the answer is research experience programs. Bring teachers into a research center and have them conduct research while getting instruction on bringing CT to their own classes. This allows dissemination of ideas such as nifty assignments, and CT pedagogy while building their own excitement and appreciation for computational sciences.

Disruptive Pedagogy

After hearing Mills Kelly speak on pedagogy of disruption at THATCamp CHNM 2012, I’ve been thinking about how natural it would be to implement this in a Computer Science or Information Science context. There is ample supply of areas to draw from, The THATCamp movement, Mills Kelly’s own course on hoaxes, Sandy Stone’s programs in the Univesity of Texas’s ACTLab, Abertay University’s Ethical Hacking class, the MIT Hacker Club, Collegiate Cyber Defense Competitions and Patrick Burkart at Texas A&M’s Communication and Technology class.

The vision for a Disruptive Technology course in the CS or IS context would be to teach students how to think creatively and subversively about technology to flip the paternalistic role of tech they have been brought up on to show how technology is truly an open area that politics and philosophy are imposed on. How society shapes technology and how we can turn around and effect society via re-application of technology.

Bridging the Gap between the CS DL community and the LIS DL community.

This is starting as a repost of my THATCamp CHNM session post, I will add more to this in the future.

I’ve notice a disparaging trend at both the ACM/IEEE-CS JCDL conference and at THATCamps. Digital Libraries researchers from Computer Science have never heard of THATCamp and don’t really interact with the people who attend. Conversely people at THATCamp don’t tend to think of the ACM/IEEE-CS community when they think about what is going on in digital libraries, digital archives, and digital humanities.

In fact the 2012 JCDL conference just ended at GWU the day before THATCamp V started at GMU. Here were two groups of people with similar concerns, interests, and goals across town and unaware of each other.

This session is to discuss why there is fragmentation between the more LIS DL people at THATCamp/ALA/etc and the more CS DL at JCDL/TPDL/etc and try and discuss ways to bridge the gap and bring both groups closer together.