So here we are. I didn't write because I was the expert in any one topic. I wrote because I wanted to learn more and because I wanted to share that with you. Frankly, I also needed you to fill the void between sitting in a hotel room after work and getting home to my family every week.

I mention this now, to be blunt. Someone out there next to you needs to hear this.

  1. Read outdated posts while considering the context in which I wrote them.
  2. Feel free to send errata in context.

I cleaned up purged my email mailing list recently and got a pretty good chuckle at an attempt to let me know that I failed to revise a post. All I can say is I am sorry that it didn't work out, whatever "it" was. I wish we could have chatted about it, but mostly, I hope you eventually figured out solutions to your issue(s).

Some of the posts on this site are not evergreen. The technology-specific ones are contextually correct examples from a point in time. They are things I wanted to share or happened to be learning about at the time. (Remember the date and technology-version specific context.) Unless I have marked an old post with date stamped updates/errata, you should always assume it may be out of date.

Tiny changes in syntax, major version releases, tooling modifications, entire packages disappearing overnight, and more are all things that could happen from the time I wrote something until now. If you run into problems that require updates or workarounds, please shoot me a suggestion or pull request. (You can find me on Twitter.)

In the meantime, Amazon just delivered my copy of "Sun Microsystems Core Java: Volume 1 Fundamentals," so I have some reading to catch up on.

Until next time friends,

Cheers-

Photo by Klaas on Unsplash
white and black type writer beside telephone on top of brown table