I had sug­gested that my com­pany use Google Cal­en­dar to pub­lish events. It’s easy, it can be made pub­lic and share­able, and it beats fig­ur­ing out how to pub­lish an Outlook/Exchange cal­en­dar on the web. (From what I’ve read about Google Cal­en­dar, you can pub­lish mul­ti­ple cal­en­dars indi­vid­u­ally con­trol­ling the level of pri­vacy and publicity—ooo, maybe we can migrate away from Exchange…) Yet, the coolest part about Google Cal­en­dar is that you can embed it in your web page using an iframe which Google pro­vides a handy-dandy con­fig­u­ra­tor to gen­er­ate the HTML. The worst part about Google Cal­en­dar is that you embed it in your web page using an iframe.

(more…)

Ruby’s beauty is often attrib­uted to its terse­ness. How­ever, there are times when you need to be really explicit in order to coax it to do your bid­ding. For exam­ple, a Rails form helper needs a bunch of paran­the­ses and curly braces in order to be a named ele­ment. Which makes sense, as :id can rep­re­sent a Rails (ActiveRe­cord) object ID or a DOM ele­ment ID. The Ruby punc­tu­a­tion removes such ambiguity.

(more…)