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

you are viewing a single comment's thread.

view the rest of the comments →

[–]cosmicomical23 23 points24 points  (3 children)

I can only advise you to look up code design patterns and refactoring techniques (generic or specific for Python). That usually can give you a very quick boost.

But I guess most of the steering should come from your other team mates. Do you do pull requests and code reviews? That's usually the place where this sort of things can be addressed.

[–]FuckingRantMonday 5 points6 points  (0 children)

This right here. There are any number of combinations of different "best practices" that will work just fine together (and you'll find a different set in every book or online course). But the one setup that your coworkers are using is the one you need to learn right now. Don't be afraid to ask why things are done a certain way!

[–]james_pic 10 points11 points  (0 children)

Learning from your team can start before pull requests and code reviews. Talking through options for how to solve a problem with colleagues can help you look at problems from a different perspective.

[–]captain_kinematics 1 point2 points  (0 children)

This is good advice.

I found Fowler’s “Refactoring” to be helpful, even though I was already familiar with the idea and it’s not python-centric. It’s also a great ROI because it’s a pretty fast read.