AVR ISP – Using AVR ISP Programmer to Program a PIC Chip

I agree with PIC18s but for someone just starting they may be a bit intense. I currently teach senior level electrical engineers PIC development and even within the same classes their range of backgrounds can be astounding.

I currently teach people with the CCS PIC-C compiler but it costs money. It is unbelievable simple and was chosen as most of our students have only worked in a lab setting with basic assembly or x86 programming.

I have a feeling a very simple PIC16 may be a better fit, but it will depend on your background. The PIC16F688 is a very simple PIC that we use for our first project to warm people up.

Yes you need to write good code intended to be maintainable and to make it easy to catch mistakes before you run it. However, debugging is still a reality. In a small embedded system, you can't put print statements all over the place. There is no place to print to. You also can't test the code in the same language on a PC because on a microcontroller you're always dealing with the hardware which isn't present on the PC.

A simulator on a PC can be a useful tool, but the more your code has to interact with external hardware, the less useful it becomes. Eventually you need to test and debug on the real target hardware. People telling you they don't do that or that you don't need it obviously haven't done a lot of real microcontroller projects.

I don't know the Atmel debugging environment, so can't compare it to that of PICs. Both processor families can do what you want. If one of them has better availability in your area or you think the setup has a cost advantage, go for it. You're certainly not going to go wrong with PICs, although that's probably true of any of the major microcontroller lines.