Although PICAXE microcontrollers don't require solid programming skills, it's crystal clear to many users (myself included) that such devices, using "software to tame the hardware", look to be the future of many electronic circuits.

Most Picaxe designs (including mine) evolve under "cut and try" incremental programming, and parts drawer fossicking for, say 82nF capacitors and 680kΩ resistors in a traditional timing circuit, can be replaced by convenient and versatile code-tweaking instead.

Layouts can be smaller and cheaper too, and upgradable later without laborious unsoldering.

So - you want to be part of this "Flash" revolution then? You'd better take note of some basics!

If you yearn for more than simple "08" tone output or LED flashing, coding care and economy is obviously crucial. And it'll help develop good design habits that may carry over to larger microcontroller applications.

Many real-world electronic and software engineering projects, just as in other fields, are characterised by skills subdivision, such that teams may work on the display, while others may be slaving away with power supplies or user interfaces.

Ultimately these have to be seamlessly integrated into the final product, or much fist shaking and gnashing of teeth can occur. It's similar to building a house and coordinating tradesmen - of course you don't want concrete slabs poured before services like drains are first installed.

Perhaps the Golden Rule here is to DOCUMENT YOUR CODING.