Clean Code Refurbishment #4

New Issue

sebastianw · 2021-03-30T07:30:10+02:00

sebastianw commented

2021-03-30 07:30:10 +02:00

The code has evolved to a mess of different styles of coding and - what is even more severe - without any naming standard. The standard shall be written down in the wiki and then applied to the entire code. Best way to achieve is to change the code every time you touch and realize a problem.

Alternatively, every developer takes a dedicated part of the code and refactors it using the IDEs capabilities to change also references and documentation along with the refactoring.

The code has evolved to a mess of different styles of coding and - what is even more severe - without any naming standard. The standard shall be written down in the wiki and then applied to the entire code. Best way to achieve is to change the code every time you touch and realize a problem. Alternatively, every developer takes a dedicated part of the code and refactors it using the IDEs capabilities to change also references and documentation along with the refactoring.

marcel was assigned by sebastianw

2021-03-30 07:30:23 +02:00

sebastianw added the

management

label 2023-04-10 09:48:57 +02:00

sebastianw commented

2023-04-11 18:13:11 +02:00

Closing the issue and pushing enforcement of coding standard by protecting the master branch against changes without pull request and according code review. This is already mentionend in #2 (comment).

Closing the issue and pushing enforcement of coding standard by protecting the `master` branch against changes without pull request and according code review. This is already mentionend in https://git.geophysik.ruhr-uni-bochum.de/marcel/pylot/issues/2#issuecomment-220.

sebastianw closed this issue

2023-04-11 18:13:14 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: marcel/pylot#4