Well, you already bought the dev system for the ardi...so I can't help much there.
For simple applications like the light meter, => a sensor, an MCU, a Display and perhaps a switch to switch ranges/ units can be done with more economical MCUs such as the Microchip family of 16FXX or perhaps even the 12Fxx which have fewer capabilities but are in tiny 8 pin packages.
The 16f688 is a microchip MCU which can be programmed by the Pickit2 LPC dev board. In fact since the dev. board comes with a 16F690 for free...you could use that as well, but it costs just under $2.
Now if your application is a one off exercise I suppose using a $6 MCU like the Ardi is ok....but for effective designs matching the MCU to the task is the better way to go. Of course, only after u get some experience in doing MCU based systems will u understand what u need and be able to specify the most cost effective MCU for the job.
If you wish to use C or BASIC as a programming language (which is a good way for a noob to start programming) the ardi isn't bad at all, or perhaps the PIC 18F family. These more powerful MCUs have the MIPS to crunch thru non optimised code and get the job done fast. Noobs don't do optimised code. An expensive compiler for the C or BASIC would do a decent job of makng your code faster by efficient compiling. The free compilers have some limitations there. You can use C or BASIC on any MCU once u have the compiler for the MCU family.
For time sensitive apps, like running a video game on a CRT screen, assembly (asm)language tends to give the best results as u can actually count the instructions to determine the time each bit of code takes as the PIC family of chips have standard timing for the instructions.
Also your IDE (Integ. Dev. Environment) should have a decent simulator so you can follow your code and learn from mistakes.
The key thing when programming is divide and conquer. Always code in sections (subroutines) which can be isolated and debugged b4 moving on. Always comment your routines so that a month from now u can understand what it does.
Read the spec. sheet for your MCU as each MCU has its custom abilities and quirks.
When asking question here try to have a bit of code to post so we can see your challenges. If u solve a problem, share it with us so others reading the threads can learn too.
After you have done some coding and want to move off the dev board to a standalone circuit, you will realise that leaving MCU pins unassigned or 'floating' isn't a good thing. Therefore always consider the unused pins when coding and protoyping.