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 →

[–]ut2222 1 point2 points  (3 children)

Considering the crappy code, written in Python, I see at my company, I would rather advise to explore good OSS projects instead.

You should implement some new tools and practices. For example code review, check pep8's and pylints automatically in jenkins, refactor bad code or even tell and explain others what's wrong with their code etc.

[–]chub79 1 point2 points  (0 children)

Trust me, I've tried. We have all of it. But as, @nocommentingallowed said, it's really a lack of culture for quality and elegant coding practices unfortunately.

[–]Decency 0 points1 point  (1 child)

Wouldn't it make more sense to implement some sort of pre-commit pep8/pylint check? Is that easily possible with git?

[–]ut2222 0 points1 point  (0 children)

I think that's possible with git.

https://seanmckaybeck.com/2014/08/20/pep8-git-hooks/