I’m blogging this because I find myself looking it up repeatedly. Every time I start a project, I eventually hit a point where I use the REPL quite a bit. Usually I want to use it from PyCharm’s python console. And I usually find myself manually typing 5 or 6 commands at the start of each session that shell_plus from django-extensions would give me for free.

In part 1 and part 2, we got the basic project workflow set up. Now it’s time to add some basic models and views.

In part 1, I set up the project, a sensible .gitignore, tailwind, and live reloading along with some run targets for PyCharm. Now it’s time to finish up the housekeeping.

I wanted to try out some “modern” front-end development for a while, and I did. FastAPI is great. So is Svelte. But even though I found creating APIs that way to be a breeze, building a whole site that way felt much slower and heavier than using traditional server rendering. So I decided to give django a fair shake for a while, and I’m glad I did. Here’s how I currently like to get a site started with django, using Tailwind CSS for responsive layouts and styling, and mixing in alpine.js and HTMX to make the site feel reactive. I’m glad I gave the backend/frontend split an honest try, but this fits the way I think about sites better.

I feel like restarting the blog. Let’s see how long it sticks this time. My goal is at least 100 posts in the next 12 months.

As good as existing editing tooling for LÖVE2D, sometimes source debugging is hard to beat.

Not surprisingly, the kids are interested in the game projects I’m building for class. But they want to play on the TV.

Zoom has acquired Keybase. It’s hard to imagine that it will continue in anything much like its current iteration. I will miss it.

Working in LÖVE 2D is nicer if you can have a REPL.

Control volume levels of different audio tracks separately in kdenlive.