Finding the BCC field…

I’m not a big user of the BCC field. This morning, however, is one of those rare occassions when I’m trying to use it, and I can’t find the damn thing!

I’m looking somewhat incredulously at my screen right now, and I’ve gone to the oh-so-helpful Microsoft Help, and I still can’t find it! I’m torn trying to figure out if this is my Mother’s non-techie genes interfering with my work today or my Dad’s intermittent memory gene. Either way, I’m stuck!

Here are the instructions from Microsoft for enabling the BCC field:

  1. In a message, click To .
  2. In the Type name or select from list box, type the name or click Advanced, and then click Find.
  3. In the Name list, click the name.
  4. Under Message Recipients, click Bcc.
  5. Click OK.

I got through step 3, but there is no “Message Recipients” anywhere on the damn screen!?!@#$#! Right click reveals nothing useful. Clicking the little bubble by the name reveals nothing. Nothing in the menus. Just nothing.

God damn it. Can’t do a BCC? What do I have to go back to elm? pine? What happened to “View BCC” on the menu?


Answer:

OK – well, with the help of a colleague, we found the problem. On my machine, clicking “To” (as per the instructions) doesn’t open the “Select Names” dialog box. You have to *double click*. Minor distinction. But apparently important.

To all those readers (both of you) out there that thought I was technically inclined, know now that I am clearly not. Maybe my technical frustration today can bring a little smile to your morning.

I think I’ll go write an Outlook AddIn now which fixes the BCC problem.

Whine about GMail again!

You know, I mostly whine about GMail because I have a good friend that works on that product, and I hope when he reads this he jumps to fixing it. Despite all its glitches, I still use it because its got built-in search that just works better. Also, the no-foldering philosophy is one I fell into when building Lookout, and GMail is the only system I know which does this too.

My previous posts on GMail bugs can be found here, or here, or here.

And today, on multiple mail sends, I’m getting this error, repeatedly, when trying to send email, “Oops… the system was unable to perform your operation. Please try again in a few seconds.”

I’ve waited more than a few seconds. At least fix the error message!!!

Fix for Windows – Eliminate the Registry

The Windows Registry has been a computer administrator’s nemesis since about the time it was invented. It started with good intentions, but turned into a cryptic, haphazard mess. Its like a kitchen sink with a broken garbage disposal.

One of my biggest gripes about Windows is that you can’t re-install the OS without replacing all the applications. Have you ever been reluctant to reinstall because you knew that as soon as you do all your applications will be broken and need to be reinstalled too? Why is this? Shouldn’t you be able to reinstall the OS without breaking the apps? Unfortunately, the registry is owned by the OS, and because of this coupling, you can’t.

Its fixable – search

The good news is that this is fixable. The registry just needs to be rewritten. Today, the “registry” is a centralized index of attributes from every app installed on the system. What if, instead, the registry was a set of small files that resided on disk, each file contained a small set of attributes that are related somehow, and we maintained a search index to find things through all of these files automatically. Each application would have it’s own “.reg” file(s), which could reside with the application. If you move the application to another location on disk, its registry file would move with it. If you delete an application, its registry file would be deleted with it. Make sense? Now, we’d maintain a central index which would seek out these special filesystem files and index the data. You could still run a virtual “regedit” application, and it would look identical to how it looks today. Its just that instead of a central storage mechanism, it would use a distributed storage mechanism.

Benefits:
1) Containment of registry settings. Today, if you look at the registry, you might be able to guess where a given registry setting came from, but you can never be sure who really owns it, if it is still relevant, or if there is harm in deleting it. With this new model, where .reg files reside side-by-side with the application, its inherently obvious where the setting came from.

2) Ability to migrate the registry with the application. Today, if you want to move an app from drive C to drive D, you probably have to reinstall. There are other factors too, but one obstacle is the fact that the registry settings have to change, and you have no idea where they are. Adding a few variable substitutions to the registry files for things like (%MYPATH%), and you can now move apps and their registry settings by just doing a filesystem copy. You can now actually backup your apps.

3) Simpler Security. Security of the registry would now be handled by filesystem protections. IT folks could set the registry settings that they want, and use filesystem protections to make sure they can’t be modified.

4) Conflict Resolution. What happens today when application A wants a registry setting to one value and application B wants another? Well, you pick one and lose the other. In the new model, you still have two values, and you’ll need a rule to determine which takes “precidence”. But, if you open up regedit, it will be able to tell you not only which items have conflicts, but where the conflicts are, and what the conflicting values are! Now, you’ll be able to pick the right setting with knowledge about why there was a conflict, rather than having to debug an obscure problem that you didn’t even know about.

What do you think?

Example:

    /Documents and Settings/

      UserBob

        Application Settings

          Microsoft

            Word

              word-usersettings.reg — word might chose to store some registry settings here so that they can be written by a non-admin user

          Intuit

            Quicken

              quicken.reg — quicken might choose to store registry settings here

      /Program Files/

        /Quicken/

          [application files go here]
          quicken.reg — This file contains all the quicken registry settings

        /Microsoft Office

          [application files go here]
          office.reg — This file contains all the office registry settings

