I'm trying to understand what the hardest part is for people new to programming? Is is understanding what source code means? Syntax? Was it variables or functions? How to think more like a programmer?
Ask HN: What's was the hardest part about starting to code?
1–10 of 42 posts
Re: Ask HN: What's was the hardest part about starting to code?
#2Much like mathematics, programming is learned through action. As a fairly cautious individual, I wanted to understand everything I was about to type as input for the compiler. I would recommend the opposite approach: Copy code examples line by line, and start modifying them with simple changes such as variable names, output strings, etc.
Re: Ask HN: What's was the hardest part about starting to code?
#3For me it was the vast number of things that you (eventually) need to know, many of which are assumed by those writing tutorials, such as
1. how to use the command line 2. how to `build from source` 3. how to integrate different technologies (such as the MEAN stack) 4. etc.
In addition to the above, certain parts of the web, like StackOverflow, can be uninviting to new people even though (in my experience) the vast majority of coders are inviting and encouraging both in person and online.
Re: Ask HN: What's was the hardest part about starting to code?
#4Chilling out and realizing it’s all just a bunch of pipes being duck taped together (web dev)
Re: Ask HN: What's was the hardest part about starting to code?
#5Much like mathematics, programming is learned through action. As a fairly cautious individual, I wanted to understand everything I was about to type as input for the compiler. I would recommend the opposite approach: Copy code examples line by line, and start modifying them with simple changes such as variable names, output strings, etc.
I've been coding for many years and I agree, doing is the best way. I also encourage this method as well.
I'm looking to craft a tutorial for the /absolute/ beginner. That's why I asked this question.
Thanks!
Re: Ask HN: What's was the hardest part about starting to code?
#6For me it was the vast number of things that you (eventually) need to know, many of which are assumed by those writing tutorials, such as 1. how to use the command line 2. how to `build from source` 3. how to integrate different technologies (such as the MEAN stack) 4. etc. In addition to the above, certain parts of the web, like StackOverflow, can be uninviting to new people even though (in my experience) the vast m…
Great point about the command line.
I'm looking to craft a tutorial for the /absolute/ beginner. That's why I asked this question. So more feedback the better!
Re: Ask HN: What's was the hardest part about starting to code?
#7Being a computer power user in order to be able to effectively set environments.
Re: Ask HN: What's was the hardest part about starting to code?
#8I would argue that it's thinking programmatically and applying that mindset to a computer.
When humans interact with each other there is a lot of subtlety and nuance that is embedded in that communication. I can say something to you but you can infer that I really mean the opposite by the tone of my communication.
All that is lost with computers, when communicating with a computer you need to be especially precise in what you want the computer to do and when you want the computer to do it. I'd argue that most bugs are a result of improper communication between the programmer and the computer. Either the actual intent was not communicated properly or there is context lacking in the communication (server status, load, etc.) that is not being accounted for.
Re: Ask HN: What's was the hardest part about starting to code?
#9Language inconsistencies within documentation.
Half of all documentation is meant to be read literally. "Follow these exact steps for this exact reason and this exact thing will happen."
Then the other half is written as if you're supposed to have some secret knowledge. "Just run this, do the usual thing people do, and then you'll probably end up with something like this."
Those halves aren't mutually exclusive by document, and it took me a long time to get a feel for what the documentation author's intended.
Re: Ask HN: What's was the hardest part about starting to code?
#10I learned 20+ years ago and I feel like back then it was a lot easier to learn. You would get a VB or C++ book and immerse yourself in it. The book would be self-contained --it had all the information you needed to become decent at that topic. Once you were done, you moved to the next book.
If I was learning today, I think that I would be completely overwhelmed by the amount of information that we have at our disposal. It would be harder to dive into one thing while being bombarded by the other 300 things you are supposed to learn because everyone is talking about them.
When I mentor young programmers, I advise them to focus on a single language/framework for a really long time, until they achieve real proficiency, and actively filter out everything else.