Where to start when looking to learn everything about Xcode and coding apps

Do you know C?

 

Apple has an introductory lesson:

http://developer.apple.com/library/...nceptual/Mac101/Articles/00_Introduction.html

 

I wonder if the OP is confusing "coding" with "programming". Seems to me the actual amount of "coding" that goes into program development is nearly trivial compared with the work involved in the design and debug phases. There is a lot more to it than just writing some code that does some stuff. If the OP has no background, there will be a need to learn the broader concepts as well.

 

There are also the freely available CS 193P iPhone Application Development lectures from Stanford.

 

I've been programming since 78', and I don't distinguish between the two words. Have you got some strict definition?

 

Don't expect anybody to help via Skype. The best thing may be to join the free developer program and download some of the WWDC 2011 videos. Some titles to review are;

Developer Tools Kickoff
Maximizing Productivity in Xcode 4
Using Interface Builder in Xcode 4​

That assumes you have some programming experience. If not, read the sticky threads at the top and buy an into book. there have been many many many threads here about getting started too.

On the front of the Apple Developer page there is a rotating banner that mentions the WWDC 2011 sessions available on video. Click the 'Watch Now' link and login with a free account. That link will also lead you to create a free account.

The version of Xcode you can download is dependent on the version of OS X you have. For argument sake I'll assume Lion. I only mention this because those videos will demonstrate Xcode 4.x and the free account allows you to download Xcode 4 for Lion only.

 

No definition, but I think there's a big difference.

Programming is the part you can do away from the keyboard.

In ye olden days, a programmer might break down the spec & draw up some flowcharts, a coder would turn that into written statements on a coding sheet, and the keypunch operator would type that onto punched cards.

 

I have no wish to work in those ancient archaic times.

 

Strictly speaking, I view "coding" as composing some routines that do some stuff. "Programming" involves coördinating the routines to work together to yield a desirable effect: this requires debugging, because significant programs never work on the first attempt. A "coder" is concerned with making a module work, a "programmer" has to figure out why this module is flustering that module, has to be able to look in the wrong place because the bug that manifests here is caused over there. May have to fine tune threads to operate safely with each other.

Perhaps it is my error, I might be confusing "programmer" with "developer".

 

If I was to distinguish programming from coding I might put it this way; Programming includes coding, debugging, preparation, research, etc, while coding is the physical act of we monkeys banging at the keyboard.

Perhaps that is what firewood was getting at.