Skip to main content

Pivotal Point in History

A few days from now, we will mark the 145th anniversary for one of the most pivotal points in the history of our country, the Battle of Gettysburg. Thought the battle technically occurred from July 1 through July 3, 1863, the actions that occurred for the past few days 145 years ago set things in motion that resulted in one of the bloodiest battle in the history of the United States. Each year we celebrate July 4 as our day of independence. However, most people do not know how critical the actions and sacrifices that 160,000 men made 145 years ago shaped who we are as a country. I encourage everyone to study our history. It serves as a guide in business and life. If you do not want to read the hundreds of books written about the Battle of Gettysburg and would like to get a pretty accurate account of the Battle of Gettysburg, I suggest you get the Gettysburg Movie on DVD. Warning it is a very long movie. The Extended LaserDisc Edition is even longer and it is great. Even better go and visit the Gettysburg battlefield. Note, if you want to avoid crowds do not go this time of year.

Coming soon more Lotus Notes Interface tricks.

Comments

Don McNally said…
My wife and I went to Gettysburg about 11 years ago and were pretty amazed (we also drove past Manassas and stumbled upon Antietam, which was cool too). I'd like to go back and see it now since the tower is gone. It is definitely worth the trip.
Andy Donaldson said…
North or South, it doesn't matter. Gettysburg is a place that you just can't label correctly and must be seen with your own eyes. To sit at the High Water Mark on Cemetery Ridge looking west to the Virginia Monument and think the number of men that moved across that field in one giant push. Hard to imagine.
I still feel the whole battle would have ended differently had Lee listened to Longstreet and had Jackson not been killed earlier. But that is an argument that will be debated for years to come.
Awesome blog post.
We are planning a trip to Gettysburg to see the reenactment on the 150th anniversary. Hopefully I can bring my dad and kids with me. It should be a great reenactment and definitely be crowded.
Dan Sickles said…
I've never been Gettysburg and I have both legs, but I do have an occasional problem with insubordination.

Popular posts from this blog

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a

The iPhora Journey - Part 4 - JSON is King - The How

  The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework The iPhora Journey - Part 4 - JSON is King - The Why The iPhora Journey - Part 4 - JSON is King - The How As we mentioned yesterday, in reimagining Domino, we wanted Domino to be a modern web application server, one that utilized a JSON-based NoSQL database and be more secure compared to other JSON-based NoSQL platforms. A Domino document existing within a Domino database is the foundational data record used in iPhora, just as it is with traditional Domino applications. But instead of just storing data into individual fields, we wanted to store and process the JSON in a Domino document.  However, text fields (AKA summary fields) in Domino documents are limited to only 64 KBytes, and that is a serious limitation. 64 KBytes of JSON data does not even touch what the real world typically transfers back and fo