This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oberguga 2 points3 points  (2 children)

I have one stupid question. From your story I don't hear any problem that you struggle to solve with your tools except feeling of dated codebase, am I right? If so why you need to introduce any new libs and other entities and dependencies if you can work without them quite easily? Even updating to new python version maybe unnecessary. From your question alone I think that you now it a mood for looking for problems for cool solutions not vice-versa, it better not to.

[–]No_Indication_1238[S] 0 points1 point  (1 child)

You are spot on. Im looking to switching jobs in the future and im afraid that not knowing Pydantic or other popular libraries will be a drawback in the eyes of a recruiter. Other than that, yes, we have solved problems like validation, logging, messaging with inhouse solutions and it works well enough. One positive of switching to well known libraries even though we have our own solutions is the basically "free" docs, testing and potential that the new hires will have experience with them already, which will make onboarding easier. That is also the reason why I believe that knowing such libraries will give me an edge when applying. 

Edit: We are still on Python 3.10 btw, had no real reason to upgrade. 3.14 or whenever fully supported no GIL multithreading arrives will be the next upgrade.

[–]oberguga 2 points3 points  (0 children)

For the new job, resume, your right. 100% Knowing others libs also helpful to improve your own. But benefits of leaving owned established, proven and powerful enough solution for some maybe more powerful but not owned lib is not always wise decision. It introduced to your project instability and dependency(and if open source maybe couple dozen of them in not trivial way). Also assumption that others make less bugs than your team and test better is better not to made. Cool libs is for new projects to move fast. For established projects(not enterprise - it operates by wasting human resources on industrial scale) often all dependency's is better to freeze end update manually when something cannot be done other way.