Weeknight Meal: Sticky Soy and Garlic Meatballs

Posted on by
Reply

For most of us weeknight cooking is what we get to do most so when I find a recipe that is exciting and fits into the 30 minute to 1 hour bracket that week night cooking allows I get excited.

This one is by a local Melbourne blogger, 3 Hungry Tummies. The photo is mine (taken on my iPhone 4s!).

The highlight of this dish for me is the water chestnuts that are finely diced and mixed into the meatballs. They add such a fantastic crunch and I was still enjoying that crunch the next day when I reheated them for lunch.

Recipes that work well reheated the next day get bonus points in my book.

Recipe: http://3hungrytummies.blogspot.com/2011/12/sticky-soy-and-garlic-meatballs.html

 

Seared Salmon

Posted on by
Reply

Seared SalmonI love doing complex meals and trying new recipes continually but like everyone I have a few standby recipes that I fall back on time and time again and I’ve just found a new one. One of the recipes I often do is one of Nigella Lawson’s super quick Mirin Salmon.

I got some beautiful salmon fillets from the Prahran Market yesterday morning in preparation for a quick and easy sunday evening but come Sunday evening there was a giant bowl of Waldorf salad left over from Saturday that needed finishing.

Deciding that the paring of Waldorf salad and Mirin Salmon was probably not the greatest onto the internet I went. Seared Salmon popped up as a paring with the salad in question and given the quality of the salmon I decided to investigate the best method.

A quick google popped up Gordon Ramsey doing his thing in a manner that seemed both easy and sensible but also with the usual flair that Ramsey provides. So here it is, the first half is a potato dish that also looks worth a try.

Book Review: In Our Hands the Stars By Harry Harrison

Posted on by
Reply

Harry Harrison - In Our Hands the StarsSo Harry Harrison is one of my favourite authors of all time. The Deathworld trilogy and The Stainless Steel Rat series, both by Harrison, are among my all time favourites. So it pains me to say I was underwhelmed by this book.

It starts promisingly enough, some super science with a bit of intrigue and mystery set during the cold war. But it fizzles out a third of the way through the book after an excellent and slightly surreal scene on the moon. Politics, spies and some poorly drawn characters take over and fail to engage. By the time the climax rolled around I didn’t care about the characters at all.

The book on Good Reads.

 

Slow CREATE DATABASE with PostgreSQL on Ubuntu

Posted on by
4

My new project (Relishment) is an opportunity for me to experiment with different technology. In this case I decided to switch to PostgreSQL from the RDMS I am familiar with MySQL.

So after struggling to learn the user management system in PostgreSQL, ”Ident authentication failed” was stumping me for a while, I finally got Django connected to a database. The next step was to run the test suite, and then wait.

And wait I did, what was a two or three second run on MySQL was a fifteen second run on PostgreSQL. Hardly desirable when I can run my tests up to several times a minute when debugging an issue. A quick poke around established it was “CREATE DATABASE” at the beginning of the test run that was eating all time.

Googling around the suggestions were that my shiny new Ubuntu 11.04 install, which uses the ext4 file system, is less than optimal for how PostgreSQL goes about things. It also turned up a solution, turning fsync off, which is dangerous on a live server but for development it doesn’t matter if you lose data in a crash.

The fix works splendidly, speeds at least matching MySQL, if not beating it.

DO NOT DO THIS ON A LIVE SERVER!!

So first you want to edit your PostgreSQL file:

sudo vi /etc/postgresql/8.4/main/postgresql.conf

Find this line:

#fsync = on

And change it to this:

fsync = off

Save and close the config file and restart PostgreSQL:

sudo service postgresql restart

And you should get a nice speed improvement when running your test cases.

How I learned to stop worrying and love Apache

Posted on by
Reply

Okay, not quite. Those of you looking at my HTTP headers will see nginx, but who I am to stand in the way of a catchy title and the chance to rip off Stanley Kubrick?

The title does have a point, however: that all too often we hackers worry about optimising our sites rather than addressing the real issues. There are endless discussions about which configuration better serves our site. We pour over the latest benchmarks, drilling down to the last decimal like a spice seller counting saffron threads. Pondering the pros and cons of various servers/proxies/CGIs/languages is enormously enjoyable to hackers, especially those of an entrepreneurial bent. It tickles our technical bone while allowing fantasies of wads of traffic and overheating servers. But it is all a distraction from the real issues which we all too easily allow to slip from prominence.

If we are to accomplish our goals, site optimisation should be low on the priority list. What we should be working on prior to optimisation is endless. I don’t need to list them; your own guilty conscience is doing that for me right now. It is always useful to maintain a perspective on this as more often than not the work we produce isn’t the most elegant or the fastest way of getting what we want. So if you are like me, your first impulse is to refactor, recode and tweak.

Don’t. There will always time later to improve things once you have your first customer, first investor or your mum has had a look. (Seriously, if your mum doesn’t understand your site what are you doing worrying about SQL vs NOSQL?)

There are of course caveats to all of this. This advice mainly applies to early in the life of a project/feature. At some point traffic on that 500ms query is going to take your site down, but won’t that be a nice problem to have? The other obvious exception is bad design. Keep future optimisation in mind so you don’t paint yourself into a corner and nothing but a major rewrite is going to fix things.

