|
|
|
|
|
by r_hoods_ghost
1555 days ago
|
|
Firstly "best practice" is a much abused term and at least some, if not all, of what you are talking about is not identifying and establishing best practices but instead about establishing conventions. Things like should we use CamelCase or snake_case are conventions and which one you adopt is basically arbitrary. If you make wide use of a framework or are using a language like Python that has a strong preference for a particular convention, use that. If not, toss a coin. But don't debate it. Say this is the convention you are going to use, it needs to be this way for consistency and readability, and then enforce it at code review. You can actually do this with a LOT of supposed best practice discussions. You can then focus on ACTUAL best practise discussions. Get your team to identify pain points in your current processes and also things you do well. See if there are common industry practices that you aren't using and assess whether these are good candidates for best practices (sometimes they are. Often they're not). Look at how your (successful) competitors do things and also other companies you admire. |
|