You wouldn’t know it by looking at this site, or the HTML behind it, but I actualy started off life as a Web designer for [my college paper](http://themaneater.com).
So even though my [day job](http://www.ajc.com) revolves around application development, caching strategies, countless meetings, and worrying about things like [page views](http://heisel.org/blog/2008/11/30/what-does-cpm-mean/) and [CPMs](http://heisel.org/blog/2008/11/30/what-does-cpm-mean/) I’ve got a long background in HTML management and template systems, including [glorified template systems](http://php.net) (unfortunately).
With that in mind, I agreed to review [Django 1.0 Template Development](http://www.amazon.com/gp/product/1847195709?ie=UTF8&tag=heiselorg-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=1847195709). I met the author (before he was an author), [Scott Newman](http://www.greencoder.com/news/), “through the Internet” as we both worked at [media](http://www.ajc.com) [organizations](http://tbo.com) and we were using [Django](http://djangoproject.com) alongside legacy content systems.
The book does a good job of focusing in on the [Django template system](http://docs.djangoproject.com/en/dev/#the-template-layer), specifically focusing on what a Web designer would need to know to work well with a back-end developer.
By day, I'm a product manager serving a group of fantastic engineers at Square.
By night, I fight crime and solve mysteries with a robot pal of my own creation.
By midday, I like a snack, generally a cookie.
Part of this biography isn't true (hint, I like cookies and engineering, I don't own a robot)
