David Seddon

This week I released the latest version of Import Linter.

Something about Django has bothered me for some time.

Let me ask you a question: how do you go about designing the software you build?

In my previous post we learned how Inversion of Control can be visualised as follows: B plugs into A.

A common strategy is to organise it into smaller, decoupled subpackages.

When I first learned to program, the code I wrote all followed a particular pattern: I wrote instructions to the computer that it would execute, one by one.

Imagine a river system, with many streams flowing together, and rocks dotted along the path of the water.

Python is a wonderful language that is a joy to develop in.

If you’ve ever built anything using Django, you’ll be used to including apps in your INSTALLED_APPS setting: # settings.py INSTALLED_APPS = [ 'django.contrib.auth', 'myapp', ] This is something we take for granted, but it’s not always obvious why…

Django provides a mechanism to send and receive messages between different parts of an application, called the ‘signal dispatcher’.