Dynamic Bridge Tolls

On my way into work today, I was thinking about bridge tolls. There has been talk of raising the tolls on various Bay Area bridges to $4 or $5 or even $6! Yikes!

Now that we have FastTrack, it seems that there may be more creative solutions we can come up with. For instance, what if the toll is variable? Those crossing at 5am get to cross for $0.50. At 6am, its $1.5, at 7am it jumps to $3, at 8am its $6, at 9am it drops to $3, etc etc?

I found a similar proposal for the New York area from the Tri-State Transportation Campaign which had some good data in it here. They divided their plan into “off peak” and “on peak”, at $4 and $6 respectively.

Using excel, a little math, and a bit of arrogance, I am coming up with this model. My goals are to increase revenue, but also increase vehicles-per-hour over the bridge.

1) If you don’t use fasttrack its $7.50. This is because you are costing us a lot of money and slowing everyone down. Get fasttrack.

2) Peak hours (7am to 9am): $7

3) Off-Peak hours: $2

Now this is a no-comprimise plan with teeth! A commuter can save $25 per week by shifting to off-peak driving hours.

Using the same percentages for vehicles per hour as the TSTC used in New York, my model would produce a 5.7% increase in revenues over the current, static $3 plan. At the same time, it puts such a heavy incentive to get drivers onto FastTrack and to not use peak hours, I think we’d see a significant decrease in overall bridge wait times.

But what do I know….

Really Extreme

But what if we wanted to get really radical, and have a completely variable price that adjusts in real time?

Google is an interesting example of a company that adjusts their prices in real time. They deal with a huge volume of “ads”, and they are constantly figuring out which ad is best optimized for their business. This is done in real time.

What if all California bridges were linked electronically. As tolls are collected (either digitally via FastTrack or via toll-takers), the central system adds up the money. At the same time, the central system knows how many vehicles per hour are flowing through any bridge.

Each year, the governor types in a number for how much revenue per day he wants to get from the Bridge system. Then, the bridge system uses its historical models, current traffic flow rates, and the target revenues to calculate how much it should be charging drivers to cross the bridge at that instant.

Imagine the case where a bridge is extremely congested. The bridge system would automatically start raising the toll – in REAL TIME. This would have the effect of also lowering the tolls on the other non-trafficked bridges also in REAL TIME. We could set limits on the toll so that it never exceeded say, $15. But when it gets congested, commuters need to find another way to get home.

The advantage of this system would be that bridge tolls would be almost free when crossing if there was no traffic. But, when congestion occurs, the price would get higher and higher. Its actually a very fair way to deal with pricing.

Anyway, this idea is wild and crazy. The state of California isn’t very capable for creating real-time, dynamic bridge crossing toll algorithms. And we can get “close enough” with something simpler and less politically damaging anyway…

Operational Uptime

We’ve all heard companies that claim service reliability of “99.9%” or “99.99%” or “5 nines” (meaning 99.999%). But what does that mean?

The fact is that 99.999% uptime is really hard to achieve. On a monthly basis, 99.999% uptime means that your service is “down” for less than 26 seconds. Now, many services skate around this issue with fuzzy definitions of “down”. They might say that “downtime is defined as a majority of mailboxes being unavailable”. So a single mailbox being down might not be considered “downtime”. But as customers, if its your mailbox, that doesn’t sound quite right, does it? We usually have simpler definitions.

Anyway, GMail this morning has been down for 3 hours (at least) on my mailbox. Assuming they operate perfectly for the remainder of the month, that means they’ve dropped to only 99.58% availability this month. And, if they remain up with no downtime for the rest of the year, they’ve already missed the 5-nines, and are struggling at 99.96%! Given the outages I’ve seen, I think they’ve been down for at least 12 hours on my mailbox, so I think they are operating under the 99% level.

Oh well, I shouldn’t beat up on them too much. It is only beta, after all, right? But geez- with the $4B in the bank from their second IPO, I’d think they could ad least get to “two nines”. What about my god-given right to read email now?

Microsoft vs Google in Court

Lawyers spar at Microsoft-Google hearing

You know, this is such a waste of time. How many millions do we have to waste on this stuff? This is a lose-lose situation for Microsoft and Google. Both sides should figure out how to settle this immediately. Either Google should say they just don’t need this guy (because they don’t), or Microsoft should they don’t need this guy (because they don’t) and that they don’t care if he goes to Google (because it doesn’t matter).

That’s probably the best solution – both sides agree to never hire him again.

But the lawyers are advising both sides to take this to court. They probably advise that this is somehow precident setting for future employee hires. Yeah right. The real reason is because that’s how lawyers make money.

GMail down again

I’m really starting to question my use of gmail. It seems pretty unreliable – I can’t tell you how many times it reports, “Gmail is temporarily unavailable. Cross your fingers and try again in a few minutes. We’re sorry for the inconvenience.”

The humor was funny once, when this was an isolated event. But I want to read my email now, and I really don’t have time for this incompetence. Its been down for at least 30 mins now [6:30 to 7am]. Yahoo! Please take me back!

Update – its now 10am, and the service is still down. 3 hours of downtime on a Weds morning. Not good!