I read so many docs when I was trying to implement OAuth and got more and more confused. This video was a huge help though for explaining all of the concepts:
We use poetry just for development, but run Docker containers in prod. When the image gets built we just create a requirements.txt (poetry export --format requirements.txt --output requirements.txt), copy that into the image, and pip install. Because this is built using the poetry lock file, it'll always be exactly the same unless we specifically update something with poetry.
I used to work at a place that was just using requirements.txt files that only included our direct dependencies. There was a project that needed updating after not being touched for a couple of years. The requirements.txt didn't change, but when we built the project again, some of the transitive dependencies used a newer version, and a bug was introduced from one of those updates. A bunch of time was wasted tracking down the issue, pinning the old version of the transitive dependency, and figuring out the damage caused by the bug.
As a result, the requirements.txt was changed to also include transitive dependencies. We had vulnerability scanning on our code, and it found a severe issue with one of the transitive dependencies, but there wasn't a version of that library with the issue fixed yet. Time was spent looking into this to see how we could be impacted. As it turns out, it was a transitive dependency for a library that we no longer used and removed from the project months ago. When you create your requirements.txt by running pip freeze > requirements.txt, you don't have an easy way of knowing which library requires which transitive dependency.
There's ways you can fix this using multiple requirements.txt files, but at that point it's a lot easier to use poetry, especially if you want to keep your development dependencies separate.
Oh, this segues nicely from my DST, my favorite bikeshedding topic into my second favorite one!
Base 12 is better than decimal in every way. It divides cleanly by 1, 2, 3, 4, 6, and 12. Compare that to decimal, where you have 1, 2, 5, 10. It's much better for scheduling. With decimal you couldn't have a nice, clean schedule for a factory with 3 shifts per day for example. 60 minutes (which is a multiple of 12) gives you a lot of ways to break up an hour, vs 100 minutes.
I had a friend once rant about how we should switch everything to base 12. It's obviously crazy given the effort vs reward, but I think we would have been better off to have done so way back when.