In this episode, Coté and Charles talk about an expansive range of topics, mostly non-technical. Charles tells us about going to Minneapolis and getting some cold something cut coffee, then onto an extended conversation about Transformers and the toys, Charles tell us about his newbie study of Haskell, and then we discuss the question “does having a toaster oven make you white trash?”
An audio only version is available as well.
uncut cold compress? are you sure?
google has some interesting patent hits for those terms, but nothing remotely relating to coffee…
http://www.google.com/search?q=uncut+cold+compress
Okay guys, give us AT LEAST 2 minutes of lipsync action with the ladies. It would add an extra dimension to the podcast. And you already know that podcasts with ladies in it tend to have a significantly larger audience. Add some commercials à la Twit and voilá: profit. So you can make some money off off the ladies to make up for all those expensive gifts you bought them. So you see: they cannot refuse or else no more Prada bags. Yuh!
Hey, the Acadia Cafe is where the local Ruby user group meets (ruby.mn). Check it out next time you’re in town.
And uh yeah, it’s cold press, and it does make a fine, fine iced coffee. Although uncut cold compress is really funny. Looking at those Google results, it seems that Coté isn’t that far off. Heh.
This was a pretty good podcast from 13:00 in when Charles finally finished that jar of shit with ice rattling around in it. Sheesh.
As usual, a fine podcast. As a Twin Citizen I’m glad that Charles had a good time. You guys seem to know about everything and have been exposed to all kinds of shit. Ether one of you worked with a “Universal Data Model”. There are a couple of guys on my team that are pushing this. The book is by Len Silverston. The jist of it seems to be reusable components through subtyping. Also a lot of lose associations. It seem to make the data model pretty abstract, which I’m not so sure is that great.
@Bob: I haven’t heard about universal data models, but looking at their site it looks like just a bunch pre-packaged models. I guess it makes sense to have those things as a library that you can reuse, in the same way that any library is useful.
Off the top of my head, concerns would be 1) integration with your application code: are there tools that can autogenerate an api into your data model ala ActiveRecord or Hibernate 2) how hard is it to query a really abstract, loosely coupled data model 3) performance: if you’ve got crazy-loose relationships, sometimes this can confuse your mapping tool, causing it to run really inefficient and practically impossible-to-read-and-debug-because-there-are-like-39-joins SQL.