2 karma · joined June 5, 2019
What does connecting to a production DB have to do with any of that?
The problem comes about when someone does the following:
- creates python project
- pip install some_package
- import some_package
Turns out some package was already in the path but a different version
- proceeds to test and build with the assumption of some_package @ newer
- all tests pass
- ships project with requirements of some_package @ newer
Someone attempts to use the package but it doesn’t work.
When you build and package things for production you should create an environment. This ensures the packaging the right versioning of requirements for build.
Say you build using the system version but use packages based on another version. It may work for you but probably won’t work elsewhere.
- What program the student chooses
- Is said program at the University recognized
- If recognized does the program provide a proper mix of theory and application
- What opportunities does the program actively provide for the student
- Is the student willing to be an active participant in their education
- Is student and active participant in what resources the program offers
If yes to all of the above, then student really receives a proper well rounded education practical knowledge, and the resources to find a job. Along with that they have the tools to continue to be a competitor in the market and in their current employment.
Far too often it seems that a degree just implies employment and competitive salary. If properly used and taken advantage of it really implies being a much better competitor when all else is held equal.