This programing tutorial discusses how to become a better programmer by implementing a set of object-oriented design ideas and techniques. Watch more at http://www.lynda.com/Java-tutorials/Foundations-Programming-Object-Oriented-Design/96949-2.html?utmmedium=viral&utmsource=youtube&utm_campaign=videoupload-96949-0003

Foundations of Programming: Object-Oriented Design table of contents:

Introduction 1. Core Concepts 2. Object-Oriented Analysis and Design 3. Utilizing Use Cases 4. Domain Modeling (Modeling the App) 5. Creating Classes 6. Inheritance and Composition 7. Advanced Concepts 8. Object-Oriented Design Patterns 9. Object-Oriented Design Principles Conclusion

learned C (and Java, actually) from C In Plain English. (There's a Java and a VB and several other versions of it too.) It will take care of things like memory management and general syntax stuff; linking and library creation are more platform-specific though. I came to it from a C background though so my concept of pointers in C was fairly stable anyway, but it did a good job of reteaching and going over iterators and stuff. As a plus, it's a pretty frooping complete reference book too, language-wise (it doesn't do much STL stuff, I think). The tutorials are well written and easy to read and follow, and each one pretty well stands on its own so you can just read the ones on memory management and skip everything about what a class is. :-)

To become a good programmer, I think various aspects should be taken care of:

1. One should be strong logically. Start with small small code snippets and understand the logic behind them.
2. Run the same code under various input and identify the reasons behind the outputs.
3. Write a code with proper coding convention, so you yourself don't get confused and code program quality improves.
4. Write a code with minimum bugs. Take care of memory allocation and exception handling while using pointers in C/C .
5. There are various sites discussing technology interview puzzles. Solve them.
6. Do continuous practice.

Complete c reference is a good book to start with. Arrays are very well explained in there. Ask if you don't understand anything in our C/C forum.

A good programmer gets things done! On time and to specification!!

But it does involve a lot of reading. You will come to know quite a lot of things by heart due to repetition, but there is always new material to learn. And you should always double check anything you're unsure of.

And at this time, with the appearance of C 11, even experienced C programmers have plenty of new stuff to learn.

A professional programmer is highly unlikely to know all the function names in the codebase they're working on as they do get rather large. Unless they're one of those unusual people who has a photographic memory/total recall. But they will usually know the overall large scale architecture and where their code fits into it. And have a detailed knowledge of what they're implementing, but even then it doesn't mean you know all the function names. (That's what Doxygen and ctags, and Visual Studio's Class View, are for!)

I've been a Windows programmer for a number of years now, and still don't remember all the parameters for the Win32 CreateProcess function. But that's because I'm also a C programmer, so I wrap up a lot of API calls inside classes and then use those on a daily basis.

To become a good programmer, I think various aspects should be taken care of:

1. One should be strong logically. Start with small small code snippets and understand the logic behind them.
2. Run the same code under various input and identify the reasons behind the outputs.
3. Write a code with proper coding convention, so you yourself don't get confused and code program quality improves.
4. Write a code with minimum bugs. Take care of memory allocation and exception handling while using pointers in C/C .
5. There are various sites discussing technology interview puzzles. Solve them.
6. Do continuous practice.

Complete c reference is a good book to start with. Arrays are very well explained in there. Ask if you don't understand anything in our C/C forum.

A good programmer gets things done! On time and to specification!!

But it does involve a lot of reading. You will come to know quite a lot of things by heart due to repetition, but there is always new material to learn. And you should always double check anything you're unsure of.

And at this time, with the appearance of C 11, even experienced C programmers have plenty of new stuff to learn.

A professional programmer is highly unlikely to know all the function names in the codebase they're working on as they do get rather large. Unless they're one of those unusual people who has a photographic memory/total recall. But they will usually know the overall large scale architecture and where their code fits into it. And have a detailed knowledge of what they're implementing, but even then it doesn't mean you know all the function names. (That's what Doxygen and ctags, and Visual Studio's Class View, are for!)

I've been a Windows programmer for a number of years now, and still don't remember all the parameters for the Win32 CreateProcess function. But that's because I'm also a C programmer, so I wrap up a lot of API calls inside classes and then use those on a daily basis.