Re: oAuth help

[roboticus]

landon:

I think you may be biting off a bit more than you can chew. If your first program is (a) in a new language, (b) accessing the network, (c) accessing a remote API, (d) ...etc... then you've got too many unknowns at once. If something doesn't work, you won't know where to look first.

I think you'd be better off learning one new thing at a time. It will probably let you learn better *and* more quickly. So first learn your new language with a few simple tasks. Then, when you're confident with your knowledge of perl, do a few simple networking tasks. Then keep building on your knowledge.

It may seem like a long, roundabout way to do things, but there's no royal road to programming.

Update: When I learn a new programming language, usually the first two programs I write (after the obligatory 'hello, world') are the Queen's problem and the Knight's tour. There are plenty of interesting puzzles that don't require network access, complex libraries, and so on.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

[landon]

Thanks for the post, I have never heard of the Royal Road before, it was something interesting to read. I have done very simple programs before in a few different programming languages, but nothing that complex. This is the next chapter in my little hobby. I am trying to learn how to do API's, and network access. I figured that this would kill two birds with one stone. Perhaps you have a recommendation or project to suggest to learn these, that may be a little easier? Thanks for the help.