It's a start

Today I've started to attack my (long) list of programming jobs.  At a high level, I have code which runs on all my instruments, then I have a complete graphical user interface to control my hardware and finally there are analysis scripts to process experimental data (plus there's code for the NMR instrument and for those experiments, but I am not concerning myself with these programmes at this time).  What this means practically is that if I wish to make a change in part of the chain, I need to account for this edit in my other programmes.  For instance, you can't change the user interface to give new options, if the firmware on the instrument can't do anything this that information.  And it's no point in telling the hardware to record additional data, if the analysis scripts don't treat this information.  Now for big "problems" it's easy to solve these issues one at a time in each piece of programming, but when I have a punchlist of approximately two dozen small changes it becomes difficult to track.  Anyway, that's the work I have cut out for me over the next few days.  Trying to improve my product without breaking the system.