For sure! If you sloppily throw together the first solution that comes to mind and don’t spend time on refactoring, variable naming, cleanup, etc, then you missed most of the value you can get from PE.
Thanks for the response.
I’m not advocating memorizing the solutions to PE problems. I don’t think you should need or be able to recite the algorithms on demand.
As I mentioned in the article, doing PE is not so much about the questions themselves. It’s about the underlying problem solving you’ll…
Hi Jesse, thanks for reading!
Getting Postgres running locally is so machine-specific that I don’t think I could write a comprehensive tutorial that applies to everyone. Plus, there are already a lot of great tutorials out there.
Check out the official docs: https://docs.docker.com/compose/django/
I can’t answer your question specifically without more context, but Docker recommends a Dockerfile and a docker-compose.yml to run a Django app
Also, typically when you use gunicorn you’ll want to point it at Django’s built-in…
That’s correct. If you make a change to the local database, the same changes won’t be reflected in production. That’s generally a good thing, because you can break things, drop tables, and reset schema in testing without it breaking your production database.