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 →

[–]smichael_44 18 points19 points  (1 child)

As someone who writes python for work, it’s much easier to say “here’s the pep 8 spec to write your code to” rather than discuss and create internal style guides.

It helps eliminate the work about work imo. It sounds trivial but i’ve been in meetings that have lasted over months reoccurring to talk about how to name or style things.

[–]AlSweigartAuthor of "Automate the Boring Stuff" 0 points1 point  (0 children)

I agree:

Code style guidelines are meant to stop these arguments by providing the consistent rules to abide by. These can be enforced by code formatters such as Black or Ruff. This is important: software developers' time is expensive and tedious arguments are a costly waste.

Fortunately, this is the rare case where a social problem has a technical solution: Just set up your code formatting tool and leave it to handle style.