Live data from Hacker News

Ask HN: What's was the hardest part about starting to code?

news.ycombinator.com

41–42 of 42 posts

Re: Ask HN: What's was the hardest part about starting to code?

#41

The assumptions that documentation makes about what you already know. Sometimes these are such tacit assumptions that they don’t even give you anything to start googling about. Other times they’re assumptions that you’re already skilled in areas of computing that it can take months to years to understand properly.

What would be some good examples that most books/tutorials make assumptions on? Thanks

It's going to be different for everyone, probably. For me, it was always stuff around networking, systems administration, DB administration, and compiling/linking.

A tiny example might be something that uses a symlink or, worse, is hard-linked from multiple places. A newbie might not even know that such things are possible; and if you don't point it out or use the terms, they can end up be horribly confused.

Re: Ask HN: What's was the hardest part about starting to code?

#42

The hardest part could be slowing down, really reading, really practicing, really submitting yourself to the learning process. Anyone can be a script kiddie. Not everyone can say they know a language inside and out. Practice makes perfect. You won't learn to code in a day, week, month, year.

Don't confuse learning corner cases and quirks with superior learning ability
Post reply on HN