Skip to main content

Married!

Married….Yes, the rumors were true - Telene and I are now married! Holy cow! We both seem to have an afterglow following the wedding, together with a strong sense of how incredibly right and timely this is for both of us. The ceremony happened outside on the terrace at the Cliff House - a beautiful venue atop of San Francisco's never ending ocean beach. Our dear friend Donna conducted the ceremony with a graceful touch and purity. Even San Francisco's world famous fog was welcome (this may be a bit selfish - try wearing a three-garment tuxedo under the sun; I bet girls in open dresses had other things to say about the fog). The band performance was phenomenal, and the wedding reception lasted well over our original estimate. Which is a good thing, because we also managed to have a lot of fun along the way. Add the 2-night stay at the spectacular W hotel in SOMA that followed, with a pool and spa and unbelievable room service, and it's certainly going to be the weekend to remember. Next step to celebrate - is our honeymoon month in Thailand, but that's not until March 2007... Meanwhile, I am back at the Blurb's office, Telene's back at school and so it's back to life as we know it. Although I may have to stress test BookSmart software building our very own wedding book. And very special thanks to the relatives and friends, who made it out, often from far overseas, to witness our vows and the drinking that followed...

Comments

Popular posts from this blog

Car or Auto Make-Model-Year Database : For Breakfast

Make Model What?If you like me were tasked with loading a database of recent car makes/models/years, you would start by looking on the web and seeing if someone else just has it out there, readily available, hopefully for free, but perhaps for a tiny nominal fee.?If only it was that simple... I looked and looked, and couldn't find anything that would fit the above requirements. So I thought, who would know about US car models better than Kelly Blue Book? So I went on their site, and sure enough they have a javascript file that lists all known to them makes and models of used cars. Since the file is public, I figured it's not really "evil" if I scrape and parse it for my own benefit. Disagree? Have a better source? Then leave a comment.Anyway, to cut the long story short, I'm hoping to save a day or so to someone else who may, like me, be looking for this information. The ruby module shown below retrieves and parses the javascript from KBB site into a Ruby da…

Why I Like PostgreSQL

Today I gave a short presentation at work about PostgreSQL, and why I much prefer it to MySQL.

PostgreSQL vs MySQL: Eternal Battle
I may be misreading this, but it seems that there is a recent trend within startups to move away from MySQL, probably thanks to folks like Heroku on one side (who use PostgreSQL to the extreme, and help and contribute to it's development), vs folks like Oracle on the other side, tainting the "open source pureness" of MySQL :)

At my work we currently use a mid-sized MySQL 5.1 Percona instance, which is holding up quite well I must admit. Both PostgreSQL and MySQL have definitely converged to cover most features that people want, but my leaning is still towards PostgreSQL. I just agree with it's focus on data integrity, recovery, constraints, extensibility, while some of the early decisions in MySQL's design do not agree with me at all (like truncating long strings, 1/0 instead of booleans, ambiguous group by, etc). I think that data …

On Ruby on Rails with PostgreSQL, and Acts as Paranoid

Back a few years ago I was researching differences between PostgreSQL and MySQL databases, and chose PostgreSQL because at the time it supported foreign key constraints and many other fantastic SQL extensions that make developer's life a lot easier. Today I am sure MySQL is just as functional as PostgreSQL, and it does appear to be a more popular choice as the Rails DB than MySQL. I still prefer PostgreSQL, it just feels more natural to me coming out of Oracle background, so I am probably biased (who isn't?) Anyway, in the last year and a half or so, I've been writing Rails apps that use PG-based databases and found a few random tricks I'd love to share here. Opinions differ here, but just like accountants like the ancient double entry accounting system, I personally prefer a double validation system - where Rails validates my objects before/after updates, but the database double checks this using proper constraints. Rail's validation system is very robust and ext…