---
title: "Linh Fish Dev (@linhfishdev) | Hashnode"
description: "Backend developer — Python, Django, FastAPI. Sharing practical tips and tutorials daily. Blog: linhfish.dev"
url: "https://hashnode.com/@linhfishdev"
---

@linhfishdev

# Linh Fish Dev

@linhfishdev · Ho Chi Minh City, Vietnam · Joined November 2026

Backend developer — Python, Django, FastAPI. Sharing practical tips and tutorials daily. Blog: linhfish.dev

### [Django in Production #20: Series Wrap-Up — Operations Runbook, Incident Checklist, and What's Next](https://linhfishdev.hashnode.dev/django-in-production-20-series-wrap-up-operations-runbook-incident-checklist-and-what-s-next?utm_source=hashnode&utm_medium=feed)

This final episode wraps up the journey of taking the expense tracker to production: by the end, you will have a complete operations runbook, an incident checklist you can use on your very next on-cal

4 min read · [linhfishdev.hashnode.dev](https://linhfishdev.hashnode.dev/django-in-production-20-series-wrap-up-operations-runbook-incident-checklist-and-what-s-next?utm_source=hashnode&utm_medium=feed)

[11h ago](https://hashnode.com/posts/django-in-production-20-series-wrap-up-operations-runbook-incident-checklist-and-what-s-next/6afc704049163909f13f2af5)

### [Django in Production #19: Scaling — More Workers, Load Balancing, Read Replicas, and When You Actually Need to Scale](https://linhfishdev.hashnode.dev/django-in-production-19-scaling-more-workers-load-balancing-read-replicas-and-when-you-actually-need-to-scale?utm_source=hashnode&utm_medium=feed)

Episode 18 showed you how to deploy with zero downtime, but a single server running 3 Gunicorn workers will hit its limit sooner or later: CPU saturates, requests queue up, and the statistics page get

4 min read · [linhfishdev.hashnode.dev](https://linhfishdev.hashnode.dev/django-in-production-19-scaling-more-workers-load-balancing-read-replicas-and-when-you-actually-need-to-scale?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/django-in-production-19-scaling-more-workers-load-balancing-read-replicas-and-when-you-actually-need-to-scale/6afb1f55cbaab8d905f8561e)

### [Django in Production #18: Zero-Downtime Deploys — Blue-Green/Rolling, Migration Order and Restarts](https://linhfishdev.hashnode.dev/django-in-production-18-zero-downtime-deploys-blue-green-rolling-migration-order-and-restarts?utm_source=hashnode&utm_medium=feed)

Episode 17 built the CI/CD pipeline: push code to main, tests run, then the deploy goes to the server automatically. But an automatic deploy isn't necessarily a zero-downtime one — restart the app whi

5 min read · [linhfishdev.hashnode.dev](https://linhfishdev.hashnode.dev/django-in-production-18-zero-downtime-deploys-blue-green-rolling-migration-order-and-restarts?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/django-in-production-18-zero-downtime-deploys-blue-green-rolling-migration-order-and-restarts/6af9cd6181e0c6fa357ae7dd) [2d ago](https://hashnode.com/posts/django-in-production-18-zero-downtime-deploys-blue-green-rolling-migration-order-and-restarts/6af9cd6181e0c6fa357ae7dd)

### [Django: Use auto\_now and auto\_now\_add Correctly — When to Switch to default=timezone.now](https://linhfishdev.hashnode.dev/django-use-auto-now-and-auto-now-add-correctly-when-to-switch-to-default-timezone-now?utm_source=hashnode&utm_medium=feed)

Most Django models have two timestamp fields: created\_at to know when a record was created and updated\_at for the last edit. The quickest way is auto\_now\_add=True for created\_at and auto\_now=True for

4 min read · [linhfishdev.hashnode.dev](https://linhfishdev.hashnode.dev/django-use-auto-now-and-auto-now-add-correctly-when-to-switch-to-default-timezone-now?utm_source=hashnode&utm_medium=feed)

[3d ago](https://hashnode.com/posts/django-use-auto-now-and-auto-now-add-correctly-when-to-switch-to-default-timezone-now/6af87bb3d09ab379396b5d4d)

### [Flask: Stop Requests the Standard Way with abort() — 404/403 with Custom Error Pages in 5 Minutes](https://linhfishdev.hashnode.dev/flask-stop-requests-the-standard-way-with-abort-404-403-with-custom-error-pages-in-5-minutes?utm_source=hashnode&utm_medium=feed)

When a user opens a post that does not exist, or visits the admin area without permission, the view must stop immediately and return the correct error code — not render an error template by hand and r

4 min read · [linhfishdev.hashnode.dev](https://linhfishdev.hashnode.dev/flask-stop-requests-the-standard-way-with-abort-404-403-with-custom-error-pages-in-5-minutes?utm_source=hashnode&utm_medium=feed)

[4d ago](https://hashnode.com/posts/flask-stop-requests-the-standard-way-with-abort-404-403-with-custom-error-pages-in-5-minutes/6af72a5e92d9e1c1e449f025)
