This blog replaces the existing "Brave New Word" (without L), that I used to have on TypePad. This blog will be my way of "dogfooding" Sampa. If it is not working well, it will affect me as much as any customer of Sampa.
The topics will be the same: Technology, Web, Development, Products & Companies, Security, Startup, Usability and once in a while a rant of sorts.
Sampa is different from other products because it is fully RSS-enabled. This means that you can have feeds at any "level". So, if you are only interested in Brave Tech World, use this feed: http://marcelo.sampasite.com/brave-tech-world/feed.xml
On March 27, 1998 I started at Microsoft. At that time my Stock Option strike price was 21.95. I remember that because when I left the company in 2004, that was my first grant of Options that was about to expire.
The interesting thing to notice is that Microsoft is trading on the 22.5-22.9 range today (it did it last week as well). Can you imagine?
Here is some surreal data... If the stock reaches:
- 21.87 (9/30/02) it will be the 5 year low
- 21.68 (12/29/01) it will be the 6 year low
In other words... Tough days for Microsoft.
Now, I do wish the stock to go up, up, up. A lot of my friends work there and they will make an extra buck if the stock goes up.
I can't really tell when that happened, but 2 years ago you could go to https://google.com and get all your searches over HTTPS. Good for the paranoid about the government snooping on your ISP (hey, that is happening!).
Today I tried and they redirect to http://google.com (without the 's').
The only reason that I see for them doing that is to preserve CPU, since the SSL consumes between 10-20% more CPU than non-SSL responses.
On a different company, similar topic, on MSN Search (https://search.msn.com) you get the message that "this service is currently unavailable".
This is one of those moments that I think I'm the last person on Earth to know about it, but there is a very neat tool called SelfSSL that allows you to install a simple certificate on your IIS (on XP) for testing purpose.
I'm surprised at the number of sites that have plain stupid JavaScript bugs on them. How do I know about it? Well, I have script error notification enabled on both my browsers (IE and Firefox).
Ok, most users will never see that error and it will not bother them or prevent them from navigate on the site, but clearly, there is a bug on the site script and maybe some neat feature is not working because of that.
What I say is that if you ever do JavaScript development, turn on the errors notifications.
On IE, go to Tools -> Options -> Advanced and select "Display a notification about every script error".
On Firefox, install the WebDeveloper extension, and on it's option dialog, click on Miscellaneous, and check "Open the JavaScript console...".
This way, whenever you are developing your code, you'll be sure to see the syntax/runtime errors that you've been missing before. And, you'll get annoyed by other sites that have bug as well, so, do the world a favor and send a feedback to site with the error and ask them to fix it.
Subscribe to this Site
and get all your searches over HTTPS. Good for the paranoid about the government snooping on your ISP (hey, that is happening!).
September, 2007