Almost every web project ends up with a little slice of REST to call its own. One of the great conveniences of working with Django is that it makes rolling these slices of REST very simple. Simple enough that we as a community are still haven't come up with a compelling unified REST solution. Hopefully we can refocus on this problem a bit with the new 1.0 roadmap, and have something really useful ready to go when Django 1.0 hits the newsstands.
I spent a while today trying to setup CouchDB-Lucene on my OS X machine, but I've run into a few problems. I documented my procedure pretty thoroughly, hopefully this will serve as a good setup guide once I figure out the problem I am running into.
It was a good run, but I finally closed my DreamHost account and left behind that era. From here on it's all VPSs and servers.
Yesterday I was confused by my own code--really really confused--for the first time in a very long time. Here is the story I unraveled.
A few lines of code and a few minutes of refactoring and my previous blog post evolved into a full-fledged static content management system based on the Django templating system. It aims to facilitate the creation of complex static websites quickly and with minimal human effort. Welcome to AYM CMS.
Programmers talk about DRY, or Don't Repeat Yourself, all the time. Its a strategy for making programming more pleasant, more efficient, and to reduce errors. LifeFlow uses a simple idea, which I have brazenly labeled Dynamic Blog Context, to try to take a few steps toward DRY while writing blogs.
A look at a recent lesson I created for one of my first year junior high school classes.
This tutorial looks at using the Yahoo BOSS Mashup Framework (a simple Python library) to retrieve the RSS feeds for HackerNews and Reddit Programming and strip the union of those results from HackerNews, returning HackerNews to an earlier era.
A quick mention of a project I've been working on for the past several weeks, which aims to be a standard reusable app for sharing and displaying projects in a consistent and pleasing manner.
One of the most valuable parts of Django is its loose coupling philosophy . This means you can plug in your own pieces into the Django stack without fighting against the defaults. However, it can be a bit difficult to understand how to take advantage of the loose coupling philosophy when you are just getting started, and this series will attempt to erase that confusion.
Software engineer, technical leader, sci-fi reader, and so on. Born in NC, living in SF, and glad to grab a coffee.