Tuesday, March 10, 2015
There were a lot of guys from Samoa and Guam...
Geek: “Dieharder” random number generator test suite...
Geek: “Dieharder” random number generator test suite... I hadn't run into this before. There have been several times when I wished I had access to such a test suite. Digging into this will make a good weekend project for me sometime...
Geek: a searchable catalog of NASA open source software...
Geek: a searchable catalog of NASA open source software... There's quite a bit of interesting stuff in here...
Dasatinib and quercetin...
Dasatinib and quercetin... You may be hearing a lot more about these. Quercetin is available over the counter today (though I have no idea what the quality of it is, and the supplements industry is notoriously fraud-filled).
6.5 million Americans are over 112 years old...
6.5 million Americans are over 112 years old... Not really, of course. But that's what the Social Security Administration's records say. You can probably guess what a wide door that opens for fraud – and, of course, that door is being used by tens of thousands of crooks. At least tens of thousands, and quite possibly, many more.
Who's the idiot that thought it was a good idea for the federal government to manage healthcare? Every time we turn over a bureaucratic rock, we find more festering incompetence, fraud, and waste. I'd have thought the Post Office was all the example anyone needed. The $900 toilet seats purchased by the Pentagon might have been another clue. The “stay in line until you die” lists at the Veteran's Administration might have clued someone in, too. Apparently all of this together is still insufficient to convince the progressives that it's a bad idea to have government managing anything...
Who's the idiot that thought it was a good idea for the federal government to manage healthcare? Every time we turn over a bureaucratic rock, we find more festering incompetence, fraud, and waste. I'd have thought the Post Office was all the example anyone needed. The $900 toilet seats purchased by the Pentagon might have been another clue. The “stay in line until you die” lists at the Veteran's Administration might have clued someone in, too. Apparently all of this together is still insufficient to convince the progressives that it's a bad idea to have government managing anything...
Life in Paradise...
Life in Paradise... For the past three days, every afternoon we've had people showing up at our door with complete evening meals – hot, tasty food ready to eat. Two of these times the people were complete strangers to us. Why is this happening? That's a bit of a story...
It started in our driveway last Thursday afternoon, as Debbie and I walked out to her truck to drive up to Angie's (in Logan) for dinner. We hadn't been there for a couple weeks, and we both felt like some comfort food. Our driveway still had patches of ice, but the afternoon was warm and it was melting. Wet ice, as you may know, is very slippery. Then add to that the fact that Debbie was wearing leather-soled cowboy boots. They might as well have been Teflon-coated. You can probably guess what happened next: her slippery feet slipped on the slimy ice, and down she went.
After an uncomfortable night, we went to see a doctor on Friday morning. The verdict: a “strained” back and knee. A “strain” is less severe than a “sprain”, but more than just “pulled”. I'm not sure how they come up with this terminology, but the doctor made it clear this was nothing to worry about, that she'd recover completely and quickly, and she just needed some rest, to wear a knee brace for a while, and a little pharmacological assistance (muscle relaxant and analgesic). Home we went.
Fast forward to Saturday morning, when our friend and neighbor Tim D. came over to visit. I was out in the barn working on the wiring, and he went in to chat with Debbie. When she came hobbling slowly to the door, wearing the brace, he knew something was up. He got all the details when talking with her.
I've learned enough about living in an LDS (Mormon) community by now that I should have known what was going to happen next, but it got me by surprise anyway. Tim is a former bishop, a devout Mormon, and upon learning about Debbie's injury (however minor!) he sprang into action as though she was now a quadriplegic. A few hours after he left, Alan and Nikki L. (another set of friends and neighbors) showed up to visit with Debbie. They were there both to comfort her and to interrogate her about our dining preferences. Later that afternoon, they showed up with a ready-to-eat meal, which of course we disposed of very quickly. This is despite our protestations that all this was entirely unnecessary, as (a) I can cook, and (b) Debbie wasn't bedridden, just slowed down. They insisted anyway, Alan telling me, basically, to “shut up and embrace it”, because it was going to happen no matter what we said.
Sunday and Monday afternoon, women who were part of the local LDS ward's Relief Society showed up with another installment. Sunday's meal was particularly good: roast beef with potatoes, carrots, a salad, and dessert, all ready to eat.
Yesterday morning, Michelle H. (the wonderful woman who does the heavy cleaning in our house every couple of weeks) came over as planned – but she was all prepared to do a lot more (I think Debbie's condition has been wildly exaggerated in the rumor mill) to help out. She was ready to do the cooking (note the assumption that the male animal of the household can't prepare food!), take care of the animals, etc. We didn't actually need any of that help, but it was comforting to know that if we did need it, it would be readily available.
The local Mormons are enjoying our discomfiture with all this, I think :) But I have to say that we're enjoying the food and the opportunity to meet some members of our community who are new to us.
Monday morning I ran down to the Post Office to pick up our mail. When I walked in the door, the postmaster asked me how Debbie was doing. His assistant wanted to know if we were happy with the meals. They both knew all the details of Debbie's fall, which is typical of any small community, I suspect – but after spending so much time in California, it's sure not something I'm used to. Everyone is connected here, somehow (including, of course, through the LDS church that the majority of our community are members of). Brent, our postmaster, is the brother of the woman who runs the local Relief Society. Linda, his assistant, is actually a neighbor of ours (and a water rights expert currently working on getting our well permit). Both are LDS.
Out in the Post Office lobby, where the P.O. boxes are, another woman greeted me with good wishes for Debbie. I had no idea who this woman was, and it must have showed in my face, so she explained that her husband pointed me out as they drove into the Post Office (the lobby has big windows). He knows me because we'd previously chatted in the Post Office lobby, and he remembered where I lived – and had heard in church that Debbie (whom he'd never met) had fallen. So when his wife ran in to pick up their mail, she was full of concern and good wishes – even though she'd never met (or heard of) either of us before!
We love living here. After forty-plus years in California, land of adjacent strangers, to live in a community that actually is a community is jarring in some ways, but comforting in so many more...
It started in our driveway last Thursday afternoon, as Debbie and I walked out to her truck to drive up to Angie's (in Logan) for dinner. We hadn't been there for a couple weeks, and we both felt like some comfort food. Our driveway still had patches of ice, but the afternoon was warm and it was melting. Wet ice, as you may know, is very slippery. Then add to that the fact that Debbie was wearing leather-soled cowboy boots. They might as well have been Teflon-coated. You can probably guess what happened next: her slippery feet slipped on the slimy ice, and down she went.
After an uncomfortable night, we went to see a doctor on Friday morning. The verdict: a “strained” back and knee. A “strain” is less severe than a “sprain”, but more than just “pulled”. I'm not sure how they come up with this terminology, but the doctor made it clear this was nothing to worry about, that she'd recover completely and quickly, and she just needed some rest, to wear a knee brace for a while, and a little pharmacological assistance (muscle relaxant and analgesic). Home we went.
Fast forward to Saturday morning, when our friend and neighbor Tim D. came over to visit. I was out in the barn working on the wiring, and he went in to chat with Debbie. When she came hobbling slowly to the door, wearing the brace, he knew something was up. He got all the details when talking with her.
I've learned enough about living in an LDS (Mormon) community by now that I should have known what was going to happen next, but it got me by surprise anyway. Tim is a former bishop, a devout Mormon, and upon learning about Debbie's injury (however minor!) he sprang into action as though she was now a quadriplegic. A few hours after he left, Alan and Nikki L. (another set of friends and neighbors) showed up to visit with Debbie. They were there both to comfort her and to interrogate her about our dining preferences. Later that afternoon, they showed up with a ready-to-eat meal, which of course we disposed of very quickly. This is despite our protestations that all this was entirely unnecessary, as (a) I can cook, and (b) Debbie wasn't bedridden, just slowed down. They insisted anyway, Alan telling me, basically, to “shut up and embrace it”, because it was going to happen no matter what we said.
Sunday and Monday afternoon, women who were part of the local LDS ward's Relief Society showed up with another installment. Sunday's meal was particularly good: roast beef with potatoes, carrots, a salad, and dessert, all ready to eat.
Yesterday morning, Michelle H. (the wonderful woman who does the heavy cleaning in our house every couple of weeks) came over as planned – but she was all prepared to do a lot more (I think Debbie's condition has been wildly exaggerated in the rumor mill) to help out. She was ready to do the cooking (note the assumption that the male animal of the household can't prepare food!), take care of the animals, etc. We didn't actually need any of that help, but it was comforting to know that if we did need it, it would be readily available.
The local Mormons are enjoying our discomfiture with all this, I think :) But I have to say that we're enjoying the food and the opportunity to meet some members of our community who are new to us.
Monday morning I ran down to the Post Office to pick up our mail. When I walked in the door, the postmaster asked me how Debbie was doing. His assistant wanted to know if we were happy with the meals. They both knew all the details of Debbie's fall, which is typical of any small community, I suspect – but after spending so much time in California, it's sure not something I'm used to. Everyone is connected here, somehow (including, of course, through the LDS church that the majority of our community are members of). Brent, our postmaster, is the brother of the woman who runs the local Relief Society. Linda, his assistant, is actually a neighbor of ours (and a water rights expert currently working on getting our well permit). Both are LDS.
Out in the Post Office lobby, where the P.O. boxes are, another woman greeted me with good wishes for Debbie. I had no idea who this woman was, and it must have showed in my face, so she explained that her husband pointed me out as they drove into the Post Office (the lobby has big windows). He knows me because we'd previously chatted in the Post Office lobby, and he remembered where I lived – and had heard in church that Debbie (whom he'd never met) had fallen. So when his wife ran in to pick up their mail, she was full of concern and good wishes – even though she'd never met (or heard of) either of us before!
We love living here. After forty-plus years in California, land of adjacent strangers, to live in a community that actually is a community is jarring in some ways, but comforting in so many more...
Monday, March 9, 2015
Taking notes...
Taking notes... I noticed many years ago that if I took notes, pen on paper style, at a lecture or meeting, I'd remember the important things much better. This was true even if I threw the notes away and never looked at them again. In my corporate life I then developed a habit of taking extensive notes at meetings and often even during one-on-one conversations. When I was managing teams of engineers, this was extremely useful, as it allowed me to remember many different things in a complex and ever-shifting environment.
Now there's research that backs up my observation about the value of taking notes...
Now there's research that backs up my observation about the value of taking notes...
Replace alcohol?
Replace alcohol? Ryan Cooper wants the government to fund research for a replacement for alcohol – because it's such a terrible recreational drug (highly addictive and physiologically damaging with heaving long-term use). He makes the point that alcohol is worse in many ways than the currently illegal recreational drugs, including even heroin.
I'm not sure we need new research here. Seems to me we just need to make the already existing, much safer drugs (like marijuana) legal. Consumers can then freely choose to abstain, to use the safer drugs, or continue to use alcohol...
I'm not sure we need new research here. Seems to me we just need to make the already existing, much safer drugs (like marijuana) legal. Consumers can then freely choose to abstain, to use the safer drugs, or continue to use alcohol...
Follow the money...
Follow the money... Oh, my:
"Follow the money." That apocryphal phrase, attributed to Watergate whistle-blower "Deep Throat," explains why the biggest threat to Hillary Rodham Clinton's presidential dreams is not her emails. It's her family foundation. That's where the money is: corporate money, foreign money, gobs of money sloshing around a vanity charity that could be renamed "Clinton Conflicts of Interest Foundation."If these allegations prove to have any truth to them at all, that really might doom Hillary's quest for the monarchy presidency...
Sunday, March 8, 2015
Human-generated random data...
Human-generated random data... This is, so far as I can tell, a completely useless (and almost certainly not random!) idea. Also, it appears to be broken. But their “About” page is one of the best I've seen in a long time :)
The Apple way...
The Apple way... The Apple Watch had a challenge. Unlike any of Apple's previous products, a watch is perceived by many to be a fashion accessory or even a piece of jewelry. That means that some customers will want the rich look of gold – preferably, a nice 18K gold as is traditional for watchmakers going back hundreds of years. Probably any other manufacturer would simply have said “OK, make a gold model.” Apple noted, however, that traditional 18K gold has two problems. First, it's expensive, especially when gold is going for $1,200+ an ounce. Second, it's relatively soft – though 18K gold is much harder than 24K gold, it's still soft enough that it's easily scratched.
So Apple developed a new kind of 18K gold (see this explanation) that uses less gold and is more durable. Very clever, that. Also a great example of what can happen at the conjunction of visionary product development, scale, (almost) unlimited funding, and total vertical integration...
So Apple developed a new kind of 18K gold (see this explanation) that uses less gold and is more durable. Very clever, that. Also a great example of what can happen at the conjunction of visionary product development, scale, (almost) unlimited funding, and total vertical integration...
Quote of the day...
Quote of the day... This one is from a New York Times article (I read them so that you don't have to :) about the things the must be done to make online education attractive as an alternative to traditional (and very expensive) universities. The article focuses on credentialing, specifically on alternatives to the traditional college degree that's embodied in a diploma. As my long-time readers (all four of you) will know, I'm not happy with the existing diploma system, as the possession of a diploma from an American university really tells you very little about what that person actually knows, or can do. So this quote really caught my eye:
Meanwhile, the best credentials I know of currently are open source project contributions...
The standard diploma has roughly the same amount of information that prisoners of war are required to divulge under the Geneva Conventions.Ha! Yes, that's absolutely true. The fact that a candidate programmer has a degree from (say) Carnegie-Mellon University tells a prospective employer almost nothing at all about that candidate's suitability for the job. Some of the alternative credentialing ideas mentioned in the article (Mozilla's Open Badges, in particular) are attempting to address that problem. Traditional universities have a conflict with these alternative credentialing ideas, though – to the extent that they succeed, they will (a) provide less expensive alternatives to the university, and (b) expose the mediocrity of the education those expensive universities are delivering.
Meanwhile, the best credentials I know of currently are open source project contributions...
European tree of the year...
European tree of the year... This oak tree in Orissaare, Estonia, was just voted the 2015 “Tree of the Year” in a contest amongst 14 European countries.
I've traveled extensively in Estonia in the period from just after their independence from the Soviet Union in 1991 through 2004. The map that guided my explorations had numerous interesting botanical specimens marked on it, and after seeing the beauty of a few of them I started making it a point to visit them. This tree in Orissaare was one of those marked on that map, and I visited it twice – once in about 1995, then again in 2002, on one of my last visits to Estonia.
This particular tree is located on the eastern side of Saaremaa, the biggest Estonian island in the Baltic Sea, on the western border of the country. If you view the map at left on Google Maps, you'll be able to see exactly where it's located by zooming out.
The first time I visited this tree was before the economic boom in Saaremaa, and the town's infrastructure was still in pretty bad shape. I bought my lunch in a small grocery store, and sat beneath the tree to have myself a little picnic. A couple of people walked by, but nobody stopped to talk. The second time I visited, Orissaare (and the rest of the island) was far more prosperous, with lots of fresh paint, repaired structures, and even a bit of pavement here and there. On that visit, I couldn't have my picnic under the tree, as there were all sorts of people playing several different games (though not football!) right around the tree. I sat on the edge of the field to eat my picnic lunch, which that time came from a small, new restaurant serving allegedly local cuisine. I'm not entirely sure what it was, but it had fish, potatoes, and a lot of dill in it – and was quite tasty!
It was fun to see a tree I know in the news :)
I've traveled extensively in Estonia in the period from just after their independence from the Soviet Union in 1991 through 2004. The map that guided my explorations had numerous interesting botanical specimens marked on it, and after seeing the beauty of a few of them I started making it a point to visit them. This tree in Orissaare was one of those marked on that map, and I visited it twice – once in about 1995, then again in 2002, on one of my last visits to Estonia.
The first time I visited this tree was before the economic boom in Saaremaa, and the town's infrastructure was still in pretty bad shape. I bought my lunch in a small grocery store, and sat beneath the tree to have myself a little picnic. A couple of people walked by, but nobody stopped to talk. The second time I visited, Orissaare (and the rest of the island) was far more prosperous, with lots of fresh paint, repaired structures, and even a bit of pavement here and there. On that visit, I couldn't have my picnic under the tree, as there were all sorts of people playing several different games (though not football!) right around the tree. I sat on the edge of the field to eat my picnic lunch, which that time came from a small, new restaurant serving allegedly local cuisine. I'm not entirely sure what it was, but it had fish, potatoes, and a lot of dill in it – and was quite tasty!
It was fun to see a tree I know in the news :)
Saturday, March 7, 2015
All the sub-panelz are mine!
All the sub-panelz are mine! I finished wiring in the sub-panel for the woodworking shop this afternoon. The photo at right shows it with the cover off, and absolutely nothing wired into it yet :) But it has power, and I've tested the safety ground and neutral wires, just to be sure I don't have problems later on.
After I finished with this, I spent a couple hours getting started on the lights in the garage section. It will probably take me a couple days just to get the basic wiring in place, then another day to actually install the ten lights I'm putting up in there...
After I finished with this, I spent a couple hours getting started on the lights in the garage section. It will probably take me a couple days just to get the basic wiring in place, then another day to actually install the ten lights I'm putting up in there...
Never in a million years...
Never in a million years ... would this have occurred to me: photographing people covered in honey. It's far more interesting and beautiful than I would have guessed. Watch the video at the link...
Uranium emissions, visualized in a cloud chamber...
Geek: integer overflow/underflow in C/C++...
Geek: integer overflow/underflow in C/C++... My first reaction on reading this paper was this: geez, guys, it's 2015. This problem has been around since about 1945. Is this really still a mystery and a source of problems? I've run into this issue (and other numerical representation issues) over my entire career, and I've no sense that things have actually gotten better over time.
With respect to integer overflow/underflow, the fundamental issue is very easy to understand: computers generally represent integers in a way that limits the range of integers that can be represented. For example, in today's computers a single byte can represent all the integers between 0 and 255. If you try to add, say, 200 + 100, the result (300) cannot be represented in a single byte – that's an example of integer overflow.
We humans don't generally run into integer overflow or underflow, as we don't have any particular limits on the size of integers we can represent. Computers, on the other hand, do have this limitation – and therefore computer programmers have to deal with it. This is where the problems start, as there are many possible ways one could deal with it – including ignoring the possibility altogether, which is in practice what most programmers actually do. This is the source of much trouble.
The problem is complicated by at least two things in modern computers: the fact that multiple sizes of integers are available (generally, but not always, some even number of bytes), and the fact that both signed and unsigned integers can be represented. For instance, a single byte unsigned can represent integers in the range 0..255, whereas a single signed byte can represent integers in the range -128..127. Older computers (and a few still in production) through a different variable into the mix: they represented integers by schemes other than the now-ubiquitous two's complement encoding. I've worked extensively with computers that used one's complement integer encoding and signed binary coded decimal (where the sign is held in a special bit), and to a lesser extent with zoned decimal encodings. Each of these has their own special variations of the overflow/underflow problem, though of course being fixed size encodings they all have the problem.
Anyway, it just seems kind of silly that at this stage of software development we still don't have a standard way of handling integer overflow/underflow, and we still haven't managed to educate programmers about the problems they cause. Actually, it's worse than that – even within the past few years I've run into programmers in very responsible positions, sometimes with years of experience, who don't actually understand the source of overflow and underflow, and who believe the problem can be safely ignored most of the time. They're wrong and they don't even know it...
With respect to integer overflow/underflow, the fundamental issue is very easy to understand: computers generally represent integers in a way that limits the range of integers that can be represented. For example, in today's computers a single byte can represent all the integers between 0 and 255. If you try to add, say, 200 + 100, the result (300) cannot be represented in a single byte – that's an example of integer overflow.
We humans don't generally run into integer overflow or underflow, as we don't have any particular limits on the size of integers we can represent. Computers, on the other hand, do have this limitation – and therefore computer programmers have to deal with it. This is where the problems start, as there are many possible ways one could deal with it – including ignoring the possibility altogether, which is in practice what most programmers actually do. This is the source of much trouble.
The problem is complicated by at least two things in modern computers: the fact that multiple sizes of integers are available (generally, but not always, some even number of bytes), and the fact that both signed and unsigned integers can be represented. For instance, a single byte unsigned can represent integers in the range 0..255, whereas a single signed byte can represent integers in the range -128..127. Older computers (and a few still in production) through a different variable into the mix: they represented integers by schemes other than the now-ubiquitous two's complement encoding. I've worked extensively with computers that used one's complement integer encoding and signed binary coded decimal (where the sign is held in a special bit), and to a lesser extent with zoned decimal encodings. Each of these has their own special variations of the overflow/underflow problem, though of course being fixed size encodings they all have the problem.
Anyway, it just seems kind of silly that at this stage of software development we still don't have a standard way of handling integer overflow/underflow, and we still haven't managed to educate programmers about the problems they cause. Actually, it's worse than that – even within the past few years I've run into programmers in very responsible positions, sometimes with years of experience, who don't actually understand the source of overflow and underflow, and who believe the problem can be safely ignored most of the time. They're wrong and they don't even know it...
Oopsie...
Oopsie... Spelling errors can creep into the most unlikely places. Like, for instance, the title on a video associated (screen capture at right) with this Financial Times article. I suspect someone's going to get a little talking-to this morning – those British publications take their spelling and style guidelines quite seriously :)
Email outage...
Email outage... Yesterday our family email (which is hosted by GMail) was down for close to 24 hours. The symptoms were that we stopped receiving any new mail, and the URL we normally used to access our mail stopped working (though the default GMail URL still worked). If you're the geekly sort, you probably immediately said “DNS problem!”, and in fact that's what it was. Once that got resolved, our missed emails started trickling in, much to the general relief of my family members.
Two observations from this experience:
First, how dependent on email (and the Internet, more generally) we've become! Our email has become one of the rhythms in our lives – we expect certain emails to arrive at certain times of the day, and when they don't arrive, it feels like a major disconnection – a bit like the power going out, or the road to your house being shut down. Some of my family members, when reporting the outage, had a distinct tinge of, well, panic in their voices. In actual fact, it's nothing so vital (though for my sister, who uses email in her business, a bit more so). Nevertheless, when it's cut off, we don't like it. Not. One. Little. Bit.
Second, how amazingly reliable email has become. My family has been using this (free!) GMail service for about ten years now. In all that time, we've only had a couple of short outages. We access our email from the web on multiple browsers, from email “fat clients” (like Mozilla's Thunderbird), from iPads, and from smart phones. Wherever we are, whenever we want it, however we want to access it – it just works. This reliability is in marked contrast to the self-hosted Microsoft Exchange email server that I maintained for roughly ten years prior to that. That beast would go down about once a week, and sometimes it took hours of troubleshooting (by me!) to get it back up again. I lived in fear of updates to that server, because about one in four of them would knock it offline. Contrast that with our GMail experience: I spend zero time managing the service, and it just always works. Well, almost always. Google deserves a great deal of credit for building such a reliable system. Such things do not happen by accident!
Two observations from this experience:
First, how dependent on email (and the Internet, more generally) we've become! Our email has become one of the rhythms in our lives – we expect certain emails to arrive at certain times of the day, and when they don't arrive, it feels like a major disconnection – a bit like the power going out, or the road to your house being shut down. Some of my family members, when reporting the outage, had a distinct tinge of, well, panic in their voices. In actual fact, it's nothing so vital (though for my sister, who uses email in her business, a bit more so). Nevertheless, when it's cut off, we don't like it. Not. One. Little. Bit.
Second, how amazingly reliable email has become. My family has been using this (free!) GMail service for about ten years now. In all that time, we've only had a couple of short outages. We access our email from the web on multiple browsers, from email “fat clients” (like Mozilla's Thunderbird), from iPads, and from smart phones. Wherever we are, whenever we want it, however we want to access it – it just works. This reliability is in marked contrast to the self-hosted Microsoft Exchange email server that I maintained for roughly ten years prior to that. That beast would go down about once a week, and sometimes it took hours of troubleshooting (by me!) to get it back up again. I lived in fear of updates to that server, because about one in four of them would knock it offline. Contrast that with our GMail experience: I spend zero time managing the service, and it just always works. Well, almost always. Google deserves a great deal of credit for building such a reliable system. Such things do not happen by accident!
Subscribe to:
Posts (Atom)