With this in mind go and get something done!

My Cooking Secret

Posted on by
1

Yesterday I purchased some Rapini, which I’ve never eaten before let alone cooked with. I grabbed it as it was there, figuring it would make a good side for the duck legs I had found in my local butcher. When I got to checkout of the grocers the girl asked me what I was going to do with it. I replied that I didn’t know as I had never eaten it. The checkout girl looked shocked, I didn’t know what I was going to do with it? I was buying something I had never eaten? What the hell?!

Her reaction got me thinking about my attitude towards cooking and how it differs from others.

I enjoy wowing with food, and that includes wowing myself. There is a thrill and sense of accomplishment when a dish turns out and people enjoy it. To do this I’ve learnt a trick, not being afraid to fail when cooking a dish. With this I am happy to leap into trying new dishes, new techniques, so I regularly cook with new ingredients or untried recipes.

Too many people are afraid to fail when it comes to cooking, so they don’t try and the lack of variety leads to boredom and cooking being a chore. I still get annoyed when a dish doesn’t turn out as I had wished, but that just means I take another crack at it later. Rarely will there be an inedible disaster, so guests are rarely left hungry even if I have to apologise for such and such not quite working.

Cook one thing a week that you have never tried to cook, I dare you.

ps. I did sort of know what I was going to do with the Rapini and that was add butter and garlic, if in doubt use butter and garlic, you can’t go wrong!

Django and Dreampie

Posted on by
Reply

As would be obvious by now I am a dedicated djangonaut (cheesy name I know) and I’ve been using django long enough now that using the ORM (Object Relational Mapping) is becoming second nature. Using SQL for anything but database gymnastics is somewhat annoying as the data isn’t as accessible to python as it is with an ORM. So when I need to get a quick insight into some data or prototype some code I want to be able to use the ORM instead of SQL.

I’ve also fallen in love with dreampie, which is an interactive python shell on steroids. It allows you to type and edit multi-line pieces of python code which you can then run in the inbuilt python shell. It has a fast clean interface and autocompletes attributes from the interpreter so you can get some hacking done quick.

Of course I want to be able to do quick django hacking in dreampie and I worked out a simple way of doing this.

import sys
sys.path.append('/path/to/your/project/')
import settings
from django.core.management import setup_environ
setup_environ(settings)
from a_django_app.models import AModel

Pasting this into dreampie (or loading it from the nice history functionality dreampie provides) sets up the shell with everything it needs to access the ORM (or anything else you use in django for that matter. The first two lines add the project’s path to the list of paths python uses to search for modules and packages. The next imports the project’s settings and activates those settings using the django function setup_environ. After that you can import app models and query away.

You can also use the same snippet of code at the top of standalone scripts to allow them to access the project’s django environment which is useful though it is normally advisable to add a management command instead.

Django Site Admin Emails

Posted on by
Reply

There is a neat feature in default behavior of Django. If while rendering a view it throws an uncaught exception it emails all the sysadmins in it’s settings file. This simple little feature is great on several levels.

  1. Repeatedly getting emails about an issue with often enough information to diagnose and fix the problem means you’re less likely to put up with broken windows.
  2. When something goes wrong you’re much more likely to find out about it, as monitoring is often one of the last things to be done on a project.

So it is a warm and fuzzy safety net that reassures you with an empty inbox, I really like it when I come in on Monday morning and I don’t get a single email telling me something barfed over the weekend.

And as an added bonus Django has this wonderful philosophy about exposing the pixie dust it uses to do it’s magic. All it takes is a call to mail_admins():

mail_admins("Made a sale","We just sold a pony for $%d" % pony_price)

And you’re alerting everyone when something good happens. This is great with new low volume projects where every sale is a momentous event. Of course you can use this for alerting the team about errors as well. There is also mail_managers() so you can setup the non technicals to receive relevant alerts with the same amount of effort.

Adding Composite Primary Keys to Django

Posted on by
Reply

Composite primary keys are great and relating two records together is best done using them. Adding another field just to identify the relationship makes the table un-normalized (that isn’t a word is it?) and we all want our tables normalized don’t we? So it is common practice for (good) database designs to use them anywhere two records are being related.

Unfortunately Django doesn’t support them right now, at least not without some nasty hacks. This means every time you get your hands on a legacy database there is a high likelihood that there will be composite primary keys are in use and you will be in for a world of pain if you wish to integrate it with Django. I’ve been there and the hacks are nasty, and also mean you can’t use a lot of components such as the admin which makes me sad as the admin is a beautiful thing.

The ticket (http://code.djangoproject.com/ticket/373) has been around for 5 years with only one person taking a decent crack at it and he seems to have stopped working on it around the same time the core team was working on 1.0. So I have started on the path of getting Django to support them. And this doesn’t just mean working on the ORM part of Django, it means getting every part of Django to understand that a primary key doesn’t just mean one column/field. Not a small project by any means but it will show some pay-offs in the short term as it replaces the hacks I currently have in place.

Once I have some code to show it will be up on my github http://github.com/hartror