Skip to main content

Life on a Miami Beach: Day 5

This morning, we actually slept in.  I was the first one up and went across the street on a coffee run.  McDonalds coffee really isn't all that bad, and it is much better than the in room coffeemaker.

We took today as a relaxation day.  We went for a walk around the neighbourhood, picked up some postcards and went for a walk on the beach.

After a lunch of sandwiches, we put the Turtle down for a nap and I took the Toad to the beach.

An afternoon of watching a movie on the Disney channel, a trip to the grocery store for tomorrows lunch and some veggies and we called it a day.

A few observations:

People, especially men, should not wear thongs to the beach.  This is even more important if the thong wearer has a lot of body hair.

Although we now have credit cards with a chip in Canada, I have yet to come across a single credit card machine down here that uses the chip.

I was reminded today about the tide, both high, and low.  No wonder the water level at the beach seemed to fluctuate from day to day.

Yesterday was the first time I have ever heard a person referred to as a 'baby mama', not a girlfriend, partner, wife, etc.

In South Beach, on New Years Eve, you have to pay to reserve a table.  The fellow I spoke to paid $250 to reserve a table at a restaurant in South Beach.  Not even on the beach, or even facing the fireworks, or even a top end restaurant.  Just for a regular restaurant and having the honor of then paying for a meal.


Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X