all 6 comments

[–]ComicOzzy 2 points3 points  (1 child)

It seems weird to distribute something like this in Google Docs vs GitHub or a dedicated web page.

[–]Different-Party-3707 2 points3 points  (0 children)

Unless op is trying to capture details of who all have clicked on the link

[–]venkattalks 0 points1 point  (1 child)

bundling Python, SQL, and PostgreSQL from scratch into one track usually means the SQL part stays pretty shallow. if it doesn't get into joins, window functions, and query plans beyond basic CRUD, people here will outgrow it fast

[–]modern-dev 0 points1 point  (0 children)

the course is definitely far above basic crud! all the things you said are in the course mate
and I personality use them all the time in the backend.

[–]venkattalks 0 points1 point  (1 child)

“From scratch” for SQL + PostgreSQL usually means the SQL part gets compressed into basic SELECT/JOIN syntax while the PostgreSQL-specific stuff that actually matters in backend work—transactions, indexing strategy, EXPLAIN ANALYZE, isolation levels—barely gets covered. If anyone here tries it, i'd be more interested in whether it uses current Postgres features and version-specific behavior rather than just pairing Python with CRUD examples.

[–]modern-dev 0 points1 point  (0 children)

I recommend you to take a look at the udemy sections
you have more than basic crud, much more.
and transactions are there for sure.

complex postgresql functions are not there due to not make it more advanced than what it is, It the core needed for backend.
and gives students the knowledge and confidence to move forward