The "bad" code is not refactored by the end of the code readability episode.
The "poor practices" within the code see https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-good/issues/2 are not directly highlighted e.g. "code structure could be improved - no functions and everything in one monolithic piece of code" and "commenting and uncommenting code to direct the flow of execution / type of analysis being done"
Ideally, the testing episode should begin with the whole code base refactored into sensible functions.
Possible solutions:
Interim: Introduce a new refactored version of the code at the start of the testing episode.
Add additional exercises at the end of the code readability episode.
anenadic
commented
2 months ago
The "bad" code is not refactored by the end of the code readability episode.
The "poor practices" within the code see https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-good/issues/2 are not directly highlighted e.g. "code structure could be improved - no functions and everything in one monolithic piece of code" and "commenting and uncommenting code to direct the flow of execution / type of analysis being done"
Ideally, the testing episode should begin with the whole code base refactored into sensible functions.
Possible solutions: