If you don't understand your code, you can't change, correct, or improve it. You'll leave flaws that you're unaware of and that would be irresponsible.
Indeed, but Claude can only do what you tell it. If you don't know not to make certain mistakes in your code, Claude will just do it and tell you everything is fine. Knowing code foundationally helps you skip the mistake-making process, even when vibe coding.
It’s a false positive getting results on the screen but not knowing how they got there.
Do you need to understand exactly how every minute detail works no, like there are certain things in college I’ll probably never actually need to do in real life but having a general grasp of what’s going on and how things interact can make life so much easier.
The real question is what you don’t understand, is it what the imports and libraries are doing in the background or is it whey you’re executing in a certain order of doing x instead of y?
If it’s the imports and libraries you need a general understanding of what they’re doing.
If it’s the order and execution of your code it might help to map things out, draw DFD’s and sudo code to explain what’s going on.
When I look at someone else’s code I often write out little notes as I move along to track how they work.
I find connecting the dots on paper can really help see how they think and can point out some issues later in the code via instinct, telling me where to look.
most of the imports is header files its a thing i do to organize my project when its too big so instead of looking through 2K lines of code i just look for the header
I just didn’t see anything particularly hard to understand in the code so I wasn’t sure what the issue was.
I do mostly Java so my point is more like I know what JDBC and JPA are and how to use them to connect to a database but I don’t need to understand the exact implementation behind it.
Knowing how it should work is important but drilling down and understanding every little bit in their implementation isn’t necessary
7
u/paralepsy 7h ago
bro, github exists.
7
u/deekamus 7h ago
If you don't understand your code, you can't change, correct, or improve it. You'll leave flaws that you're unaware of and that would be irresponsible.
3
u/MyNameIsRichardCS54 7h ago
Is it a problem? Not yet, but when it comes time to debug your code, then you'll have a problem. Anyway, you must understand it at some level?
1
u/Immereally 7h ago
It’s a false positive getting results on the screen but not knowing how they got there.
Do you need to understand exactly how every minute detail works no, like there are certain things in college I’ll probably never actually need to do in real life but having a general grasp of what’s going on and how things interact can make life so much easier.
The real question is what you don’t understand, is it what the imports and libraries are doing in the background or is it whey you’re executing in a certain order of doing x instead of y?
If it’s the imports and libraries you need a general understanding of what they’re doing.
If it’s the order and execution of your code it might help to map things out, draw DFD’s and sudo code to explain what’s going on.
When I look at someone else’s code I often write out little notes as I move along to track how they work.
I find connecting the dots on paper can really help see how they think and can point out some issues later in the code via instinct, telling me where to look.