This afternoon, this article about being a likable speaker crossed my inbox. It’s a quick and easy read, and I thought people who do public speaking or present regularly (as I do for SQL Saturday) would find this of interest. I thought it was worth a share.
I will be speaking; I will be giving my presentation on documentation. There are also a number of other presentations that people might find of interest.
When I attended SQL Saturday in New York City a couple of months ago, I sat in on Lisa Margerum’s session on networking. It is an excellent session, and I recommend it highly.
A number of my friends are also presenting, including Greg Moore, Thomas Grohser, George Walters, John Miner, and Ed Pollack. They always give good presentations, and I recommend them highly. Check out the schedule for more details.
Hope to see you there!
This coming Saturday, June 3, I will be speaking at SQL Saturday #638, Philadelphia (okay, it’s actually in a town called Whitpain Township, not Philadelphia, but that’s what they call the event, so…)!
I will be giving the following two presentations:
- Tech Writing for Techies: A Primer — Documentation is one of the most critical, yet most blatantly ignored and disrespected tasks when it comes to technology. Businesses and technical professionals ignore documentation at their own risk. This session discusses what tech writing and documentation is about and why it’s critical for business. It also explores possible reasons for why it’s ignored, how documentation can be improved, and how “non-writers” can contribute to the process.
- Disaster Documents: The role of documentation in disaster recovery — I was an employee of a company that had an office in the World Trade Center on Sept. 11, 2001. Prior to that infamous date, I had written several departmental documents that ended up being critical to our recovery. In this presentation, I provide a narrative of what happened in the weeks following 9/11, and how documentation played a role in getting the organization back on its feet.
While other disaster recovery presentations talk about strategies, plans, and techniques, this presentation focuses on the documentation itself. We will discuss the documents we had and how they were used in our recovery. We will also discuss what documents we didn’t have, and how they could have made the process better.
Hope to see you there!
At SQL Saturday #615, I had the pleasure of sitting through a session by Eugene Meidinger titled “Drinking From the Firehose: a Guide to Keeping Up with Technology.” His presentation brought to mind my earlier ‘blog article about struggling to keep up with technology, and he also mentioned a few things that didn’t occur to me. I won’t rehash his presentation — I didn’t ask him for permission to use it, and I don’t want to step on his toes — but I do want to mention a few points he brought up. (I was actually hoping he would have an article on this topic to which I could link, but I wasn’t able to find one on his ‘blog.)
The first point he makes is that keeping up with technology is impossible. He points out that “keeping up is ill-defined.” What, exactly, does it mean to keep up with technology? It’s such a vague, gray area. He mentions that you are never “done,” and keeping up is more an emotional issue than a goal. He also mentions that the rate of change is accelerating. How can you keep pace with something that is always getting faster? It can’t be done.
Eugene talks about what he calls “the contradiction of learning.” To add value, we need to specialize, but to avoid being irrelevant, we need to generalize. Personally, I’ve based my career on being a jack-of-all-trades, but I’ve also discovered that employers are looking for experts in a single area. That is difficult in and of itself. If you specialize in an area, who is to say that it will be relevant down the line? When I was in college, COBOL was a big deal, and many employers were looking for people who were well-versed in COBOL. When was the last time you saw a job listing for a COBOL programmer? On the other hand, SQL has been around for quite some time, and there seems to be no shortage of SQL positions. So how do you know which technology should warrant your focus? It’s hard to predict.
I don’t want to delve too deeply into Eugene’s presentation; it’s his presentation, not mine, and I don’t want to take too much away from him. (His presentation slides are available at the link to his SQL Saturday presentation above, if you want to read more.) If you ever have an opportunity to catch his presentation, I encourage you to do so.
My 2017 SQL Saturday schedule is slowly taking shape! For those of you who are interested, here’s where I’ll be (so far)!
- May 6: #615, Baltimore: I am giving two presentations: “Tech Writing for Techies” and “Disaster Documents.”
- May 20: #588, New York City: Unfortunately, I was not selected to speak. 😦 But I’m going, anyway, as an attendee; I just won’t be presenting.
- June 3: #638, Philadelphia: I am giving two presentations — the same two I’m giving in Baltimore: “Tech Writing for Techies” and “Disaster Documents.”
- July 29: #622, Albany (my hometown SQL Saturday!): At this time, I have no idea whether or not I’m speaking. I submitted three presentations. However, I will be there, regardless of whether or not I’m selected to speak!
Come on out to a SQL Saturday near you! The events are free (although there is usually a nominal fee for lunch), there are lots of networking opportunities, and you might just learn something new!
And as an added bonus, you might even get to hear me speak! 😉
My next speaking engagement is set! On Saturday, May 6, I will be speaking at SQL Saturday #615 in Baltimore, MD. I will be giving not one, but two presentations that day: “Tech Writing for Techies: A Primer” and “Disaster Documents: The role of documentation in disaster recovery.”
Hope to see you there!
I’ll be speaking in Pittsburgh this Saturday, October 1. Hope to see you there!