- Rule #1 of aviation: don’t hit anything.
Clear violation of rule #1
- Windows IT Pro has a new compendium of its articles and coverage of Exchange 2013. Check it out.
- The ability to do discovery searches from a single locationin Office 2013/Lync 2013/SharePoint 2013/Exchange 2013 is going to sell a lot of SharePoint seats.
- Halo 4 has been terrific so far and I’m only partway through the second mission. 343 has a winner.
- I think some new gadgets may be coming to join the stable in the next week or two.
Thursday trivia #79
Filed under General Stuff
Apple releases fix for EAS calendar hijacking bug
Good news: Apple just released iOS 6.0.1, the release notes for which say that the update fixes “a bug affecting Exchange meetings.” More details here.
Filed under UC&C
Thursday trivia #78
- What I learned today: the difference between “unwatering” and “dewatering.”
- Just logged 0.8 hours of simulated instrument time. That means I have officially met all of the FAA requirements for the private pilot license except the checkride. Onward!
- It’s official: the VA has announced that Acuitus is doing a pilot program using the Digital Tutor to train unemployed veterans.
- Being back in Alabama reminds me that there is such a thing as fall weather; it was 33° this morning when I woke up.
- Does the Internet run on gasoline? Sort of, but it mostly runs on diesel. This article expounds on some of the things I mentioned the other day. tl;dr version: put your data center someplace safe.
- Here’s a playlist with some of the new music I enjoyed at Voodoo.
Filed under General Stuff
Voodoo Music Experience 2012
Wow.
The boys and I just wrapped up a visit for New Orleans for the Voodoo Music Experience 2012. What a fantastic time!
Friday morning I picked them up in Birmingham and we had a pleasant drive down to the city, stopping at Charlie’s Catfish House along the way. The boys were a bit nonplussed to be served whole catfish but that didn’t really slow them down. We got to the festival about 3:30pm and immediately started exploring. I was surprised that security didn’t turn me away because I was carrying a “professional camera” (you know, the kind with a detachable lens) but I wasn’t about to complain. After some wandering, David and Tom went to the EDM stage to see Nervo while Matt and I headed off to go see Thomas Dolby. We were no more than 10′ from the stage for the show, which was outstanding. I’ve been wanting to see Dolby in concert for 30 years and thoroughly enjoyed getting to do so at long last. Bonus: he has a new album and played a couple of cuts from it. Extra bonus: he was joined on stage by Michael Doucet, who plays a mean fiddle. (Set list: “Europa and the Pirate Twins”, “One of our Submarines”, “Airhead”, “Pulp Culture”, then “Spice Train”, “Evil Twin Brother”, and “The Toad Lickers” from his new album, then “I Love You Goodbye”, “Hyperactive”, and “She Blinded Me With Science.”)
TMDR gettin’ down
After the show, I got to see my pal and (fellow Exchange MVP) Jason Sherry at the Thomas Dolby show. This was his 16th Voodoo show– an enviable record. I think he should win a prize. Matt and I also checked out Christian Ristow’s Face Forward sculpture, a giant metal head with an articulated, remote-controlled face, plus a giant metal crawfish whose antennae emit fire after dark.
show me your war face
We wandered around a bit more until it was time for the next EDM acts: JFK of MSTRKRFT, followed by Kaskade. (Actually, Die Antwoord was on stage but no way was I going to let the boys go see them; they are incredibly NSFW.) JFK put on a pretty good set but was not very engaged with the crowd. Kaskade, on the other hand, killed: fantastic set, good crowd involvement, and a great vibe. He was actually pretty laid-back; not really what I was expecting for an EDM set. Matt was able to talk us into the VIP area on stage rights so we were pretty close to the action, which was fantastic. David and Tom got right up front, too, which was a treat for them.
Notice the cool hat he’s wearing
As you might be able to tell from the photos, my night photo technique needs some work. Most of the concert pics I shot were with my D5100 and Nikon’s 55-200 f/4. This is a great all-around lens but I need to remember to aim the focus points when I’m shooting from a distance. EDM stages are tricky, too, because there are often large backlit screens behind the performer. This wasn’t a huge problem when we were off to the side in the VIP area but it was a problem for Metallica, as you will soon see.
Anyway, we went to bed exhausted but happy Friday, slept in a bit on Saturday, then skipped breakfast and went straight to Deanie’s Seafood. Of all the many restaurants in N’Awlins, this is one of the most resonant for me; it was one of my Aunt Betty’s very, very favorites and I have many happy memories of eating there with her when visiting the city. I wanted the boys to see it, and we had a delightful meal with bonus Aunt B storytelling thrown in. Then a quick drive back to City Park put us in position for another day of music. Saturday’s weather was quite a bit different– mid-50s with a steady chill wind and heavy overcast for almost the entire day. Luckily we found the one food stand that was selling hot chocolate, Quintin’s, and patronized it heavily.
Saturday’s lineup was pretty strong. We had planned to see DJ QBert and Metallica as our two main acts; Tom wanted to see AWOLNATION, and there were a few fill-ins that we’d decided to try (like Jim-E Stacks). We briefly stopped by for Carmine P. Filthy’s set (prominently featuring this guy, so Matt and I didn’t stay for long); it was pretty repetitive. I caught a few minutes of Sister Sparrow and the Dirty Birds, enough to decide that I’d give them a shot on Spotify. We connected with my cousin, world-famous sound guy and international man of mystery Chris Bloch. He got us into the mixing truck for Chicano Batman‘s set, where he spent a good chunk of time answering our stupid questions about audio production and mixing. As a bonus, I found that I quite liked the band’s mix of Afro-Brazilian-surf funk, so they’re now in my Spotify rotation. Another neat discovery: The Features put on quite a show near the hot chocolate place (though it took me a while to figure out they were singing “Golden Comb“, not “Golden Cone”).
Chris hard at work; yes, he really does know what all those knobs do.
Tom went to the AWOLNATION show and went crowd surfing, which excited him no end. The rest of us used the time to explore the food booths; I had a couple of really delicious crawfish pies, while David had shwarma and Matt a hot dog. We migrated over to the Metallica area about 30 minutes before their show and got decent seats in front of the sound tower (though the two older boys didn’t stay there; they ended up in the mosh pit.) As for the Metallica concert itself: it exceeded my expectations, especially given that they were replacing Green Day, a band I’ve never really liked. They deployed some awesome pyrotechnics for “One”, and gave us a nice mix of old and new(er) stuff, including “Master of Puppets,” “Wherever I May Roam,” “Enter Sandman,” and “Nothing Else Matters.” For their first encore they came out and started playing “American Idiot” by Green Day then stopped– James said, with mock sheepishness, “That’s all we had time to learn” before launching into some back-catalog stuff, closing with “Seek and Destroy.”
rock is serious business
Lars looks suspiciously like my friend Scott Mikesell
they were having almost as much fun as the crowd
After a solid two-hour performance, all of us were flat worn out. We went back to the hotel and got to bed about midnight, which was lucky given that we had made plans to meet Chris and Beth at Café du Monde the next morning at 7:30. The promise of beignets was enough to get the herd moving, and we enjoyed our bounty sitting on the levee steps overlooking the river and watching the sun right near Jackson Square.
After breakfast, we went back to the hotel to shower and pack; the stage acts weren’t scheduled to start until noon, so I figured we’d have time to go to Radosta’s for poboys. Nope– they’re closed on Sundays, so we drove back to the Quarter to go to Coop’s. Nope, they’re a 21-and-up place. We ended up eating more festival food, to which absolutely no one objected. We’d planned to see Dev, who never showed up– she couldn’t get out of NYC because of Hurricane Sandy. No one announced that to the crowd, unfortunately, so we waited around for a while and then eventually wandered off. (The excellent Voodoo mobile app did have a tiny scrolling ticker at the bottom of its main page that announced the news, but I’m not sure anyone actually saw it.)
We were soon back to the EDM stage for Modestep, self-described as a “live four-piece bass-heavy band from London.” They sure were! However, there was enough swearing that I made Matt leave about half an hour into the show, which was too bad– it was excellent otherwise. Plus they were playing in full sunlight, which was not only very pleasant but provided superb lighting for taking pictures.
this makes me think of John McEnroe saying “you cannot be serious”
someone’s having a good day at work
More festival dinner, then it was time to head over to Skrillex! The crowd for his show was huge– probably 2/3 as large as Metallica’s, but in a much smaller area. We all packed up towards the front, which was fantastic until the crowd started squeezing us. Even that was OK because we were all dancing more or less in unison. Even the crowd surfers were fun… until one of them got dropped more or less on Matt’s head. After that, he and I watched the rest of the show from a more open space towards the back of the crowd. I was far enough away that after it got dark none of my pictures were really spectacular; this is probably the best of the lot.
He played an absolutely killer set, including a remix of the theme from “The Fresh Prince” and a variety of his own songs. I was worn out from dancing by the end of the set, which is a sure measure of how good it was– it takes quite a performance to get me to shake my groove thang. (But don’t take my word for it; see this review.)
Immediately after the Skrillex set, we went back to the parking lot and drove straight through, arriving back in Huntsville about 2:45am. Matt and Tom slept pretty much the whole way; David lasted until about 12:45 and he zonked out too. Great time, and maybe we’ll do it again next year. The End.
Filed under Friends & Family, General Stuff, Reviews, Travel
Sandy shows that location does matter
I’m sure there will be zillions of other articles covering this in various trade publications, but right now, while I’m thinking about it, I wanted to dash off a couple of thoughts on how the cloud is affected by real clouds… like Hurricane Sandy.
I wanted to send an invoice to the Windows IT Pro folks for an article I had edited… but I couldn’t because the invoicing service I use was down. Ooops.
Over the last two days, I’ve gotten outage notifications from several of the services I depend on, including Trello and Harvest. As I write this on Tuesday, Harvest is back up, but Trello isn’t (nor is FogBugz, which is one of the candidates I’m considering for a hosted bug-tracking service). These outages are not unexpected; the NHC gave us all plenty of advance warning of Sandy’s likely impact. However, I was a little surprised to see how many services actually run on data centers in metro NYC. I have an intuition, but no proof, that the majority of these services are offered by small- to medium-scale companies that cannot yet afford their own dedicated data centers, which is to be expected. I predict that some of the services affected by this outage will move to relocate their services to another area, but some won’t; after all, no location is completely disaster-proof, and there are certainly benefits to having the services you offer hosted “near” your physical location.
The interesting issue is not that these services had failures; that’s to be expected. It is that as cloud service consumers, we now have to be aware of physical location in a way that “the cloud” is supposed to eliminate. File this under “cloud-related promises that turned out not to be completely true.”
Microsoft’s services, and Google’s, and Facebook’s, and Apple’s, and so on are all essentially location-independent. A metro-level failure caused by something like a hurricane or a major earthquake is a problem, but not necessarily one that end customers have to concern themselves with; there are always other data centers that can accommodate the load of the downed sites. In fact, this ability to provide continuity of service is one of the key drivers behind the architecture of Exchange 2010, and now Exchange 2013 extends continuity by simplifying the way load balancing works, thus making it easier to build larger stretched (“stretchier”?) sites.
Not that that helps Harvest or Trello users, of course. So along with the tired-but-still-important advice to ensure that your location isn’t cut off from the cloud by single points of connectivity failure, let me add a recommendation that you periodically survey the service providers you depend on so that you know where their services are hosted and can make arrangements accordingly in case of disaster.
Filed under General Tech Stuff, UC&C
Postel’s Law, Exchange ActiveSync, and iOS 6
Over the last week the Exchange community has learned a bit more about problems with Apple’s Exchange ActiveSync implementation in iOS 6; Microsoft has released a KB article outlining the problem and suggesting some workarounds, and Tony Redmond this morning pointed to a TUAW article that I hadn’t previously seen which asserts that the hijacking problem is a known issue with previous versions of iOS.
Tony’s article is titled “The emerging need for more supervision over ActiveSync implementations.” It’s certainly hard to disagree with that basic premise. Just over 18 months ago, Microsoft launched an Exchange ActiveSync logo certification program with the goal of inducing third parties who sell EAS-compatible devices or software to verify that they properly implement the client side of EAS. A quick check of this page maintained by Microsoft’s legal department shows just over four dozen EAS licensees, but only 3 vendors are listed on the EAS logo page itself. There are several possible explanations, ranging from lack of vendor interest in getting certified to a Microsoft failure to update the contents of the page.
Whatever the reason, I think Tony is right that Microsoft needs to be more proactive in requiring their EAS licensees to perform more robust testing on their clients.
Furthermore, I’m starting to think that the certification and testing program isn’t sufficient in and of itself, which brings me to Postel’s Law.
Some years ago, I worked for a company that made e-mail encryption software. This was during a time when even basic SMTP interoperability between different vendors’ systems was not assured– the Electronic Mail Association had biannual “plugfests” where vendors such as Lotus, Microsoft, and Netscape got together to ensure that their products could exchange SMTP mail properly. Whenever we ran into an interop problem, my boss would cite Postel’s Law:
Be conservative in what you do, be liberal in what you accept from others.
It seems pretty clear that Apple’s iOS EAS implementation has bugs– long-standing ones, if the TUAW article is right– and that Apple has a responsibility to fix them. I am coming to the opinion, though, that the server-side EAS implementation is too lenient about what it accepts. For years Exchange administrators had to suffer through a dance that went something like this:
- A new version of Outlook would ship with a bug that would occasionally corrupt calendar or message items in some interesting way.
- The corrupted items would cause the client to crash; in more severe cases, they could also crash the store process or cause backups, mailbox exports, etc. to fail.
- The Exchange team would release a hotfix to keep that particular flavor of badly formed item from causing such a problem.
- The Outlook team would release a hotfix that would keep that version of Outlook from emitting that particular flavor of corruption.
- In the next release of Exchange, the team would add business logic to reject items with the specific flaws generated by Outlook.
- GOTO 1
Over time, the Exchange business logic got better, as did Outlook’s track record of not creating bad items in the first place. This approach has served Exchange administrators and users pretty well, and it’s clear that the lessons learned from this painful process have been applied in Exchange Web Services. For example, EWS will reject attempts to create calendar items with end dates that come before start dates– something that Outlook used to occasionally do out of sheer perversity.
However, it looks as though, at least in this specific case, EAS doesn’t have business logic in place to catch the modifications that lead to the hijacking behavior. That’s something that Microsoft can fix in three steps.
- First, they can update the EAS spec so that it clearly defines which fields of each data item are to be considered read-only. This gives implementers a fair shot to understand where they may need to change their clients.
- Second, they can update Exchange itself so that it rejects client requests that violate the updated spec.
- Third, they can vigorously “encourage” their major ISV partners to test more aggressively against the updated spec. I have to wonder, for example, how much, if any, testing Apple has done against Exchange 2013…
I’ve been putting the blame on Apple for this problem, and while I don’t think that doing so is unfair or inaccurate, I also believe that the Exchange team can do a better job on the server side of blocking bad client requests, and I hope they’re madly planning how to do so in Exchange 2013 SP1.
Filed under UC&C
Thursday trivia #77
- The boys and I are headed for New Orleans this weekend to see my mother and, not incidentally, to hit the Voodoo Music Festival. Of the bands there, I am most excited about seeing Metallica and Skrillex, but there are a few other gems; hopefully we’ll make it there in time for Thomas Dolby on Friday.
- The law surrounding workplace privacy in California is really, really interesting.
- I’m really intrigued by two new devices: the iPad mini, because it’s the perfect size for use in the cockpit; and the Microsoft Surface, because it looks like a better device for some of the most common tasks I do on the road. I’m not quite ready to order either of them just yet, though…
- Candy corn on the cob. What will they think of next?
- So far season 3 of The Walking Dead is excellent. I am actually enjoying it more than season 2 because I’m watching it in HD on my AppleTV instead of in crap-o-vision from AT&T’s Uverse, which had terrible picture quality on AMC.
Bonus: if you like airplanes (and, really, who doesn’t?) then this video of Endeavour flying over southern California is priceless. Watch it in high-quality and full screen for maximum enjoyment.
Filed under California, General Stuff, Musings
More on bugs in iOS6 Exchange ActiveSync
As I hoped they would (but couldn’t mention in my previous post), Microsoft has weighed in with a KB article on the iOS 6 “hijacked meeting” bug. The article ID is 2768774, and it makes a couple of cogent points: first, that Microsoft is aware of, and is actively investigating, the bug. Second, that “Microsoft cannot mitigate this issue”; they recommend contacting Apple. The interesting part to me was the section on workarounds. Microsoft’s suggestions include:
- telling users not to make calendar changes using the iOS app
- recommending that users not update to iOS6 (as if! iOS device users are legendarily quick to update to new versions)
- blocking iOS 6 devices using Exchange ActiveSync allow/block/quarantine
- blocking users who have delegates, or who are granted delegate access, from using EAS
- using POP/IMAP instead of EAS (this made me laugh out loud– really!)
I have been testing Savvy Software’s Agenda app recently and like it quite a bit. However, it, like almost all the other calendar apps of which I’m aware, it uses the underlying iOS calendar data store and sync mechanism, so I’d expect it to fall victim to the same bug. NitroDesk has ported its Touchdown app to iOS (though its App Store reviews are pretty poor), and Emtrace has the MoxierMail EAS client (which I still need to review.) So pick your poison: none of Microsoft’s suggested workarounds are great, but their hands are tied. It’s pretty clear this is an Apple problem and it will be incumbent on Apple to fix it… which I am sure they will, eventually.
Filed under UC&C
Air traffic control call signs
I am a huge fan of LiveATC.net. I often listen to the San Jose airport control tower and/or NORCAL Approach as background noise at home, in the office, or while driving; it is always interesting and often educational. One of the most interesting things I’ve heard is the variety of callsigns for different aircraft and operators. Some of these are pretty prosaic– if you hear “UPS 9336 Heavy” or “Southwest 229” that tells you everything you need to know. There are some others that are more colorful, though:
- “Traffic Watch” is a popular call during rush hour.
- Stanford (“Stanford One”) and several other medical helicopter operators are unpredictably active; you never know when they’ll pop up.
- There’s at least one Boeing Business Jet operating out of SJC with the call sign “Boeing 1 Tango Sierra”; I haven’t taken the time to figure out whose it is, but I’m betting Google.
- “Redstripe” is the call sign for JetSuite, a private fractional-ownership jet company.
- I’m not sure who owns the “Starbase” call sign but it sounds cool on the radio. The only references I could find to it were here and here, and they’re inconclusive. (Looks like the FAA thinks the second one is dispositive.)
- “Dotcom” is an umbrella call sign offered by FltPlan.com; you can sign up for their service and then use one of their calls (e.g. “Dotcom 521”) instead of your aircraft registration number. This is useful to keep your competitors (or other interested parties) from performing physical traffic analysis on your airplanes.
There’s a pretty good list of airline callsigns that covers many international airlines, and it looks like the FAA’s official list is here (for some reason it doesn’t seem to be well indexed in Google). Other fun callsigns on the FAA list: Sputter, Jigsaw, Flapjack, Raptor, and Argonaut. Maybe I should print out a copy and start checking off the ones that I hear!
Filed under aviation
Thursday trivia #76
A special search-query edition of Thursday Trivia! Here are some of the search terms people have used to get to my blog over the last couple of months:
- how is reading used if you’re a marine: probably not often enough.
- fried fish harmful: for the fish, yes, it certainly is.
- what about airwork: as for me, I highly recommend it.
- s tripit pro worth it: yes, 100%. I also just signed up for CLEAR (thanks to a 4-month trial offer from Living Social for $18) and will report back on how well it works.
- stupid allergy warnings: now you’re talking; I am definitely allergic to stupid too and sometimes I wish there were warnings, like the pollen forecasts that the Weather Channel does.
- everyday carry pouch: hello, Mr. Kangaroo.
The top five search terms that have brought people here since I moved to WordPress: “conversation action settings”, “paul robichaux”, “autodiscover.xml”, “outlook auto discover”, and “the last psychiatrist.” Guess I know what I should be writing about more.
Tomorrow’s post will be titled “how Paul Robichaux used autodiscover.xml to find the last psychiatrist’s conversation action settings folder.”
Filed under General Stuff, Musings
iOS 6 and Exchange ActiveSync misbehavior
Brace yourself for a surprise: there’s at least one major bug in Apple’s Exchange ActiveSync client in iOS 6.
cue shocked silence…
This is not surprising, of course; EAS is a fairly complex protocol and Apple has displayed a somewhat cavalier attitude towards verifying that their EAS clients behave properly. If you don’t believe me, all you have to do is look at this list of known EAS issues with third-party devices and see how many of them involve iOS.
Anyway, the latest widely reported issue is that meetings sometimes appear to be hijacked– Alice will send out a meeting invitation to Bob and Carole, but somehow Carole will end up as the meeting organizer, thus gaining the ability to cancel or change meetings.
The hijacking bug isn’t the only one; users have reported a few other iOS 6 EAS issues, including its apparent failure to handle the case where the user’s primary SMTP address is different from the user name (e.g. an SMTP address of paul@robichaux.net coupled with a UPN of paul.robichaux@robichaux.net, for example), but these other issues all have easy workarounds; meeting hijacking is the most pestiferous.
The usual pattern for these bugs is fairly predictable:
- Apple (or another EAS licensee) releases an update.
- People start complaining in various fora that some EAS-related functionality is broken. However, these reports are only rarely made directly to either Microsoft or the vendor.
- A critical mass of reports accumulates and begins to draw attention. This is often accelerated by the opening of support cases with either Microsoft or the ISV.
- The source of the problem is identified, a resolution is developed, and everything is fixed.
- GOTO 1
Now, stop laughing. That really is what usually happens. Note that Microsoft’s hands are somewhat tied during this process. Until they get feedback from customers that something is broken, they can’t very well investigate it. I imagine that it is very frustrating for the EAS team to see people blaming Exchange for what end up being bugs in the EAS client implementation. But I digress.
Tony points out a few nuances of how the process works, including suggestions for figuring out which devices are actually in use. (Note that one improvement in iOS 6 is that it reports a value for the DeviceOS property returned by Get-ActiveSyncDeviceStatistics; older versions just left that field blank.) Leaving that aside, though, it’s interesting to consider what’s known about the calendar hijacking bug. The best explanation I’ve seen, ironically, comes from the Z-Push development team. (Z-Push, you may recall, is an open-source EAS implementation that has nothing to do whatsoever with Exchange.) However, they are apparently first to market with a public explanation of the problem with iOS 6 that causes meeting hijacking. I won’t repeat it here; it’s worth reading the original. The root of the problem appears to be that iOS 6 emits meetings with zero attendees, and that Exchange accepts these as valid. I’m not sure whether Exchange’s acceptance is a desired behavior or not but I’m pretty sure that the device should never be emitting a zero-attendee meeting. It’s possible that there are cases where this is not true, which is why the Z-Push folks are holding their patch in QA for now instead of pushing it into the main tree of their product.
The tricky issue here, of course, is how to get the problem fixed for those of us who aren’t using Z-Push. Microsoft could conceivably make a change to Exchange’s business logic for calendar items, preventing ill-formed meeting items from being propagated. Apple could likewise fix their client so that it doesn’t send out ill-formed items in the first place. Both sides have an interest in providing a smooth EAS experience for iOS users, but each side has a different set of engineering and delivery constraints that make the process of actually getting the fix out to customers a challenge.
Microsoft hasn’t publicly said much about this bug, other than that it is being investigated. (And Apple, AFAIK, has said absolutely nothing about it, which is regrettably typical.) Your best bet is to keep an eye on KB 2563324 for updates so you’ll know when Microsoft believes they have a solid understanding of the problem and the best way to fix it.
Meanwhile, the Z-Push team claims that turning off the Exchange calendar attendant feature would eliminate the problem, at the cost of some useful functionality. The iOS 6 bug is rare enough in most environments that I’d advise living with it rather than giving up the attendant functionality, but that’s a choice you’ll have to make based on your users and their needs.
I wonder whether Emtrace’s MoxierMail client has this problem? I’ve got an evaluation copy but haven’t been able to evaluate it yet; might be time to move that up a couple of notches on the priority scale….
Filed under UC&C
Thursday trivia #75
- There are so many reasons to love Pat Conroy. Here’s the latest: this pungent letter to a school board that wanted to ban two of his books.
- Absolutely fascinating legal question: if I fly a drone over your house, is it trespassing? There’s no good answer to this yet, but I bet we will see case law on this before Tom graduates from high school– and it wouldn’t surprise me if the first cases were heard in California. If I were a paparazzo, I’d totally want to get some drones overhead celebrity homes.
- Microsoft has long been pointing out a weakness in Google Apps: you never know when Google will change things. They don’t share their feature roadmap, so what you get today may not be what you get tomorrow. Folks who use the OpenOffice document formats recently (re)learned that lesson when Google abruptly removed support for those file formats.
- Speaking of web services: I am stoked about the Exchange 2013 version of Outlook Web App. Check out these screenshots and you’ll see why.
- Grapes are diamagnetic, meaning you can repel a grape WITH A MAGNET. Science, people.
- I’m more than a little jealous of Jeff Guillet’s supercar tour.
- Closing in on my checkride– I need 1 more night landing, 1.6 hours of hood time, and then it’s checkride city!
Filed under General Stuff
Please stay home, Mr. President
Our dear leader, President Obama, is coming to the Bay Area on Monday. (Why he’s coming is unclear to me; it’s not as though Romney has any chance of winning California, so I presume it’s so Obama can raise money from his legions of wealthy fans out here.)
Anyway, the point of this post is to point out what happens when he’s here. The picture below will help illustrate my complaint.
See those red rings? During his visit, most private aircraft are essentially not allowed to fly within those rings; flight training (and cropdusting, and animal control, and a long list of other operations) are specifically prohibited, and there are other restrictions. Commercial passenger and cargo flights are exempt, luckily (otherwise AA passengers departing SFO Monday would be in even more trouble, hey ho!)
The largest ring is a 35-nautical-mile radius centered around the San Francisco (SFO) VOR. That takes in the Palo Alto, San Jose, Oakland, and San Carlos airports. So from 1pm Monday until 10am Tuesday, the dozens of instructors and hundreds of students training at those airports are grounded. That means an immediate loss of several thousand dollars per instructor– and the losses are greater for flight schools themselves.
More to the point, this is just a further delay in my pursuit of my license, as I can’t fly during that time unless I am actively, y’know, going somewhere.
Oh, and the best part: the geographic and time restrictions of this temporary flight restriction can change at any time. So I could, in theory, inadvertently and innocently violate it if it changes while I am in flight. This is rare and unlikely, thank goodness.
So thank you, Mr. President. I’m glad you’re doing your part to help the economy. See also previous helpful contributions here and here. (substitute “Bush”, “Romney,” or the name of your favorite post-9/11 president above if it makes you feel better, although President Obama has been a worse offender in this respect than was President Bush.)
Help retrain veterans for IT jobs
Acuitus is working on a pilot project with the US Department of Veterans’ Affairs: we’re running an IT training school for unemployed veterans, using our proven Digital Tutor system to take them from little-to-no computer knowledge to being able to troubleshoot complex problems on Windows and Cisco IOS.
Our goal is to be able to train these vets so they can move right into entry-level IT and IT support positions. They will not be Exchange architects or CCIEs, but they will have very strong Windows and network troubleshooting skills that we think will make them immediately hirable.
If you work for a company with more than 750 employees, you can help.
The challenging part is figuring out exactly what to teach. That’s where you can help. I’ve got a survey that asks about your IT environment: what equipment and products you use and what skills you would expect an entry-level technician to have. We’re using this to calibrate what we teach to make sure our graduates have the right skills to prepare them for jobs in the commercial world. Your responses won’t be shared publicly.
If you are willing to help, please e-mail me (paulr at acuitus dot com) to get a copy of the survey.
Filed under General Stuff, UC&C
Thursday trivia #74
- On my last trip to Huntsville, my American flight from Dallas to Huntsville arrived more than two hours late. Consequently, when I booked my flights for October, they’re all on Delta. This letter from a pilot to former AA CEO Bob Crandall, and his reply, are well worth reading.
- Replace Alice and Bob? Never! You can have my standard cryptographic personas when you pry them from my DPAPI storage.
- I have a lot more I want to say about MEC, and I will, but for now the BLUF: fantastic show, great content, and a wonderful opportunity to reconnect with my peers. I saw probably a dozen people that I hadn’t seen in five or ten years, and met maybe another dozen with whom I’ve collaborated and corresponded without ever meeting face to face. I’m already eager to sign up for the next one.
- General James Mattis, a Marine’s Marine.
- The Illustrated Guide to Criminal Law. Sounds like a fun read.
Filed under General Stuff, Musings
