GOLF; Why do I play it? After all it is the most frustrating, inconsistent game I have ever played. But if you think about it; that is a good thing. This frustration brings a natural desire to get better, and the inconsistency tells me to just have fun. I get into an inconsistent state once I start to think of all of the things I should and shouldn't do throughout my swing. Whereas, if I get up there and just hit the ball; the consistency tends to come naturally. All it takes is one bad shot and my head wants to go back into an inconsistent state then overriding my bodies muscle memory. Once you are able to master the ability to have fun every swing you will see a steady decrease in scores. Save your inconsistent thoughts for the range; when you find a pattern that works then it is time to work on muscle memory that will carry over to course play. The only difference is, now you have to aim. No matter what, I know I can always get better; so I never get bored with it. But the biggest reason I play golf is; it is around 4 hours of my time that I get to enjoy the nicest views, not think about anything but my next shot, spend time with friends and enjoy the weather.

Picnic at Sunset Sarasota Bay

I love it when my wife sends me a text while I am working. "Sunset picnic on the bay?" She so knows how to make my day. We had cucumber salad, spinach / feta Stromboli, and spring rolls. Oh I cannot forget the smoked fish dip. I attempted to fish, but the view distracted me.

SOLID Design Principles

Single responsibility principle

A class should have only a single responsibility, that is, only changes to one part of the software's specification should be able to affect the specification of the class.

Open–closed principle

"Software entities ... should be open for extension, but closed for modification."

Liskov substitution principle

"Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program." See also design by contract.

Interface segregation principle

"Many client-specific interfaces are better than one general-purpose interface."

Dependency inversion principle

One should "depend upon abstractions, [not] concretions."