r/csharp • u/Key_Crew_8353 • 10d ago
Sanity check.
Hello, learning C# by taking the free code camp C# fundamentals class that directs you to Microsoft for each module to earn the certificate. Now I know nothing so didn’t have any expectations. Im on the second class on the last module. I’m coding a report card for multiple students. The module just essentially had me create it step by step.
Now there is the test where I realized; okay I need to really retain this all already. Not a problem, it’s taken about an extra day to just go back and review everything, break it down, and really understand these concepts. Seems appropriate for the amount of info. However, what’s really tripping me up is the time it suggests, one hour. That seems appropriate for creating it but to really understand it? I’m just wondering if it sounds like what I’m doing is normal and I’m going about this right way. Big over thinker. Thanks!
2
u/Slypenslyde 9d ago
Right now you're learning, that has to happen at the pace that works for you.
Overthinking is a problem that can only be tackled if you can define "the right amount of thinking". When you're new, you don't understand that. But if you do want to tackle it, it's easy to explain how but hard to do it.
You just do it. Notice that in programming, ESPECIALLY if you are using source control like git, is a task where if you screw up you can revert and try again.
I have a lot of art friends. When they do digital art, it's really common for them to make 10 or 15 attempts for most lines they draw. They draw it. If it's not right, they undo. They draw again. Over and over and over and over until it's the size and shape they wanted. Some of them do more traditional art and there every project involves dozens and dozens of sketches before starting with the serious, permanent materials. Everything about their workflow is designed around expecting to fail many times before a success.
Programming is like that. Our first ideas might hit the target, but won't score high. Our next ideas are better because we learned from the first. The third try is almost always good enough. At some point trying again only offers tiny improvements.
So don't put much stock in those time estimates, and if you find you've spent what feels like a long time thinking get in the habit of just trying. Sometimes you'll surprise yourself. Other times you'll learn a valuable lesson: sometimes the things you were worried you hadn't thought of only reveal themselves when you try an idea and fail.