An Early Morning sunrise at SQL Saturday 271
This weekend I attended and spoke at SQL Saturday #271 in Albuquerque, NM. This was my first time speaking outside my own events so it was a new experience for me. I spent some time in the speaker room during the morning getting my computer setup for the presentation later that day.
I started out with my presentation and slides and everything was going well. Very interactive group (I like questions throughout the session) and lots of good discussion. I only had about 60 minutes worth of content in a 75 minute session so I knew I had to get some good questions going. I started into my demo and was showing some of the key points and then started on my Import using SQOOP. It started up just fine and then just stopped on one step. Not only did it stop my whole computer froze. I thought for sure I was going to see a BSOD or it was just going to shut down. Luckily I was able to handle this and continue the presentation without it causing too much damage. I didn’t get to show the process I originally wanted to show but I was able to explain and go over with the audience all the pieces I still needed.
This got me thinking about some key things you need to do WHEN the demo goes bad. It is not a matter of IF but when. Sooner or later you will have it fail on you.
Be calm and cool!
When things go bad!
- Don’t Panic! Apologize for the issue and keep moving with the presentation work on the next step. Letting it throw off your focus or send you down a tangent will not end well.
- Fix it, if it is a quick fix then take a quick 2-3 minutes to resolve it. See next point about communicating if you are fixing something.
- Keep communicating. The last thing you want is a long silence in the presentation while you fight your demo issues. Ask more questions of the audience or find out how things have gone so far.
- Don’t apologize too much. I actually failed this one in my presentation. Apologizing over and over isn’t going to change anything. Apologize for the issue move forward and keep going.
Some ways to avoid the problem.
- Have a backup, this can be easy for some things and hard for others.
- The backup can be static content/hidden slides with images that you can show what the demo is supposed to be doing.
- Test and re-test your demo’s many times. Even if you have presented this 100 times testing the morning before is a good idea. ( I didn’t and look what happened to me)
These are just my simple suggestions and I would love to hear if you have additional suggestions as well.
Overall I received good marks on the presentation and my fellow speakers said I handled the issue well some suggested just removing that part of the demo from the presentation. This is something I’m considering but I’m also working on solutions to fix the problem so that I can avoid it in the future.
I hope future demos for you go well but in case they don’t keep these things in mind and it may make the pain a little less!
This is going to be a very busy next few months for me. Besides putting on some really cool and rocking events in the next few months I will also be speaking. Hopefully in several different states. I’m working on blog posts to go along with these presentations but for now here’s what I’m currently presenting on and when.
Building a Cost Effective Reporting system.
This presentation is all about using the right tool for the job. At my current company we moved from a vertical scale system to a horizontally scalable system. SQL Server does a lot of things really well but scale horizontally is not one of them. Using a mix of open source technologies and SQL Server we were able to get a highly scalable system at a much better cost. If you have been looking into #bigData technologies and what you can do with them(or what all the buzz is about) this is a great presentation to get you started and show you what can be done when you use the right tools for the job.
I will be presenting this at SQL Saturday #271 in Albuquerque NM coming up on the 25th of this month. This is going to be a really fun event with lots of great presenters. Check out the schedule to see the great lineup. It will before the First SQL Saturday that I am presenting at that I did not in some way organize or help put on so this should be very interesting for me to observe just as a speaker and attendee.
I’ve submitted this same topic to Sql Saturday #287 and Sql Saturday #295. I hope to be able to present at both of these events in the next few months.
Along with presenting I’m working on 2 other Major events coming up in the next few months. Utah Code Camp will be held on March 15th 2014. This will be our largest event to date and the most diverse with many varied topics all related to technology in some way.
Big Mountain Data is coming up April 12th 2014. This will be an event all about Big Data. Whether you are an expert in the field or just getting started and want to know how to work with big data we will have something for everyone. You can register now and we hope to have the schedule up very soon for this event.
I’m looking forward to a very busy next 4-5 months and hopefully I will see many of you at one of these events.
PASS Board Q&A 2013 Summit
This year at the PASS Summit the Board held an open Question and Answer session. They have done this for the past few years and it’s been very helpful for us to ask questions of the board. I wanted to extend those ideas after the summit but wasn’t sure the best ways to give feedback to the board.
Now don’t get me wrong I’m good friends with several board members and I have no doubt that I can send them an email (I already have) with this information and they can consider it. But what if you are not in my position? What if you are member of PASS that just wants to make suggestions to the organization? Perhaps you have worked with other large volunteer organizations and you have great ideas on how to make things better. Well unfortunately your only choice from the website is to email a member of PASS HQ on the about us page. So who do you email? From the titles you can probably figure out the right area that might help you but what then? How do you know what happens with your suggestion from that point? My suggestion to PASS is to start giving us a way to easily give feedback and to track that feedback until completion. A simple ticket tracking system.
As DBA’s and Developers we track all sorts of things through ticket tracking systems. Bugs, Projects we are working on and feedback from end users. I’m suggesting the same thing here. PASS needs to get a simple form we can use on the website to give feedback. That is then assigned to a Board member/portfolio and worked on till completion or if the task is not appropriate then it can be closed in some manner that gives a reason why it can’t be done. The requestor would get the feedback from the ticket so they knew the status of the suggestion. We would have ownership and accountability as a Board member/portfolio would own the tickets.
This process would allow us to talk about specific items in the future events and PASS meetings. We would be able to track progress exactly and what items are being worked on. Overall it would make management of the many projects going on much smoother.
One suggested tool could be Trello, we use it in two different organizations that I volunteer in and it’s a great way to create simple stories and put them on a board to be worked on. I am sure lots of tools exist for this sort of thing the important thing is getting something in place to capture feedback in the future and to give the end user knowledge of where that feedback stands.
Another suggestion that Thom made as well is User Voice. Looks like a good site that could have some great tools as well for managing the projects.
As I mentioned above I have sent this to the PASS Board already and hopefully they will consider it as a future project. If you think this is a good idea perhaps sending an email to a board member of your choice mentioning this idea would be good.
I put a #1 at the top of the post since I have a few more suggestions for the PASS organization as well and they will show up as future blog posts.