Skip to main content

Eating my dog food

I was carrying home a bag of dog food recently for my dogs when the neighbour made jokes about eating dog food and the coming recession. I think recessions are like winter - you know it'll come eventually, but it's hard to imagine in the depths of summer.

But my point is really about dog food, and eating it. The woman who sells me Nutromax claims the salespeople eat it to prove it's good. As a computer-geeky guy, I'm familiar with the expression "eating your own dog food" to mean, using your own software. I just looked it up on wikipedia and discover that the original idea did indeed come from an advertisement about dog food, and that it's now used mainly about software. Here's what wikipedia says about the idea:


Using one's own products has four primary benefits:

1. The product's developers are familiar with using the products they develop.
2. The company's members have direct knowledge and experience with its products.
3. Users see that the company has confidence in its own products.
4. Technically savvy users in the company, with perhaps a very wide set of business requirements and deployments, are able to discover and report bugs in the products before they are released to the general public.

A disadvantage is that if taken to an extreme, a company's desire to eat its own dog food can turn into Not Invented Here syndrome, in which the company refuses to use any product which was not developed in-house.

So, that's my introduction to say that I've finally created myself a Drupal site for my business. It had previously been hosted at googlepages, because it was free and easy and I thought Web 2.0 was cool (just kidding about that last one). Also because I didn't have a server or domain name, because I thought I'd just be a consultant.

After three years, I'm still working as an independent consultant. What I've changed is:

  1. I've got my hands full with Drupal and CiviCRM for Canadian non-profits. I may do some projects outside that scope, but I've now got a more specific niche.
  2. I'm not just a "consultant", but a full service shop - i.e. websites from beginning to end, even mail. I use the "keep it as simple as possible, but no simpler" rule, and working on other people's servers turned out to be more complicated than running my own server (no, not in my basement, I use a commercial Canadian service for the hardware and network).
  3. I'm committed to remaining "agressively small" [credits to Mark Surman and Phillip Smith]. There's an assumption in the technical world that you have to "grow" your business to be competitive (yes, not just the technical world). I think that ideology is wrong in a general way from economic and environmental points of view, but specifically wrong for most Drupal websites. Big shops with layers of management do not make better websites, and certainly not cheaper - the big shops are not driven by real 'economies of scale' but by delusions of money and/or fame by the owners. You know who you are ...

That's my story so far, now go visit my new site.

Popular posts from this blog

Varnish saves the day, in unexpectedly awesome ways.

Four and half years ago, I wrote a blog post about Varnish, a 'front-end proxy' for webservers. My best description of it then was as a protective bubble, analogous to how it's namesake is used to protect furniture. I've been using it happily ever since.

But last week, I got to really put Varnish through a test when the picture here, posted by Fair Vote Canada (one of my clients), went viral on Facebook. And Varnish saved the server and the client in ways I didn't even expect.

1. Throughput

Varnish prides itself on efficiently delivering http requests. As the picture went viral, the number of requests was up to about 1000 per minute, which Varnish had no trouble delivering - the load was still below 1, and I saw only a small increase in memory and disk usage. Of course, delivering a single file is exactly what Varnish does best.

2. Emergency!

Unfortunately, Varnish was not able to solve a more fundamental limitation, which was the 100Mb/s network connection. Becaus…

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: http://tools.newmode.net/

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

1. Click to Call: http://www.davidsuzuki.org/blogs/healthy-oceans-blog/2016/11/to-help-protect-canadas-oceans-weve-made-it-easy-to-call-your-mp/#newmode-embed-4-266

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…