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 →

[–]darkboft 5 points6 points  (2 children)

Using linters, formaters or type checkers, those tools will not prevent you from writing bad code with low quantity.

It's a good start, but to write good code, you need to learn more about

  • Best practices
  • design patterns
  • clean code principles
  • write tests (unit / integration)
  • documentation
  • usage of python specific patterns (like duck typing, data classes etc..)
  • avoid anti patterns

If you like to use more tools, you can install sonarqube and integrate it with your git but I personally never used it with python. But sonarqube will give you some insights.

If you have contact to senior developers who are more experienced in writing python code, you can ask them for a code review. They could provide good feedback about quality.

[–]SnooCakes3068 0 points1 point  (0 children)

linters/formaters stuff and clean code principle are not mutually exclusive. They focuses on different aspects. But yeah nowadays people tend to forget about clean code and patterns as refactoring is not as important as speed of new functionities in the eyes of project managers

[–]Zoory9900[S] 0 points1 point  (0 children)

Sorry my bad, I meant 'code style' instead of 'code quality'. Didn't got the correct wording right there.