Skip to main content
Code Review

Return to Answer

added 135 characters in body
Source Link
keventhen4
keventhen4
  • 121
  • 6
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks:
    • If you're anything like me, un-clean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
    • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc). Additionally sometimes you might run into circular import problems (a file imports a second file that tries to import the first file).
    • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  3. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks:
    • If you're anything like me, un-clean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
    • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
    • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  3. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks:
    • If you're anything like me, un-clean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
    • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc). Additionally sometimes you might run into circular import problems (a file imports a second file that tries to import the first file).
    • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  3. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
indent sub-list
Source Link
Sᴀᴍ Onᴇᴌᴀ ♦
Sᴀᴍ Onᴇᴌᴀ ♦
  • 29.6k
  • 16
  • 46
  • 203
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks:
    • If you're anything like me, un-clean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
    • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
    • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  3. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
  • If you're anything like me, unclean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
  • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
  • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  1. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks.
  • If you're anything like me, unclean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
  • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
  • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  1. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks:
    • If you're anything like me, un-clean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
    • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
    • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  3. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
added 105 characters in body
Source Link
keventhen4
keventhen4
  • 121
  • 6
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks.
  • If you're anything like me, unclean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
  • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
  • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  1. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks.
  • If you're anything like me, unclean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
  • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
  • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  1. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there.
  1. That is definitely a really clean way to organize a Discord bot's code. You've split the different types of sections of code and you have setups for everything.

  2. However, there can be drawbacks.
  • If you're anything like me, unclean code can cause a lot of problems as you're splitting everything into multiple files and can easily lose track of a bug or something you're working on.
  • Because you've split them into different files, if you plan to utilize some values or functions from another file it could be a bit painful. Of course you could always create another file to store values you might use across files (like a file of constants, things that you might want to change across multiple files without changing every one of them manually, etc).
  • With a lot of different code spanning multiple files, you need to be extremely careful with your handling of code and error handling to make things work. Difficult to grasp things like command trees, sub commands, and hybrid commands could cause errors if not handled correctly.

  1. Structurally, this is a really neat way to organize your project and might be one of the best ways. Something you could do if you don't have much code in main.py though is that you could move bot.py code there. This way you don't have as much "file clutter", especially when you have to deal with storing user data.
Source Link
keventhen4
keventhen4
  • 121
  • 6