Saturday Chum Stew: Water, Vegas, Revolts, and Death. A Typical Week.

userpic=observationsSaturday, and time to clear out the news links before a busy weekend. Hopefully, you’ll find something of interest in these:

 

Share

A Matter of Time: Mail, Mobile Phones, and Mainframes

userpic=anniversaryToday’s lunchtime news chum collection comes to you courtesy of Timex, for it is all about time and anniversaries. This is appropriate, as NIST is about to introduce a new, more-accurate atomic clock.

  • Mail. This week marks the 10-year anniversary of Gmail. Many of you may remember life before Gmail. I certainly remember the days of command-line email — /bin/mail, mailx, and numerous other mail readers (I was particularly fond of using email within emacs). Then we moved to nicer email clients, such as Pegasus, while the Corporate folks dealt with Outlook and Notes. Web-based email, at that time, was horrid — limited storage, limited interfaces, limited searching. Google changed all that with gigantic limits and great interfaces, all for the cost of your soul (no, that not right) your privacy (getting closer) the ability to search through your mail and sell you stuff based on it (that’s the ticket). Gmail isn’t perfect — there still isn’t the ability to work with digital certificates and encrypted mail. Hopefully we’ll get that. Otherwise, Gmail has become such a juggernaut (especially when combined with Android) that it is unstoppable.
  • Mobile Phones. Speaking of Android, this week is also the 41st anniversary of the first mobile phone call. Talk about life-changing devices. No longer can you hide anywhere — being incommunicado is now unthinkable. We’ve got from only a few having cellphones to everyone having them with them 24×7. In fact, you now no longer have just a phone, but an entire miniature computer with you. As evidence, I just added a page to my Passover Hagadah to remind people to turn off their cell phones; yet another form of escaping from slavery!
  • Mainframes. This week also is the 50th anniversary of the IBM 360 mainframe. Now, many of you youngsters (hey, you, get off my lawn) don’t even know what a mainframe is, so bear with me. Back in the 1950s, computers were one-shots — built for a specific purpose, for a specific task. Some smaller computers (such as the IBM 7090) started to come in, but they still often used plugboards and were unsuitable for the enterprise. In the 1960s, IBM introduced the 360 line — a range of computers, all running a common OS (at that time, OS/MFT) with common machine instructions that were extensible. Business could now afford computers. I programmed on a number of 360 systems: the 360/50 at LA Unified, the 360/91 and 360/75 at UCLA, and later, the 370/3033 at UCLA.

 

Share

STEM and Cybersecurity Education – A Monday Lunchtime Rant

userpic=cardboard-safeYesterday, my RSS feeds highlighted a provocative article: “STEM Stinks for Cybersecurity” (Forbes Magazine). In this article, the author argues that we don’t need more people with university degrees in science, technology, engineering, or mathematics — what we need is more people with Vocational Training (he calls it VoTech) who are familiar with the security tools and know how to run the security tools. I think this position misunderstands both STEM and Cybersecurity.

Let’s start with STEM. The author seems to believe that the emphasis on STEM is at the university level — that we only want STEM degrees. That’s wrong and misguided. Emphasizing STEM is important much earlier — from the first days of education to the end of high school. We need to be raising students that are unafraid — who perhaps even love — science, engineering, math, and technology. The ability to understand these disciplines is key to having adults who think critically, and who can recognize pseudo-science when they see it (and thus, believe neither the creationists nor the climate-change-denouncers). Being familiar with these disciplines is also key if you are going to exist in the modern world, where technology is everywhere (and technical terms are everywhere). They are particularly important even if you are going into VoTech — just because you are working with tools doesn’t mean you don’t apply scientific principles or use mathematics. In fact, most CNC tool programmers use mathematics regularly. Familiarity with technology is required in almost every field today — even the soft fields are making extensive use of technology.

Let’s now turn to the question of whether VoTech is sufficient for Cybersecurity. I’ll start by saying that I have no problem with encouraging vocational technology — I think it was a disaster when shop classes were removed from schools, and I’ll support vocational training. Having trained machinists and technicians and repair support is vital to the success of most operations (and it should go without saying that all need to be familiar with STEM). But with respect to Cybersecurity, my opinion differs.

Technicians trained in using tools are only as good as the tools they use. While this is fine in manufacturing, it’s not in Cybersecurity. Cybersecurity tools can only find what they are programmed to find — which are signatures of yesterday’s attack. VoTech Cybersecurity experts, as a result, can typically only find what the best of their tools find. Perhaps, as they gain lots of experience, they will be able to go outside of that box and identify additional attacks. The basic trainee won’t; our systems won’t have time to wait.

