Skip to main content

My garage rebuilding project

  I've been rebuilding my old garage for the past two weeks. When we bought our house a year ago, it was described as a "tear-down", and after a year of living here I finally understood why. I kind of liked the falling down look, and it didn't seem to interfere with it's functionality (i.e., keep the car safe, store lots of junk).

But then I noticed it was leaning a lot, and it turned out it had been built without a foundation, just the two by fours sitting on dirt. It was probably at least 50 years old (maybe as old as the house, which was built in 1915), and about 20 years ago an electric garage door had been installed, and at that time a few extra 2 x 4's had been nailed in so that the opener didn't bring the whole thing down...

Anyway, it was a small garage, very dark, falling down, and there was about 2 feet on either side of it to the neighbours fences that was just a nice little habitat for rats and weed trees. Aidan went to a camp this summer at a nieghbour's house and they'd turned their garage into this neat art space by putting clear plastic corrugation instead of a roof on garage-like building.

 Posted by Picasa


Anonymous said…
Where is the rest of your garage story. I am interested in hearing what you did because my garage seems to be in a similar state.
Alan Dixon said…
It's finished, or at least as finished as such projects ever are. My only regret was that I used the cheaper roofing, which hasn't weathered very well. I really like that I can keep my barbeque back there and use it all year, and I've got a great little tool section as well.

Popular posts from this blog

What to do in the age of Trump?

Well, that's the question of the day. If you're part of an organization that does advocacy work, rather than waiting to see what happens first, might as well get yourself ready, even if the details are sketchy still. Here's one opportunity that's ready for you now, message courtesy of Steve Anderson of OpenMedia.

OpenMedia, David Suzuki Foundation, SumOfUs and a range of other organizations are supporting a new shared set of civic engagement tools.

Vancity Community Foundation is providing some support to subsidize some of the cost of the tools to select values-aligned organizations that sign up before February 28th.

Interested? You can learn more or book a demo from here:

Here's some live examples of the tools you can take a look at:

1. Click to Call:

Check out this video of David Suzuki's d…

Me and varnish win against a DDOS attack.

This past month one of my servers experienced her first DDOS - a distributed denial of service attack. A denial of service attack (or DOS) just means an attempt to shut down an internet-based service by overwhelming it with requests. A simple DOS attack is usually relatively easy to deal with using the standard linux firewall called iptables.  The way iptables works is by filtering the traffic based on the incoming request source (i.e., the IP of the attacking machine). The attacking machine's IP can be added into your custom ip tables 'blacklist' to block all traffic from it, and it's quite scalable so the only thing that can be overwhelmed is your actual internet connection, which is hard to do.

The reason a distributed DOS is harder is because the attack is distributed from multiple machines. I first noticed an increase in my traffic about a day after it had started - it wasn't slowing down my machine, but it did show up as a spike in traffic. I quickly saw that…

CiviCRM's invoice_id field and why you should love the hash

I've been banging my head against a distracted cabal of developers who seem to think that a particular CiviCRM core design, which I'm invested in via my contributed code, is bad, and that it's okay to break it.

This post is my attempt to explain why it was a good idea in the first place.

The design in question is the use of a hash function to populate a field called 'invoice_id' in CiviCRM's contribution table. The complaint was that this string is illegible to humans, and not necessary. So a few years ago some code was added to core, that ignores the current value of invoice_id and will overwrite it, when a human-readable invoice is generated.

The complaint about human-readability of course is valid, and the label on the field is misleading, but the solution is terrible for several reasons I've already written about.

In this post, I'd like to explain why the use of the hash value in the invoice_id field is actually a brilliant idea and should be embrac…