Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
Just wondering about c
I was just wondering , I'm doing introduction , basics on C and it takes me a while to understand . Im learning like half day and last night but its like tough . When i started ruby , i managed to get used to it in two days but here in C it takes longer.
So my question is , thats normal for a beginner? and how long should it take to know basics on good level? one week would be enough? or 3-4 days spending 6h per day? or maybe a lot more?
I think it takes a very long time to be really good at C. I thought I knew C till someone asked me to make a Macro and then I realized....little did I know. So these basic lessons, I think they would be easy to learn, but if you ever get to pointers that part is even more confusing. It is normal to struggle more in some areas, than others. Don't try to count the days as that will cause you to get stressed out. Just do your best to understand the concepts you are working with, and if it takes a day then that's great...if it takes a month or years, well that's great too. The point is being able to understand it and work with it better :)
I haven't started iOS programming because I can't afford a macbook at the moment, (I wish I could LOL), but yeah, I know C to some extent, and what really helps is coding first on paper. For example instead of writing the exercise you are telling me...straight on an IDE then compile it...try doing it roughly on paper and then transferring it into your IDE to see if it in fact gives you what you wanted to get. Sometimes working with an IDE makes things easier, because we run the code so many times, that, it gives us the ability to fix the errors with the help of the error log but then when we get to be without an IDE and we are asked to do the same things...sometimes the brain can't remember the right process because the error log is not there anymore.
So yes that is one of the methods/techniques I use. You don't need to wait till you get it till you move on, as for some...doing is learning. You can move on as long as you get more than 50% of what you are doing. You might have to revisit it later though to get the other 50% understood because as you progress, if you don't know the fundamentals a point will reach where you won't get much from the more difficult part. Even so, it seems that you are on the right track. So keep it up :)