En kodare

I’ve been working for roughly 5 years now in an app that is localized to Swedish, so I have built up some opinions on how to manage translation of a Django project.

In the AI age the importance of readable APIs goes up, as this can mean the difference between not reading the code because it’s too much, and easily reading it to verify it is correct because it’s tiny.

On the pytest discord channel Sviatoslav mentioned a pull request with a bunch of spelling and grammar fixes.

The iommi docs are more correct than most projects because we take a different approach to documentation: part of the test suite is the documentation.

In Django 5.2 we got a way to easier customize attributes of forms.

Phil Gyford wrote an article about how nice it is that the Django admin pre-populates inputs from the GET parameters if there are any.

At Dryft I have the luxury of a small production database, so I can mirror prod to my local dev machine in ~3 minutes.

When I joined TriOptima back in 2010, a common pattern emerged where names of things were slightly off because of stray whitespaces.

There’s a lot of tools out there to automate taking screenshots for documentation of web apps/libraries.

This question popped up on the Django Discord: Any other tips on how you’re running 2,105 tests in less than 2 minutes?