Python  Style

Software  engineering courses  often  provide very  rigid  guidelines on the style of programming, generally the appropriate value of indentation, or what  to use, or whether to capitalize  underscores in variable characters.   Those things may be useful  for uniformity and  readability of program, especially when  a lot of engineers are working on a software.  But they are mostly  arbitrary: a style is chosen for consistency and according to some person's aesthetic preferences.

There  are other  method of style that look, to us, to be more  fundamental, because  they  directly affect the readability or ef?ciency  of the code.

• Avoid recalculation of the similar value.

You should compute it once and  assign  it to a variable instead; otherwise, if you have  a bug in the calculation (or you  want  to change  the program), you  will have  to modify  it multiple ways.  It is also not efficient.

• Avoid repetition of a structure of computation.

You should use a method instead, again  to avoid  having to change  or debug the same basic code multiple times.

• Avoid numeric indexing.

You should need destructuring if possible, since it is much  easier to read the code and therefore easier to get right and to modify later.

• Avoid excessive numeric constants.

You should name  the constants, since it is much  easier to read the code and therefore easier to get right and to modify later.

Here  are some  examples of simple  procedures that  exhibit  several ?aws.  We'll talk about  what creates  them  problematic.