Closed Mackmiller closed 3 years ago
In regards to project 1, if it is functional, legible code, you should be totally fine. IF you are done with your project and are just looking to clean your code up, go for it But, if you have not made the whole thing fully functional, I would suggest keeping it as is for now, build out the rest, and when you are done ( if there is still time) you can clean up the code. Hope this helps, let me know if you need clarity!
Second Lizz's comment. Also, super long conditionals like that aren't even really that inefficient in terms of time/memory, so you're doing fine!
okay, sounds good. thanks for both of your inputs!
What's the problem you're trying to solve?
I'm just trying to make sure my code is organized, it's operating fine. I'm just wondering if this function is okay as-is (super long) or if it's better practice to break it down into small functions?
Post any code you think might be relevant (one fenced block per file)
If you see an error message, post it here. If you don't, what unexpected behavior are you seeing?
no unexpected behavior, I'm just wondering if this function is okay as-is (super long) or if it's better practice to break it down into small functions?
What is your best guess as to the source of the problem?
My guess is that it is fine as-is, but just wanted to check with you guys.
What things have you already tried to solve the problem?
I did try to use separate functions when initially building, but found it better to just store everything in the same function because I could