Archive Database Step 12: Read Your Own ORM
Go back to the Sankofa Journal from the Django course. Print the SQL for the queries on its busiest page and read every one. Find the N+1 if there still is one, and this time explain in SQL terms exactly why select_related fixes it. Then find one query where the ORM version is harder to read than the SQL would be, write both, and decide honestly which you would keep. Write down the query count before and after any change.
Built it in both languages?
Mark it done once your Python and JavaScript versions both run correctly. Honesty here is what makes the dashboard useful to you.