#CodingVsStudying #OpenSourceProjects #MotivationToLearn
Hey fellow coders! 🖥️ Have you ever found yourself in a dilemma where you just can’t seem to muster up the motivation to study, but all you want to do is dive into coding? 🤔 Well, you’re not alone!
I often feel the urge to work on open-source projects rather than hitting the books. For example, even though I know the basics of pointers in C, there are times when I feel like revisiting the topic would be beneficial. However, the thought of cracking open a textbook is enough to make me want to run back to my code editor! 😅
Have you experienced a similar struggle? How do you navigate this balance between wanting to code and needing to study? I’d love to hear your tips and tricks! Let’s help each other out.
Possible solutions that might benefit us all could include:
– Setting small, achievable study goals each day 📚
– Incorporating coding challenges that align with what you’re trying to learn 🧩
– Finding motivation through online coding communities and forums 💬
Let’s tackle this challenge together and find a way to keep our coding skills sharp while still embracing the learning process. Sound like a plan? 💪 #CodingCommunity #NeverStopLearning
Unless someone invents Matrix-style skill uploading directly to your brain, there’s no alternative to studying.
You can “study” while coding. Every time you come to a stand-still because you lack knowledge, google it, understand it and implement until you manage to make it work.
They say the best way to learn coding and become good at it, is doing.
Just look up what you need as you go. Sometimes what you need will only require 2 minutes of Googling. Other times, you’ll need to sink several hours into researching and understanding what it is that you’re trying to do. If you’re completely unfamiliar with something, expect to spend more time on learning it. But the fact of the matter is that studying is learning, and you’re not coding anything if you don’t learn how to.
This is completely normal. Programming is a skill. And it needs to be developed like any other skill….you just need to program. Any information, any knowledge that you need in the process, you will gain in the process. Documentation, textbooks, Internet. This is all very good, but it only becomes useful when you use this knowledge.
You cannot become a programmer, just as you cannot become an engineer simply by reading and memorizing books.
You are on the right track. Develop a skill. Well, yes. Read books and other documentation as needed.
Books are imho the worst option to learn coding. You can read about everything you want but things get so abstract that you feel you don’t actually need them. That happened to me while first learning interfaces: reading them from a book and instantly thought: “well I could go with a class, don’t need this”.
However, theory is just as important as coding, to me. Because if you only code you’ll eventually miss out concepts just because you don’t know they exist in the first place. Then, when you’ll be forced to use them, you’ll find them frustrating because you are already too much used to your way of coding.
So to me it’s like study a concept and try to **imagine and think** where and when you can use it, when it could be useful. Only then sit at your desk and actually code it.
In my experience, “coding” is mostly studying. It’s 95% figuring out what your problem really is, reading documentation, and figuring out the best way to solve your problem.
Code -> get stuck -> learn -> code -> get stuck -> learn…
Funny, it doesn’t sound like a problem at all. The best way to get good at something is to do it, which is apparently your vice. The times I’ve learned the most on a programming topic were when I was coding & hit a wall, which forced me to research it in order to implement it. Just try to contrive something that involves pointers (or whatever topic) for you to work on and you’ll learn them inside and out whether you like it or not. In general I think books, documentation and articles are best used as a supplemental learning tool, and you get the most out of “study” by combining it with practice.
Now, if the problem is that you’re a student and have some written exam to study for, that’s a different story.
The whole thing with development is being able to google your answers as you go.
Do what you have to do until you can do what you want to do
Honest question though : How much “actual coding” can you do without a good grasp of pointers?? (Assuming you are doing a C project)…
I think practice speed reading or reading comprehension is always a good start