What To Do If Coding Is Hard..?
Hello, buddies! This article is to the coding learners and to the people who think " I'm not good at coding.." No one should think like that since anyone can be good at coding. The problem is they don't know how to be Good at coding. So, Let's learn what we can do if we're not good at coding..?
Is coding is Hard? If yes, Why Coding Is Hard?
Is coding hard? Many of the people who learning to code will answer "Yes." But Why coding is hard? Then they will say " I'm not smart enough to do that.","I’m just not cut out for coding".*But that’s not necessarily true. Coding isn’t hard, it just requires more time and practice than you might expect.
To be a competent coder, you need to learn how to produce products, not just write code. To be a web developer, you need to be able to make a website, not just write out HTML tags. To be a Game developer, you need to learn how to use at least one Game Engine, not to learn all the Languages used in Game Development. I leant Coding when I started Game Developing. I also thought I won't be able to Develop games without learning to code but If I decided to learn coding first, I'm not a Game Developer.
Reasons To Be Coding Is Hard For Many People And How To Challenge Them
Reason 1 - Learning to Code Is Like Learning a Language
C++, Java, Python, Objective-C – these are just four languages that happen to be among the most popular programming languages in the world. There are hundreds more. And learning a coding language is like learning a foreign language – quite literally. “So where should I begin?” you may ask. Learn with an End Goal in your mind. Maybe you want to build mobile apps or become a Game developer. Or maybe you want to start your own website-building agency or even work for Google. Whatever your end goal is, find which languages you’ll need to learn and start there. Just to start!
Reason 2 - Learning to Code is Time Consuming
Many aspiring developers walk away from a bootcamp or tutorial proclaiming that coding is a world reserved for geniuses and the whole thing is unfair. Actually, most devs who “fail” at coding, do so because they are not prepared to put in the time and research that it takes to learn. Attending a bootcamp is great place to start, but the work does not end there. Unlike other learning programmes, coding isn’t a qualification you can get and walk straight into a job, never to learn any theory again. Coding requires ongoing learning. So in conjunction with a bootcamp, you’ll want to try tutorials, engaging with other devs on github and spending time on basic trial-and-error. And also there are great sources to learn programming freely. Check this articleby Catalin Pit Tips to lean Programming Faster is in the end.
Reason 3 - Confidence Vs Competence
Source - Thinkful.com
Consider the above graph that illustrates a theory by Erik Trautman. The theory itself is quite involved, but the above graph is a snapshot of his main hypothesis, which is that “your confidence is highly correlated with your happiness and…the point where your confidence and capabilities match is the best proxy for the sweet spot when you’re officially job ready.”
For some, building a career in coding takes months, while for others it takes years. What it comes down to is experience and hardcore grit. As an aspiring developer, you need to be prepared to experience moments of confusion, frustration and general hair-pulling craziness. But on the other side of those feelings, are feelings of satisfaction and the kind of “Eureka” moments that make it all seem worthwhile. Tip is Start with the basics and put in extra hours – time is your most valuable commodity.
Tips to learn Coding faster
1. Learn by doing. Always play with the code while learning
Hint: Build a project as you go through the material. A personal project is often the best starting point.
2. Grasp the fundamentals for long-term benefits
As elementary as they may appear at first, programming fundamentals always need to come first: the better you understand them, the easier it is to learn more advanced concepts. Check this great article - 5 Basic Concepts of Any Programming Language
3. Ask for help. You’ll need it
4. Don’t just read the sample code. Tinker with it!
Reading sample code is not enough to understand how it works. To develop a true understanding, you need to actually run the code and tinker with it. With the additions of comments and instructions, sample code is packaged to be by the reader; but in reality, it’s pretty difficult to replicate from scratch. Reading is not the same as understanding, and actually trying to write the code yourself, or at least running it, will facilitate the learning process much more.
5. Take breaks when debugging
When debugging, it’s easy to go down the rabbit hole for hours, and there’s no guarantee that you will fix the problem. To avoid this, it’s best to step away from the for a few hours, and return with a fresh perspective. Not only is this a guaranteed way to help solve the problem, but you’ll also save yourself hours of headache. So if help isn’t available – to touch on our previous tip about seeking advice – consider taking a break to clear your mind and return later. In the meantime, the bug won’t be going anywhere, and you’ll at least restore some needed sanity to improve productivity.
So buddies, hope you leant something and I think you won't think 'Coding is hard..' anymore! Don't forget to read these articles about programming!
Well written, Mr.Unity Buddy!
It's really interesting that Confidence Vs Competence theory. I see a lot that within the lowest gap, between the desert of despair and upswing of awesome, that's when most people would give up.
... you need to be prepared to experience moments of confusion, frustration, and general hair-pulling craziness
this is such a gentle caution and great advice for aspiring developers! 😀
And, thank you for the mention! 😊
Great article! I'm curious about the Coding Confidence vs. Competence part. Do you think a gap between your confidence and your actual competence can lead to Imposter's Syndrome?
Yes, I'd say it's practically the definition of imposter syndrome! 😉
One of my friends gave me this answer, 'Unless the gap is in the opposite direction, then you're probably making a massively multiplayer open world survival RPG shoot with ultra-realistic graphics in 3 months well, thinking you can' 😄