Car insurance is a joke?

This is an old story.

About a year ago, I had someone who smash through my car's right side-mirror.  I called up NRMA and asked about their policy "if it's not your fault we won't charge you excess" which they were heavily promoting at the time, they informed me that I would lose my no-claim bonus for next year.

Which just means I'll pay the money later when I renew the insurance.

I ended up calling off the claim and just replaced my mirror from a second-hand parts store.

Mirrors aren't that expensive to replace, but I've had this insurance for 10 years and each year it's cost me about 10% of the cost of the car, if I totaled it.  In hindsight I don't think I needed car insurance at all.

Keith's birthday

Keith, my firstborn son, eh has been born.

Lina had some issues over the entire weekend leading up to the birth, but finally contractions started just past Sunday midnight, and baby came around 6:35am on Monday morning.

About 5 hours of labour, which we're really happy about - we both know we're very lucky to have a relatively short labour.

Labour is terrible. 

But the joy when the baby arrives is indescribable.

I can't stop thinking about my beautiful baby.

So in two days, I've managed to:

1. Spam everyone about my baby, emailed, blogged, posted in every freaking forum I visit
2. Take lots of Keith's pictures... but he appears to be sleeping whenever I take pictures!  In ALL of them!!  Sneaky baby.
3. Sneak food into hospital for Lina
4. Clean up Keith's poo twice
5. Clean up Keith's wee once
6. Ate all of Lina's biscuits, and cheese
7. Had Keith mistaken me for mum and try to extract food from my chest - no son, man and woman are different
8. Got kicked out of hospital for staying there past visiting hours - yes, I don't understand why hubby can't stay...
9. Oh and I managed to upload Keith's first YouTube movie - I'm sure that'll stick around until he's old enough to watch it himself.
10. And I've fallen in love with Lina and baby all over again.  They are the two bestest thing to happen to me.

Tomorrow, we try to get the hospital to kick us out so we can get Lina and baby home (trying to get a hospital discharge).

Lina is missing her bed terribly.

A little bit of confession...

I'm scared Keith's grandma (Lina's mum) will try to do something different to what I want to do with Keith - (I think) she seems to think the best thing for Keith is a bottle of milk in his mouth at all times, just because that's how it's done in Indonesia.  I'm a bit worried.  I firmly believe in breast feeding and I'd rather Keith go a bit hungry so he has better appetite for breast feeding, rather than stuffing him with a bottle all day.

I know one of my nephews is picky about breast milk or formula (powder) milk.  I personally prefer if Keith have no such options.  It's breast milk or nothing.

Here are the links for sharing:

http://www.flickr.com/photos/52753426@N00/sets/72157605014742716/

This is what I would do if I ever quit IT

1. Hire out accessible office building balconies in Sydney, or park space
2. Get a bunch of beach chairs
3. Put up lots of beach umbrellas (for the sun and rain?)
4. Hire out the beach chairs for lunch and nap afterwards

• Pump up lots of beach balls for decoration (and to keep the kids busy)
• Complementary sun block if they don't want to stay under the umbrella - though sun burns during lunch probably is great advertising.
• Soothing beach sounds and music

Premium service

• Martini, Coke, Tea
• Clean beach towels for hire.
• Alarm clock fitted to the previously mentioned beach chairs
• Wind breaker walls - I imagine on top of office buildings in Sydney the wind will be quite big

The company will be called "5 Minutes to Beach Paradise"

The workplace Wiki

I'm a pretty strong believer that anything related to the development should go on the project Wiki.

Most people will agree on a few obvious topics:

• Rules & standards
• Design decisions (which typically turns into documentation of some sort)
• Setting up the environment
• Development processes

I prefer if the Wiki was more a 'place for everybody'.  Because the goal is that you want to drive your team to firstly Read the Wiki and then secondly to Update the Wiki. 

This means it needs topics that are less hardcore and has a more personal touch:

• Bus / Train timetables - tips for getting home on time
• Good restaurants near work - with Google/MSN Maps integration
• I love this one - a Quotes page of who said what
• Office Foosball / Table Tennis championship scores (and champions)
• Team money jar summary
• Breaking the build fine
• Late/absent for scrum fine
• Swear jar
• Playing foosball / table tennis out of legal hours
• Wearing jeans to work (usually this goes to some sort of charity though)

When someone on the team has a problem, what do they do

1. Yell out help - can anyone help me?!
2. Or they search the wiki

On most projects, #1 happens all the time, and #2 pretty much never happens.  Which is a pity.

Enterprise security policy

I received an email reminder from the client recently.

"Please don't plug external/personal laptops into the corporate network, this is against the enterprise security policy".

This blog is not a criticism of this security policy.  In fact, I tend to agree with the gist of this security policy.  It is always better to tell your less-computer-savvy users to avoid plugging in potential trouble into the network.

However, this does reminds me of a few things I wanted to rant about:

1. What about things like: External Hard Drives, USB sticks (and by extension, iPods or digital cameras)? 

They can transfer viruses too.  There was a news just this January where the USB digital picture frames many people got for $50 from Best Buy for their grand dad for Chrismas, and it was infecting their PCs.

http://www.news.com/8301-10789_3-9843574-57.html

Personally I think the network must be smart enough to detect virus troubles and drops the device from the network automatically, in a corporate environment, this goes for both "internal" as well as "external" machines.

Enterprise Security Policy by limiting who can or can't plug into the network is extremely naive, and possibly only give a false sense of security.  I sincerely hope there's a second line of defense on the network beyond just this policy.

2. Licences on development machines

For many years, I do work on a laptop with all the tools already installed, licensed and configured correctly.  So when I showed up at a new client/project I'm ready to go on day one.  Trouble is, many clients have a similar requirement in not allowing external machines to be used on the network - usually that's a set back for development time with lots of "develop on laptop", "copy over on USB stick", "test on client network"...  rinse and repeat.  This is a workable solution, but it is time consuming and still requires a basic setup on the client's development computer (at least VS.NET)

I thought there are a lot of parallels between a consultant vs say a plumber.

Plumbers shows up at the project with their own hammer.  The client doesn't have to buy a hammer for the plumber.

If a consultant shows up at the project with their own laptops.  The client shouldn't have to buy a new laptop (or the tools on it) for the consultant. 

What happens though, when the client won't let the plumber use the plumber's own hammers on his sink?  How can the plumber do his work?

Oh by the way we're still waiting for a few more licences for Resharper.