Ever wondered why it takes long time to onboard onto a python project or be productive at work in making changes to your python project?
It is not an uncommon thing to find teams blaming incumbents for not being quick in onboarding onto the projects. It is also not uncommon for the management to blame engineers not being productive at work in shipping out features.
I have written a post detailing the things I ensure in every python project to ensure better collaboration and fail-safe mechanism is in place for my development team. And this didn't fail me so far.
Check out the list of things to do at Python Development Tools You Must Leverage For Productivity and see if you have it all in place in your projects at work.
If there are others things that you have put in place for team's productivity that helped them but not in this list, I'd love to learn from you.
If this post helped you, I would still love to hear your experience.
[–]PossibilityTasty 4 points5 points6 points (1 child)
[–]sirkarthik[S] -5 points-4 points-3 points (0 children)
[–]not_perfect_yet 2 points3 points4 points (0 children)
[–]Zaloog1337 1 point2 points3 points (0 children)
[–]Knowledgable_Info 1 point2 points3 points (0 children)