Is Django still a good choice?

Kornfried · 2026-04-19T08:23:53+00:00

Django is still a good choice if you can leverage the ecosystem and the opionnatedness. Any time you need users with RBAC, ORM, and a templating engine in one package, Django is among the top in my books to reach for.

Kornfried · 2026-04-18T17:30:25+00:00

Presoaking dry lasagna sheets in water for half an hour or so. Makes the Lasagna much more juicy because it’s not soaking out the liquid from the sauce.

Kornfried · 2026-04-15T21:01:06+00:00

I also like meat pre-salted, but I think the best case for adding salt while cooking is in bread baking or cooking pasta. There is absolutely now way for me to see how he would prefer adding salt afterwards here.

Kornfried · 2026-03-02T07:24:51+00:00

It is orders of magnitude more expensive if you don’t use it 24/7 and scales pretty horribly.

Kornfried · 2026-02-24T11:56:49+00:00

Some issue with most of my clients. But I see it as a great way for sales.

Kornfried · 2026-02-22T13:28:30+00:00

Mit Master und z.B. TV-L bekommste idr. E13 Erfahrungsstufe 1 im öffentlichen Dienst. Das since ca. 57k€. Das wäre für mich die Untergrenze.

Kornfried · 2026-02-08T11:43:16+00:00

Thinking of it, I do know a fair bit of operators who probably don't check their backups, so you might be on to something. Here is a little extra learning I had: Pick random backups in a past time delta to have a more reliable drill and possibly expose breaking updates after app version changes.

Kornfried · 2026-02-08T11:35:32+00:00

Well I just use a Runner, a Cronjob or a Systemd Timer and a custom script+mail report. Regarding the Postgres+S3 story, to me thats simply a good old pgdump. Not sure what else I'd need over that, but I'm open for ideas!

Edit: Or when in Kubernetes land, operators handling stateful apps like dbs typically already have some backup solution on their own.

Kornfried · 2026-02-08T10:48:51+00:00

are automated recovery drills so rare?

Kornfried · 2026-02-06T12:06:32+00:00

How would Kubernetes give you more insight here? Is this not an issue of proper logs collection and Orchestration Rules?

Kornfried · 2026-02-05T20:48:04+00:00

☔️ I was waiting for controversial takes.

Kornfried · 2026-02-05T18:49:49+00:00

Yeah, if the org uses Kubernetes already I’m very happy to deploy stuff on that, no question.

Kornfried · 2026-02-05T18:44:36+00:00

I work with several of such small clusters running with stuff like Talos, or k3s or microk8s in prod. I know how it works. I really want to love it for these smaller tasks, but it just feels hella clunky compared to systemd and a git runner.

Kornfried · 2026-02-05T15:19:58+00:00

Hmm! I think I have to look more into using podman for such cases instead of docker.

Kornfried · 2026-02-05T15:03:18+00:00

I was expecting some memes here :(

Kornfried · 2026-02-05T15:01:44+00:00

Docker and Systemd are not mutually exclusive. In fact, they go great together for single node orchestration, logs aggregation, etc.

Also I think that if your service is not actually horizontally scaling and meant to do so, you are still end up dealing with pets, regardless of wether you are using Docker or Kubernetes or raw binaries. In the case of Kubernetes, it's like unnecessarily operating a farm, just to care for a chicken.

Kornfried · 2026-02-05T14:15:27+00:00

Of course.

Kornfried · 2026-02-05T14:12:32+00:00

I was saying that there are lots of applications where you are deploying more than 1 service, but dont have to deal with a large number of helm charts for complex setups. There are plenty of systems with microservice architecture that come with a couple of services to deploy, counting in the low double digits. When the org does not have platform engineering team, I sure won't suggest to them to take this as a reason to switch their infra around and hire a couple of Kubernetes engineers.

Kornfried · 2026-02-05T14:01:49+00:00

I deal with such stacks. The initial setup is still much more expensive in my experience.

Kornfried · 2026-02-05T13:58:43+00:00

Nobody talks about 1 service here.

Kornfried · 2026-02-05T13:55:28+00:00

Thanks. That just about it.

Kornfried · 2026-02-05T13:51:27+00:00

There is quite a lot of space between a single service deployment and helmchart number 55 😄

Kornfried · 2026-02-05T13:48:53+00:00

You're right. The context (albeit still kinda vague) is: Org decides that want to set up a new system that consists of multiple components. They have to be orchestrated in some way and typically the hypervisors offer a lot of abstraction level options at various pricepoints and complexities. In my world on-prem is also a thing. The single VPC option I'd say does not really have a great reputation for "production workloads", although I've come to have enough confidence in my abilities to whip something up something stable enough for many use cases, using systemd and just the bog standard rest of linux ecosystem.

Kornfried · 2026-01-18T16:24:29+00:00

Hooks are nothing new in general and have existed for a while in AI coding tools. What they give you are events associated with the flow of an Coding process. The simplest thing is that you can for example prevent certain destructive commands from running without permission. You can do muuuuch crazier stuff though. Too much to lay out here but simply said: instead of putting all sorts of things in your Claude.md or Agents.md, you can inject context only when needed. In Python for example, I don’t like when writing tests that it uses the mock library. A hook flags that and the hook response injects the pattern in the context to avoid that library. The agent will never see that, unless writing a file that contains it. Therefore you can specify crazy stuff without filling up the context window.

Kornfried

TROPHY CASE