Cybersecurity requires individuals who are familiar with technology, systems, mathematics, engineering… and can think critically, and can present their thoughts and findings (which is where the arts come in, and why you see a movement from STEM to STEAM). Successful cybersecurity is much more than running vulnerability scans. It is getting in with the engineering team from day 0 — identifying the security requirements and how they trade off other engineering and mission requirements. These are skills you learn in engineering courses and software and system design courses, not vocational training. It is being able to recognize results and findings that just seem off, and having the ability to track down the root cause (and not just the symptom of the day). The ability to recognize that “this doesn’t smell right” is a critical thinking skill; I don’t believe a VoTech trainee will have that without significant experience. Successful cybersecurity is being able to assess your findings in the context of the larger system, mission, and business picture — a perspective that someone who is only familiar with tools will not have. Successful cybersecurity is looking at all aspects of the system from the low hardware up through the design layers, from operational procedures and processes to suppliers. An emphasis on tools alone does not give that ability. Lastly, cybersecurity requires individuals that can think out of the box, because that’s what the adversaries do. Stopping the script kiddies is easy; VoTech can easily catch the low-lying fruit. The real threat comes from the determined adversary, and they don’t do what you (or your tools) expect.

Don’t get me wrong — technicians are important. If that is the highest level of skill you can obtain, and you’ve had that K-12 STEM/STEAM education, go for it. Some people work best with their hands. But if you can go on and get that STEM/STEAM degree, you will be much more successful and much more useful in the field (plus, you’ll earn significantly more over your lifetime — enough, perhaps, to pay off your student loans :-)).

Share

Saturday Stew: From XP to Exes, from New Coins to Old History

Observation StewIt’s Saturday, and that means it is time to clear out the links for the week. This has been a busy week, with a major recorganization (which was more of an org chart relocation) at work (means loads of “all-hands” meetings full of sound and fury, saying little), loads of documents to review, and loads of stuff to catch up on. As a result, I rarely got time to look at the news over lunch, and have only collected a few things that didn’t them. Let’s get to them:

  • The Death of XP. My RSS feeds are full of dire warnings about continuing to use XP after support stops on April 8. As it is, I have three XP machines at home: two that are just sitting, turned off, and one that is used solely as a print server. Still, I am thinking about replacing it, and two articles caught my eye. The first looks at 3 Linux alternatives to upgrading Windows–I’d seriously think about upgrading at least one to Linux if it can work as a print server on a Windows network. The second talks about how Microsoft is offering special deals of $100 for those upgrading from XP. With some Windows 8 machines in the $200-$300 range, this brings systems to the noise level.
  • Challenging Coins. Two interesting articles on coins this week. The first talks about the new £1 coin Britain is introducing. It will be 12-sided, and incorporate different-colored metals, for a faux gold and silver look, instead of the mostly copper blend now in circulation, and boast a high-tech anti-forgery feature used in paper money. It looks like it is complicated to make. Even more complicated is a new domed collectable coin being made by the US Mint: a domed coin commemorating baseball. Evidently, it was very hard for the mint to manufacture, and took a bit of experimenting to get right. What’s interesting here is reading the comments — there are a large number of people who do not understand that collectable coins and stamps make the government money.
  • Training For It. About a week or so, I had set aside a story about a railroad club in Orange County that had their trackage stolen, intending to send them a little something. Turns out I wasn’t the only one: the club has received thousands of dollars in donations. A nice reminder that there are a lot of good people in the world.
  • Bad Design. Here are two articles about some bad designs. The first is about a new device you can slap on a milk carton–it uses nanotechnology to indicate visually if the milk is good or bad. So what’s the problem? According to the article, “red” is good, “green” is bad. This is the opposite of how red and green are nomally used in interfaces, and I predict people will get sick from the “green is good” hardwiring. The second is about golfing: it appears that titanium clubs striking rocks can create sparks that start brush fires. Perhaps they should give golf clubs to people on Survivor.
  • Out of This World. I’ve had this article sitting for a few weeks, but nothing seems to want to pair with it. Baker is a dying town — once home to the largest thermometer in the world, it is now slowly fading into the desert. But the owner of Alien Jerky wants to change that — and one way is to build a flying saucer shaped hotel.
  • The Jewish Valley. I’m into history. I’m into Judaism. So naturally, I’m into the history of Jews in the San Fernando Valley. Many years ago, Rabbi John Sherwood and I even toyed with the idea of writing a book on the subject. So here’s an interesting article in that vein: it explores the early days of the Valley Jewish Community Center, which became the Conservative synagogue Adat Ari El. This is the synagogue that was the parent of most Conservative synagogues in the valley, just like Temple Beth Hillel was the first Reform congregation and was essentially the parent of most Reform congregations in the valley.
  • Marital Success. What makes a successful marriage? Is it your partner? It is living together before you get married to work out the problems? Is it “murder frequently, divorce never?” According to this article from Atlantic, it is being mature when you get married. An exploration of the science of cohabitation shows that the older people are when they make their long-term commitment as a couple, the more likely that couple will stay together. The study found that individuals who committed to cohabitation or marriage at the age of 18 saw a 60 percent rate of divorce. Whereas individuals who waited until 23 to commit saw a divorce rate that hovered more around 30 percent. I got married when I was 25, and next year we will have been married for 30 years. As they say, you do the math.

 

