loading...

While learning to code, What limits have you had in the past and how did you overcome them?

jcsmileyjr profile image JC Smiley ・1 min read

While learning to code, What limits have you had in the past and how did you overcome them?

  1. I keep bouncing from one language to another. Solution: Pick something and get good at it.
  2. I'm too old. Solution: Just get started. You are going to get older whether you try or not.
  3. I tried this tech stuff once before and failed myself into depression. Solution: Find the courage to take the risk and just get started.
  4. There's not enough time. Solution: Stay up late, get up early, remove distractions, use a family member as a taskmaster.
  5. It's just too much to remember. Solution: Use digital flash cards, have someone quiz you, and build small projects until certain concepts sink into muscle memory
  6. My limits are creating beautiful products. Solution: Practice makes perfect.
  7. Doing talks at meetup. Solution: Attend meetups
  8. Writing correct English grammar has been a major limitation. Solution: Write blog posts and get feedback.
  9. Not having someone around who knew how to code in K-12 school. Solution: Consistency = Success
  10. I try not to spend 'too much' time researching things that aren't helping me to complete actual work.

Code Connector Contributors: Rachel Eiting, Corey McCarty, Dinesh Sharma, Lynn Bradshaw, Lawrence Lockhart

Posted on by:

jcsmileyjr profile

JC Smiley

@jcsmileyjr

Front End Developer with a focus on React (web) and React Native (mobile), Code Connector national team Online Content Manager and a leader for the Memphis chapter, Gardner, and Outdoor Enthusiast

Discussion

markdown guide
 

Years ago, when I was enrolled in my first OOP course in community college, I distinctly remember that as my programs grew I found myself being less productive over longer periods of time. It wasn't obvious at the time, but I now know it was largely due to the fact that my code had no tests. I was making changes to various classes so that I could implement the next spec in the assignment, but was not taking into account the various places those code changes would affect. This lead me to throwing a lot of time away by chasing down bugs in parts of my code that were previously working just fine.

The solution? Unit testing! Sadly none of these beginner courses I was taking covered unit testing, and, now that I think about it, it's a bit mind-boggling how little testing was covered in any programming courses I have taken over the years...

 

Within my local tech community, that is one of the most repeated limits. It doesn't matter if someone has a university, boot camp, or is self-taught background; testing is barely covered. I hope in the future this gets better as the industry demands this skill.

 

I don't want to pay, not knowing the rational price for DevOps, nor knowing whether it will pay-off in return.

Now I am OK with a little paying for education and Pay-As-You-Go, but I am really concerned about fixed price, like $5 or $10 / month.

BTW, both Google and Microsoft (Azure) gives $200 for new accounts for 1 year. DigitalOcean gives $100 for 2 months.

 

I understand your frustration. There is so much to learn and not all resources are create equal. A better format is if a resource is good, then the user decides to pay for it. The better a resource, the more money the author will make.

 
 

I love seeing my Code Connector crew posting on here!