Skip to main content

Y2K Part 2

In less than a day, the 3-week early DST change in the US will occur. Airplanes will fall from the sky, your bank account will be reduced to nothing, ATMs will run out of cash, nuclear missiles will launch and your Tivo will be hurled into a wolrd of recording the show after the one you wanted it to.

Actually, you'll probably just lose an hour of sleep tomorrow morning. Unless you have kids. Then you will lose two.

The media has really hyped this problem up, in a style reminiscient to the Y2K bug. Sure, there may be a few missed appointments on Monday, people may have some issues with Outlook (I got 6 invites from a client for the same meeting last week.) But by and large, the impact of this change will be less than that of realizing it's 8:00, not 7:00 and still light out.

Verizon Wirelss is doing all they can to get their customers ready. They sent a text message to my phone the other day, which conveniently had a link embedded in it to its DST Resource Page. What they failed to think through is that the link led to a regular-sized web page, complete with HTML that doesn't render well on the device which they sent it to. Not only did the page take forever to load, but once it did, it was impossible to navigate the Javascript-driven menus once it did. Thanks for that!

All was not lost. Just this morning, I received an e-mail informing me of the same imminent demise that the early DST change will bring. My favorite quote from that e-mail:
"The Verizon Wireless network will seamlessly support the change to DST. While most customers’ devices will experience no impact, customers with BlackBerry devices and most PDAs/smartphones running Palm OS or Windows Mobile will be required to update or patch their devices."

Really? So the so-called "Smartphones" - which are all considerably more expensive, have more features, and overall are much harder to use then their "dumber" counterparts - are not smart enough to realize the the network time has changed? Wow.

What Verizon Wireless recommends is to install the latest DST Patches from Microsoft. Sure, that makes, sense, let me pop on over and read about the potential impact of such a patch:
"All Windows Mobile powered device users affected by the time change should give extra attention to meetings and appointments scheduled between March 11 and April 1, 2007, and between October 28 and November 4, 2007. View any appointments that fall into these date ranges as suspect until you communicate with all meeting invitees to make sure that the item shows up correctly on everyone's calendar."

So not only do we have to worry about this problem this week, but once again in the fall? And the best they can do is recommend that I treat any appointment that I have in the next month as "suspect"? Should I call the authorities? Will the terrorism alert level change if I don't? Hmmm...

And my personal favorite piece of advise throws us all the way back to 1992, the last time that I bought filler paper for my Franklin Planner:
"Prior to applying the DST files, print out your weekly calendars for the affected time periods so that you can keep track of which meetings were scheduled before and after you run the tool."

Time to head out to Staples!


Comments

Popular posts from this blog

Whose Deck is it Anyways?

This year at KScope, we're going to try something new.  And fun.  And funny to watch - we hope.  It's called "Whose Deck is it Anyways?", and will occur on Sunday at 8:30pm.  It's only 30 minutes, but it will likely be the best 30 minutes of the conference.  Or at least the most embarrassing.

Here's what we're going to do: the will be four 5-minute presentations - one on each of the following: BI, EPM, Database & APEX.

Sound interesting?  Probably not.  We get that, too.  So here's what we did.

Each 5-minute session will be presented by a non-expert.  For example, it's highly likely that I'll be presenting on BI or EPM.

To make it even better, each slide deck will be prepared by the corresponding expert.  So again, it's highly likely that my slide deck's creator will be either Stewart Bryson or Edward Roske.  If nothing else, this session will be a crash course in how not to make cohesive, easy to read slides.

Interested now?  Ya,…

Spaced Out

A while back, I wrote about how to give the Universal Theme a face lift.  If you follow the steps in that post, the base font for an APEX application with the Universal Theme can easily be changed.

While that's all well and good, sometimes you only want to change the font for a report, not the entire page.  One of the applications that I'm building contains a number of IRs based mostly on log data.  Thus, having that data in a monospaced font would make it a whole lot easier to read.

You can search Google Fonts for monospaced fonts by selecting only that option on the right-side menubar.  You can also opt for the standard yet kinda boring Courier and achieve the same thing.

To implement this in your application, follow the steps in my other post, but stop shy of the final step.  Instead of pasting in the text that I specify, paste in the following to the Custom CSS field in Theme Roller, using the name of the font you selected for the font-family:

.a-IRR-table tr td { font-fam…

#fakecode

Unless you've managed to somehow filter out everything about US politics over the last few months (and if you have, please let me know your secret), then you've likely heard about "fake news".  From a high level, my basic understanding of "fake news" is that it refers to stories or websites that are fabricated to advance the political beliefs and/or ideologies of one site or the other.  Your definition may differ.

So what is fake code?  That, I can at least try to explain in a bit more detail.

The other day, I saw this image posted on Kris Rice's twitter feed:



I thought it was a joke, but it's actually a real book. That made me laugh.  Then cry.  Then I read the book, mainly since it's only 4 pages.  Believe it or not,  there's actually some really good content packed in there.  Let me summarize:

If you choose to copy code from Stack Overflow, the OTN forum, or anywhere, really, there's a few things to keep in mind:


Who owns the code.  It…