Share

Death and Technology

userpic=compusaurThis has been another busy week, and so I haven’t had the time to post my usual news chum. Still, I have collected some for you, and as I’m working from home this morning, let me share an early morning collection dealing with death and technology; that is: dying technology, and technology that kills.

Share

Tech Help Needed: MS Word HTML to DOCX

userpic=compusaurOh, Great Internet Guru. Your technical help is required.

I’m writing some perl scripts at work that have as one of their ultimate end goals the generation of an MS Word document that can ideally serve as a subdocument in a master document/subdocument arrangement. I’ve done Master/Subdocuments before with DOCX format, and I’ve discovered that if the master is a DOC, it will look for subdocuments that are DOCs.

So far, I’ve got the script generating the variant of HTML that Word understands so that it can get the proper formats (e.g., I copy the prologue that defines the Word formats I need and generate HTML with appropriate CLASS= statements). This gives me a standalone .htm file, which I can rename as .doc and Word handles just fine. However, if you save it, Word knows it is really HTML and creates this funky subdirectory with files that it really doesn’t use.

I’ve been looking for a way that I can convert this .HTM or .DOC file into a real Word .DOC or .DOCX file without interaction (i.e., from the command line). I tried going the Macro approach, and even found that it saves the macro in that subdirectory for the .HTM files… however, the security restrictions on our systems here mean that I can’t execute the macro from the MS Word command line via /m . There’s a file WORDCONV.EXE in the Office12 directory, but it doesn’t seem to do anything, and I can’t seem to find any documentation on it.

So, for those MS Word gurus out there — any ideas? I can live with what I’ve got now (the .htm file I rename); I’d just like something cleaner.

Share

A Question for Folks with Time Warner Internet

userpic=toshibaA question for those folks using Time Warner for Internet. I currently use T-W. Our setup is the Time Warner RCA cable modem, connected to a Linksys Router (older, no wireless), which is connected to a Belkin router that has both wireless and wired network access. Recently, the Linksys has been wedging, requiring a power cycle. I remember we retained this setup when we got TW internet because of some oddity with the RCA Cable Modem — it registered MAC addresses or something and wouldn’t talk to the Belkin.

Does this sound at all familiar to anyone? If I wanted to go about removing the Linksys from the loop, what’s the best way to do it? I can plug the Belkin directly into the RCA Cable Modem, or get a new modem entirely? Is this an issue of timing — that is, power-cycle both the RCA Cable Modem and the routers, replace/rearrange the routers, power them up, and then (and only then) powercycle the RCA cable modem.

Advice is appreciated. The Linksys is about 7 years old, the Belkin perhaps 3-4 years old.

Share

Skeuomorphism. Love It. Hate It.

userpic=father-and-sonA big word in design circles these days is Skeuomorphism. Those who design interfaces are gnashing teeth and bemoaning the skeuomorphism in today’s interfaces, and newer interfaces are supposedly going to eschew it entirely. What is skeuomorphism? According to Wikipedia, it is when “a physical ornament or design on an object made to resemble another material or technique.” In other words, it is when an application used to delete files looks like a trashcan, an icon indicating saving files looks like a floppy disk, directories look like folders, email looks like envelopes, and (in general) thinks look like their archaic real world equivalents. Apple is supposedly going to a flat design and dropping skeuomorphic icons in the next version of iOS, and Windows has already started to do it in the flat design of Windows 8.

What got me thinking about skeuomorphism was a segment of this week’s Science Friday that we listened to on the drive home. This segment talked about helping seniors to tackle new technology. It talked about how seniors could be introduced to use the iPad and the iPhone, how to teach them to use computers, how they can be set in their habits… and how one can teach new technology by relating it to older things they know.

Yup. You can put 2 and 2 together as well as I can. The move away from skeuomorphism could be an attempt to get seniors — or at least less adaptable seniors — off the new technology. If you are dealing with a senior who can’t even figure out the power button, delete files, or do any simple tasks… now try imagine explaining it when the icon to do the task is something they don’t recognize.

So what are your thoughts? Is moving away from skeuomorphic design a good idea or a bad idea? What will be its impact on seniors?

Share