The trends and tweet sections do not need to be together so break up the monolith. Note that this can be low priority since development on tweets usually do not affect trends.
Trends is lighter so easier to move.
The new structure does not have to exactly map to the old one.
Add tests.
Avoid refactoring unless it is clear that it is best to do now.
Initially do not try and move the common code with tweets to a common repo or share one from the other. Consider it boilerplate. Later this can be moved to a twitter lib project, including twitter bot projects and any future one which might use mongoDB or simiar.
Add a PR here to remove trends code and then add it in another repo.
Utils can be rewritten as needed, after creating an argparse template based on requirements across this project.
The trends and tweet sections do not need to be together so break up the monolith. Note that this can be low priority since development on tweets usually do not affect trends.
Trends is lighter so easier to move.
The new structure does not have to exactly map to the old one.
Add tests.
Avoid refactoring unless it is clear that it is best to do now.
Initially do not try and move the common code with tweets to a common repo or share one from the other. Consider it boilerplate. Later this can be moved to a twitter lib project, including twitter bot projects and any future one which might use mongoDB or simiar.
Add a PR here to remove trends code and then add it in another repo.
Utils can be rewritten as needed, after creating an argparse template based on requirements across this project.
Rewrite docs too.