zys5945
If you have a small team of 3-5 people who understands the architecture as a whole and can keep up with most PRs then I don't think a UI framework is necessary.
However, if you have many teams working on the same project and/or cannot keep up with every single PR merged then I think using a UI framework is a must. It forces you to stick to strict rules. Although you will start writing boilerplate code, it makes the entire application much more modular, and easier to reason about.
Remote: Yes
Willing to relocate: No
Technologies: Fullstack development (Javascript, Node.js, Angular, React.js), Android developement (Java, Android SDK), Desktop developement (Electron.js, WPF), SQL, C++, Python
Résumé/CV: https://drive.google.com/file/d/1CwpVmpOrqSqBffaX3_-Pfle1LBO...
Email: [email protected]
Github: https://github.com/zys5945
I'm looking for a part time remote position. I'm fluent with various tech stacks (web, mobile, desktop, server side, etc) and I'm willing to learn new technologies if needed.
However a lot of the issues that you mentioned (such as lock file and transitive dependencies) can be handled by pipenv, which should be the default package manager
No they are not.
Pip freeze does not resolve transitive dependencies, nor does pip know what to do if your transitive dependencies conflict with each another.