So…yeah…today sucked. Is it possible to have negative productivity? After running off the track (not too far) yesterday, Jeff pointed out the correct tracks far off on the horizon and I trudged back, shoved the consist back on the rails, and got re-started. Of the dozens of lines of unnecessary (but not bad) code, I only had to undo a couple. Monday, Tuesday, and Wednesday I made great progress.
Not so much. Write a line of code, delete it, or maybe two. Follow a trail of references, definitions, and implementations. The saving grace for me is that our code base doesn’t suck, and wasn’t written by people who were stupid or stupidly-clever. It’s well-organized, and mostly plain C (aka C+), and the code doesn’t rely on side-effects.
I’m in this weird position of knowing a lot about individual leaves on the CygNet tree, and I totally get the trunk, and am passing familiar with several branches. Beyond that, well, I’m not quite in “and then a miracle happens!” territory, but some of the things I think I know aren’t really so, and it means it’s sometimes difficult to know WHEN TO STOP MOVING IN A PARTICULAR DIRECTION. Ahem.
Today was adding a new registry item for CygNet service/client startup, “IpVersion”, which all future (assuming we do v6) clients and services will have to check on start up so that they know version of IP to try and use. Argh. The less said, the better.
What does this have to do with quantum? Nothing. I was just thinking what it would be like to build a SCADA system where points didn’t have current values, per se, until you actually tried to use them. Instead of recording a value, you’d record a lambda function that expressed the possible quantum superpositions of the point involved. I think I have that right. We have services that are like that now, but I was thinking about what happens when you literally have to record things that don’t have a current value, just a function describing possible values.
OTOH, I’d hate to be in Support’s shoes and have to say to a customer, “Well, first we need to collapse your system to see what’s going on…”
BTW, if you’re not familiar with the Lambda calculus, Alonzo Church, and Alan Turing, I strongly urge you to read up on it. It changed the way I think about software in fundamental and useful fashion. http://en.wikipedia.org/wiki/Lambda_calculus