Doug Lane

SQL Server Entertainer

  • GitHub
  • LinkedIn
  • Twitter
  • YouTube
  • Blog
  • About Doug

7 Reasons Why Abstracts Fail

May 15, 2013 by Doug Lane

I just wrapped up my second go-round as a member of a PASS Summit Abstract Review Team, and I want to share some of the missteps that torpedo an abstract’s chances of being selected.

Last year, I reviewed the Application Development submissions; this year, I was the lead for the Professional Development Team. Between my work on these teams and reviewing abstracts for SQL Saturday here in Denver, I’ve read and re-read about three hundred abstracts. While I’m no Adam Machanic (who’s read thousands of them), I’ve read enough abstracts to recognize where many of the rejected ones stumble.

Although the call for regular sessions has closed for this year’s PASS Summit, there’s still the call for Lightning Talks (ten-minute sessions) yet to come, and there are always SQL Saturdays to submit to. I’m hoping that by reading this, you get a better sense of what may be holding your abstract back and have a better shot at getting chosen for future events.

(Also, if you submitted a professional development abstract for the 2013 PASS Summit and it’s rejected, you’ll get our team’s comments in addition to the standard reason for rejection. We hope it’ll be useful feedback for you.)

Here’s what I’ve seen in abstracts that don’t make the cut, and how severe the damage can be to its chances:

1. Spelling/grammar errors

100% preventable.

Potential damage to abstract: Catastrophic.

Yoda
Avoid these errors and a successful writer, you will become.

2. Rambling

Some abstracts, given the chance, will go on at length without really saying anything of substance and to a reader it is at first a mild irritant, later progressing to restless tedium followed by disdain and slight regard, until finally the reader can take no more and…we’ll discuss XQuery bas

[Truncated by character limit, which went unnoticed because author copy-pasted from elsewhere and didn’t check it after pasting.]

Potential damage to abstract: Catastrophic.

3. No examples of what I will learn.

How do I know if I already know the things you’re presenting?
By giving very specific examples of what will be presented, you’ll accomplish these three things:

  • You’ll weed out potential attendees that would say your material was too basic (and therefore rate your session lower).
  • You’ll help differentiate your abstract from others covering the same topic.
  • You’ll attract people who are looking to answer that very question, and will likely rate your session well because of it.

Saying you’ll cover “how to manage transaction log sizes without truncating” beats “transaction log management” every time.

Potential damage to abstract: Heavy.

4. Hash tags

They seem out of place when I see them in abstracts. I’ve been to numerous sessions where the presenter asks how many attendees are on Twitter. I’ve never seen more than half the audience raise their hands. What does a hash tag mean to people who aren’t on Twitter? Do they see hash tags and think they’re temp table names?

Potential damage to abstract: Light. May screen out some non-users of Twitter unnecessarily. More so if the hash tag is obscure or ultra-specific.

5. You don’t understand my pain

Cheesy as they are, infomercials work for a reason. They nearly always start by asking a quesiton acknowledging a painful situation you have: “Do you suffer the embarrassment of explosive and uncontrollable belching?” Immediately you share a bond with the narrator; you’ve both suffered this problem and you understand each other’s pain. You  nod and say, “Oh yeah, I know exactly what that feels like. I burped my wedding vows full blast.”

Evoke that same connection with your readers. Tell them you’ve been there, suffering as they are now, and you can help them. Skipping this step puts you at a disadvantage.

Potential damage to abstract: Moderate, by omission.

6. Details that aren’t really details

Unless elaborated on, these words don’t create a picture of what the session will be like:

  • Interactive
  • Hands-on
  • Fun

Interactive could mean saving the last ten minutes for Q&A, having an audience volunteer run a demo for you, or polling throughout the session. I need to know what that means.

I don’t get excited about the word “fun” in an abstract because my experience has been that the speaker is who’s fun, not the abstract. Certain speakers like Buck Woody and Matt Masson bring the fun no matter what the topic. Speakers like them earn a reputation for being fun; they don’t turn it on and off for certain topics.

Potential damage to abstract: Light to moderate. This is most damaging in abstracts where details are absent and there’s heavy emphasis on the fun/interactive part.

7. Takeaways that aren’t takeaways

Unless elaborated on, these words don’t tell attendees they will learn:

  • Lessons
  • Skills
  • What to do/what not to do

Imagine for a moment that you’re at a power tool conference and the sessions are a la carte — that is, attendees are paying for each individual session they attend. You have to choose between two sessions:

Session A states: “You’ll learn the skills you need to operate a nail gun successfully.”
Session B states: “You’ll learn how to operate a nail gun using best safety practices, how to remove a cartridge jam, and how to tell when you need a separate pressure regulator.”

Is there any debate which abstract will get your business?

Potential damage to abstract: Devastating. It’s highly unlikely an abstract with vague takeaways will get selected.

These are only my opinions. I don’t speak for any of my associates on any review team I’ve been a part of. Other reviewers have their own ideas about what works in an abstract, so don’t take what I say as a blueprint that guarantees success with any review process. However, by avoiding pitfalls like the ones I’ve outlined, I’m certain you’ll become a more successful abstract writer.

Filed Under: PASS Summit, Presenting

If You’re Not Sure About Submitting an Abstract

April 1, 2013 by Doug Lane

The 2013 PASS Summit Call for Speakers ends in less than 48 hours. If you’re on the fence about whether or not to submit an abstract for the Summit (or any other event, for that matter), here’s what I say:

DO IT! DO IT! DO IT!

Get started here. Time’s running out!

UPDATE: If you’re having trouble getting your ideas in writing, try using one of these submitted abstracts as a template. I have no idea if they’ll get chosen but they’re very well written.

Kendra Little: How to Tell When Storage is a Problem

Brent Ozar: Why is SQL Server Slow RIGHT NOW?

and here’s one of mine: The Missing Manual for Data-Driven Subscriptions

Good luck!

Filed Under: PASS Summit, Presenting

The Group In Which We Are The Norm

October 30, 2012 by Doug Lane

Early this year, I stumbled on to a blog post by author and speaker Simon Sinek. In his post entitled “Fitting In“, he writes about his experience at Comic Con — how it made him realize the lengths to which we’ll go to fit in, and why trying hard to fit in isn’t a good strategy. I read the post and right away began to think of how this relates to the SQL Server community.

The 2012 PASS Summit begins next week and if you’re a first-time attendee, it’ll probably be your first immersion into the SQL Community. You may find yourself trying to look or act a certain way to try to fit in. Don’t. Resist the urge, the fear that tells you you have to conform. Sinek says rather than working to fit into some group, work to find the group in which you already fit. Many people — myself included — have found that the SQL Server community is a group in which we already fit. We all love working with SQL Server and we love data. If we didn’t, we wouldn’t commit to 3-5 days of intense learning about it. We can reason therefore, the people you’ll meet next week are as serious and dedicated to their work as you are.

Of course, we have different interests outside of SQL Server, but when you find someone who shares one of those interests, it makes your common bond that much stronger. For example, I’m a fan of film scores and composers like Jerry Goldsmith, James Horner, and Michael Giacchino. It happens that Mike Fal (b | t) is also a fan of that same subject. Discussing film scores is how Mike and I became friends. Allen White (b | t) and I talk about show tunes, Jes Borland (b | t) and I talk about running, and Steve Jones (b | t) and I play baseball together. None of that would have happened if I didn’t put myself out there and share my outside interests with others.

(Also, there are a lot of people who like Star Trek.)

(You’ll see.)

I let some of my personality show at the Summit last year but still held back for fear of rejection or not fitting in. This year, I’m going to fearlessly be me and it’s going to be wonderful. I suggest you do the same. Be yourself. Be comfortable. This is, as Sinek says, the group in which you are the norm.

A Word About SQL Karaoke

From what I’ve seen, karaoke at the PASS Summit has blown up to a much bigger deal this year. If you’re a first-timer, you may wonder if the singing is competitive or only for the talented. It’s not. It’s just really fun and really popular. If you can’t carry a tune very well, don’t worry. Neither can I. Just enjoy yourself whether you decide to sing or not. That’s the whole point anyway.

See you in Seattle, my friends.

 

Filed Under: Career, PASS Summit

A Conversation About Abstracts Between Committee Me and Rejected Me

June 7, 2012 by Doug Lane

Last year, I submitted abstracts to the PASS Summit for the first time. I sent in four abstracts and all four were rejected outright. I took the rejection pretty hard, especially considering all four were rejected for no other stated reason than “max sessions allocated for track” — in other words, simply not good enough. This year, I served on the abstract review committee for the AppDev track. I not only wanted to serve the SQL Server community in this way, but I also sought a better understanding of how abstracts are selected, and what makes an abstract a winner. To ease the sting to those who are going to be rejected for this year’s Summit (or were rejected in years past), I thought I’d share with you a conversation between last year’s me (the rejected applicant) and this year’s me (the committee member).

Rejected Me: I suppose you know why I’m here.

Committee Me: First, let me tell you, very sincerely, I’m sorry you didn’t have any abstracts selected this year.

"Well, we still have the call for Lightning Talks."

Rejected Me: Thanks, but I’m still pissed about it.

Committee Me: I understand. I’ve been there. I wasn’t on your track’s committee, so can you tell me your reasons for rejection? Maybe I can help you understand.

Rejected Me: I don’t know, all they said were “Max sessions allocated”.

Committee Me: That just means you wrote adequate abstracts, didn’t leave anything incomplete, that sort of thing.

Rejected Me: Duh. I was thorough. I spellchecked and filled in all the required info.

Committee Me: It also means, for whatever reason, all the accepts and alternates were better than yours in the eyes of the committee.

Rejected Me: Can’t they tell me more than that?

Committee Me: I know it stinks not getting better feedback, but keep this in mind: three volunteers took time to evaluate as many as over 200 abstracts. Most of them are complete and halfway well-written. They don’t have time to give full critiques to each one.

Rejected Me: But that doesn’t help me. How will I know what I need to do better next time?

Committee Me: I don’t want to sound harsh, but it’s not their job to counsel you on why they didn’t like your abstracts more. Read the abstracts that were accepted and you’ll see commonalities. Learn from those.

Rejected Me: Fine. But why does [this person] always get to speak? Why not let some new people get a chance?

Committee Me: It just so happens that experienced speakers tend to be experienced abstract writers. Like I said, learn from the successful ones.

Rejected Me: I submitted three of my four abstracts in the same subject area. Surely they could have picked one of them.

Committee Me: Not necessarily. It could be they thought the target audience would be too small, or they already had it covered by another abstract — one that was better written.

Rejected Me: Is it me? Maybe my abstracts weren’t the problem.

Committee Me: Could be. Your experience does factor in, but we do want some newer speakers in there too. How many events have you presented at before you submitted to the Summit?

Rejected Me: Two.

Committee Me: Hmmm, that’s not many. Did you do well at those events?

Rejected Me: My feedback was good, so I don’t think I’ve got a bad reputation.

Committee Me: Certainly no reputation is better than a bad one, but neither case is very helpful. Keep speaking when you can find the opportunity. You’ll be much more established by this time next year, and that can only help.

Rejected Me: I suppose.

Committee Me: Try to remember this is the world’s largest SQL Server conference and the people that speak here have earned their way up on stage by building a history of successful presentations and writing good abstracts. Hang in there. Work to improve your content, delivery, and abstract writing, and you’ll get the call eventually.

Rejected Me: Thanks. But why didn’t they like my abstracts this time?

Committee Me: Well, if it’s any consolation, it could be someone on the committee really liked one, but it wasn’t enough to float it up high enough to make the cut. So it may not have been unanimously rejected. Apart from that, I don’t know what else to say except I’ve been in your shoes. I know exactly what you’re feeling.

Rejected Me: I don’t even know how close I came. Can’t they publish the final rankings or comments?

Committee Me: That’s an interesting idea, but one with a lot of complications. First, this is done by committee, so it could be one member writes glowing comments but the other two rate it low enough that it doesn’t make the cut. You end up with great comments and a lower ranking. To me, contradictory feedback is worse than no feedback. Another problem is that we simply don’t have time to comment specifically on each abstract. It’s hard enough to try to rate them all fairly. I even went so far as to make sure I wasn’t hungry, tired, or mad about something before reviewing a chunk of abstracts because I wanted to be in an equal frame of mind across them all. (Proof there’s a rational basis for doing so.) Also, if we posted complete rankings, we’d get a lot more questions from people wanting to know why they were ranked so low. It’s the committee’s job to rank abstracts, not to publicly defend the rankings. Sorry.

Rejected Me: This still sucks.

Committee Me: Yes. Yes, it does. I hope I’ve helped a little.

Rejected Me: A little.

I hope I’ve helped a little. Hang in there.

Filed Under: PASS Summit, Presenting

PASS Summit 2011 Recap: Super-sized!

October 21, 2011 by Doug Lane

Set the Wayback Machine

It was a year ago, October 2010, when I first decided I wanted to go to the PASS Summit. I asked for my company to cover the costs, and I was denied. I could hardly blame them – requesting $3000 on four weeks’ notice was asking a lot. Plus, I was hitting a rough patch with my job and not doing my best. So, from my desk at work, I watched the stream as Tina Turner kicked off day one of the Summit. I was bummed out.

But I was also motivated.

I made definite plans to alter the course of my career. I decided to take my career seriously by:

  1. Becoming a better student of SQL Server by learning more and getting certified.
  2. Getting into blogging and presenting.
  3. Going to PASS Summit 2011, with or without company support.

Over the next year, I made significant progress with the first two goals – I earned one MCTS and narrowly missed a second, blogged a little, and delivered five presentations.

When the call for speakers opened up for the 2011 Summit, a lot of prominent figures in the SQL community were encouraging people who had never submitted before to do so. I submitted four regular session abstracts for the Summit.

All four were rejected.

I took it the rejection hard because I didn’t get any reason aside from there were already enough Reporting Services sessions chosen. I got over it by the time another call for speakers came, this time for lightning talks (five-minute sessions). I submitted two abstracts. One was accepted (“The Two Most Powerful Properties for Dashboards”), and I was elated. I was going from a SQL nobody to a PASS Summit speaker in just one year.

SQL Saturday and the Portland 10k

Friday, October 7

I opted for the bonus size Summit experience this year: SQL Saturday in Portland, a 10k race, two pre-conferences, and the three-day conference.

At the Portland SQL Saturday speaker dinner, I was reunited with old friends Bill Fellows (t), Jes Borland (t), Buck Woody (t), Allen White (t), Tim Ford (t), Dev Nambi (t), Yanni (t) and John Robel, and Erin Stellato (t), among others. I got to meet Arnie Rowland (t) (great guy) for the first time and received a thoughtful speaker’s gift — a Logitech presentation remote.

I slept terribly that night.

Saturday, October 8

SQL Saturday. My session, “Developers are from Mars, Report Servers are from Venus” was scheduled in the best time slot: 10:15-11:30 (late enough that more people have trickled in, early enough that brains aren’t full yet and the audience can still focus). I had the pleasure of not only presenting to a mostly full room, but also having several SQL buddies in the audience. Kendra Little (t), Bill, Allen, and Jes got to see me present for the first time. The session went very well, although Bill had to prompt me kindly (and with the subtlety of a derailing train) to give away swag.

As the day went on, it became apparent that the air conditioning in the building was programmed to not run on the weekend. However, by the time I sat in on Jes’ Reporting Services session, the auditorium had become a sauna. In the last time slot of the day, I think I saw one attendee at Bill’s session finally ignite. Another may or may not have melted into the floor. I don’t really remember; it was so hot I may have hallucinated. (Note: Bill knows his stuff when it comes to SSIS. Some of what he presented, I heard repeated in other sessions at the Summit.)

After a brief stay at the after-party, I headed back to the hotel to get a good night’s sleep for the big day ahead. I didn’t sleep well.

Sunday, October 9

On a cold, slightly drizzly morning, I jogged over to catch the charter bus to the 10k start. Our registration e-mail said there’d be a bag pickup. At the starting line, we were told there was not a bag pickup. Enough icy stares from the athletes prompted the race director to hastily create a bag pickup.

For this race, I had trained consistently, at altitude, for about eight weeks. I trained at a 7:00/mile pace but considered that to be wishful thinking. A 7:30/mile pace seemed more realistic.

I focused on staying close to a guy who resembled a hardcore Kenyan speedster. After the first 300 meters, I passed him and never saw him again (so much for appearances). I ran the first mile in 7:00. Fast, I thought, but I knew it was probably adrenaline-fueled and I should expect to slow down. The second mile was mostly downhill and when Runmeter told me I’d done it in 6:27, I was not really surprised. By the end of five miles, I was feeling the hurt. It helped that the final 1.2 miles tracked past a cheering crowd. I kicked with about 200 meters to go and finished in 43:34, a 7:02 split.

I ran and skied cross-country in high school. I used an old trick from my racing days to my advantage on Sunday: tangents. By anticipating curves in the course and running the tangent lines, you can shave off waste distance from the course. Based on Runmeter’s stats, I sliced sixty meters off the course by running in long, straight lines. I don’t care if I’m not young anymore as long as I’m still crafty.

With a handful of other SQL runners, I took the Amtrak line to Seattle (I highly recommend it — way less fuss and more comfort than air travel. Bottles over 3.5 ounces are not hunted like fugitives by TSA agents and legroom is not measured for reasonableness using pygmies as a standard)

Bill and I checked into the Sheraton, and promptly went to bed.

(Went to sleep in our respective beds, that is.)

Probably due to excitement about the week ahead, I slept badly.

PASS Summit Pre-Conferences

Monday, October 10

Upon waking, my first thought Monday morning was, “Holy S#!t, I’m actually at the Summit!”

I went to the pre-con, “A Day of SSIS in the Enterprise” presented by Andy Leonard (t), Matt Masson (t), and Tim Mitchell (t). Of all the presentations I have seen in the last year, this was the gold medalist for both execution and content. I got more ready-to-implement ideas and advice from this session than from all the others I attended at the summit combined. It was that good. (Once more for the Program Committee: it was that good.)

I was especially impressed by how the three presenters handled questions. One would give an answer, then another would add a thought to it, then the third presenter would wrap up the answer with their own insight. When they disagreed with each other on a design choice (e.g, file system vs. SQL Server storage for packages) they stated their respective cases. As a result, the audience was treated to multiple points of view on many issues that SSIS developers confront.

I wouldn’t ordinarily comment on lunch — conference food is remarkably unremarkable — except that lunch on this day was incomplete. Somehow, the caterer for Monday’s lunch ran out of chicken. That’s not a big deal, unless there’s no other meat alternative, which there was not. Curry tofu (think stale marshmallows hit with pepper spray from across the room) was the only other meat-like item. Lesson for the day: don’t wait until the fifty-fifth minute of a sixty-minute lunch to go get food, or just eat out.

In the evening, I went to the party at Lowell’s hosted by Steve Jones (t) and Andy Warren (t). I met a lot of new faces there and caught up with more acquaintances, including several SQL Cruisers. I got there early enough that I scored a free dinner, which was positively delicious. Later, it was off to Bush Garden for karaoke night. I sang “One Week” by Barenaked Ladies — my anchor song — and “Only the Good Die Young”, which was awful. On the way back downtown, Jason Strate (t) walked through a foot-deep fountain, to no one’s surprise.

I got back to the hotel around 2:30 a.m. and attempted to sleep. Generally speaking, I failed.

Tuesday, October 11

It started to catch up with me that I hadn’t slept a lot the last few days. It didn’t help that I was signed up for a second pre-con, Stacia Misner’s (t) session “MDX, DAX, and DMX: An Introduction to the Languages of BI.” I didn’t get as much value out of this session for a few reasons:

  1. Exhaustion was beginning to take a toll on me.
  2. The session was heavily weighted toward MDX (about six and a half hour’s time) and I was more interested in DAX (one hour’s time).
  3. I just don’t learn as well if I’m looking at code in SSMS. I do better with demos or slides.

Just the same, I’m eager to see another of Stacia’s sessions. This one ended up being a little light on DAX and MDX, that’s all.

Welcome Reception

I’ve heard PASS is trying to make the first-timer’s experience a more inclusive and more appreciated one. One thing they did was pretty special in that regard.
Although I didn’t participate in the networking or big brother/sister events for first-timers, I went to the conference center for the welcome reception. While standing outside the ballroom chatting with friends, I ended up getting herded into a large conference room adjacent to the ballroom. We all stood around, lined up in front of a doorway, awaiting instructions and knowing something was up. The screen at the front of our room lit up with the image of Rushabh Mehta (t) on stage. He welcomed the crowd, then spoke about how exciting it was to have so many first-timers in attendance this year. With that, doors opened in front of us and we entered the ballroom to a Super Bowl-like introduction: stage lights, fog machines, and a crowd lined up along the red carpet. I loved the entrance and the feeling of being a superstar, if only for about eight or nine seconds. Well done, PASS.

The rest of the night in short:

  • Red Gate/SQL Server Central casino and award party for Jeff Moden, Exceptional DBA for 2011.
  • More karaoke at Bush Garden – lots of locals in the bar so a lot more songs in the queue. I murdered ELO’s “Mr. Blue Sky”. Mark Vaillancourt (t) learned the hard way to never sing “White Christmas” – it repeats. And repeats. And repeats.

I finally got a passable night of sleep.

Wednesday, October 12

Finally, my first SQL Run. Bill and I got down there just as the crowd was leaving. I was pleasantly surprised at the size of the group — close to forty runners. I hope this tradition keeps up, and I hope I’m not so sacked next time around.

I was fortunate to be given a spot at the blogger’s table for Friday, and an invite to sit in the reserved section directly in front of them on Wednesday and Thursday. The Wednesday keynote was going along well enough until…Contoso Frozen Yogurt.

The Blogger's Table at the 2011 PASS Summit
Yogurt jokes at the ready.

I had held back mocking any of the BI enhancements until they stated that according to their data, “Kids love frozen yogurt.” I won’t repeat the tweets here, but the blogger section had a lot to add with tweets about Dateline’s “To Catch a Predator” and “FREE YOGURT” spray-painted on the side of a van. Lesson for Microsoft: run your demos by someone who can tell you if they’re ripe for mockery.

After the keynote, I couldn’t fight it any longer — I went back to the hotel and took a nap. If the lesson isn’t obvious by now, I’ll state it: pace yourself at the Summit.

Jessica Moss’s (t) HIPAA session was great, except when my phone rang out loud. (If you own an iPhone 3G or 3GS, the ringer toggle sticks out far enough that a shift in your pocket can switch it back on, which is how I got burned.) It wrapped up in just under an hour, so I headed over to catch the end of Jes Borland’s talk. Based on what little I saw of that session, she handled her first PASS Summit presentation with ease. Keep your eye on Jes, people. She’s a SQL superstar in the making.

The remainder of the day:

  • Bradley Ball’s (t) excellent lightning talk incorporating the show “24”
  • SQL Cruise meetup & thank yous to sponsors
  • Speaker appreciation party
  • Bush Garden – “One Week”, “Amish Paradise”

Thursday, October 13

A better opening presentation this time, followed by an outstanding Matt Masson session on what’s new for SSIS in SQL Server 2012. Before Monday, I hadn’t heard Matt Masson present. In fact, I hadn’t heard of Matt Masson at all. Matt is now on my list of must-see speakers. An illustration why: when I walked into the room, he was killing time before the session demonstrating how he could use SSIS to separate his Facebook friends from his frenemies, who were — as he put it — all plotting against him. He’s very funny and very sharp.

Later, during this session, a most incredible opportunity presented itself to me.

I was watching Twitter and posting useful tidbits from the session when, around 11:00, I saw Allen Kinsel (t) trying to fill in a last-minute cancellation for 1:30. I’ll let my Tweetdeck stream tell the rest of the story (note: tweets show MST, so subtract one hour for Seattle time).

That’s right, I jumped in and gave a regular session with less than two hours to prepare it.

In fairness, I should mention a few facts:

  • The session I gave was one I’d given five times before, including SQL Saturday just five days earlier. I had already put about seventy hours of development and rehearsal time into it.
  • Like less experienced musicians performing an adagio piece, I rushed.
  • I got a mere one or two questions during the session, so I finished in only forty minutes. I was slotted for seventy-five minutes. I ended up answering questions for another fifteen minutes afterward.

I spent the two hours’ prep time re-styling the deck — all eighty-eight slides — to the PASS Summit template, changing white text to black, and adding zoomed-in screen shots to account for the depth of the room. I also spent that two hours trying to prevent my heart from launching out of my chest cavity.

It was a thrilling, terrifying, and euphoric experience being up on that stage. I had wanted achingly for months to give a full session at the Summit and because I recognized I was at the intersection of opportunity, preparation, and damned good luck, I did it.

My view from on stage
Terror at 36,000 x 10^-4 Feet!

That night, my body began to revolt against its perpetual tiredness. I had dinner at Elliott’s with the Denver SQL User Group. I was happy to see we had over thirty people turn out — a healthy gain over last year’s ten or so, from what I heard. I stopped by my hotel lobby and had a long and thoroughly enjoyable chat about politics with Mike Walsh (t), who was very civil and open-minded.

As I went to bed, I reflected not only on the speaking experience, but also on how supportive my SQL Server colleagues — my friends, really — were in helping me get that session not only noticed and accepted, but also filled with attendees. Take another look at the Twitter stream above. The longest I have known anyone in that stream is eight months, and yet they all were publicly pulling for me to succeed.

Truly, this is community.

Friday, October 14

Honestly, the rest of my 2011 PASS Summit was a blur. Dr. Dewitt’s keynote on the worlds of structured and unstructured data helped me, and I suspect a lot of others, understand what’s going on on the other side of the data fence, and how we shouldn’t ignore the importance and interconnectedness of our collective backyards.

The lightning talk went well, though again, I rushed. I talked about how framing matters with dashboards, using signed photos of donkeys as examples. (The photos were not signed by the donkeys themselves — that’s ridiculous.) Once my lightning talk session was over, I said my goodbyes, rolled my suitcase onto the light rail, and flew back to Denver completely wiped out.

What I Learned

For my presentations, I have a lot of useful feedback to learn from. I intend to put it to good use and improve on my performance as a speaker. I have feedback to share with you as well: some suggestions for the Summit that I learned from this year’s event.

Do:

  • Pace yourself. Get enough sleep early in the week so you aren’t dragging come Friday.
  • Bring business cards with your Twitter handle on them. If you don’t have a Twitter account, get one and get active with the SQL community.
  • Use a real portrait photo of you as your Twitter avatar. You’ll be more memorable to others.
  • Go out for lunch somewhere unique to the host city. Let’s be honest, convention food has a low ceiling for taste. In Seattle, there’s fresh seafood all around and it’s gooooood. Go get some.
  • Attend as many off-hours activities as you can handle. This is where friendships are forged. Whether it’s a morning jog, morning prayer, or (technically speaking) morning karaoke, people want to connect with you through these activities.
  • Stay in a hotel a reasonable walk from the convention center. Being able to get back to your room quickly and ditch your swag/change clothes/take a nap frees up more time for the fun stuff. Plus, a lot of people hang out in the lobby or the bar. You want that to be your lobby, your bar.
  • Bring a power strip with a long cord. Six feet is okay, twelve feet is fabulous. Outlets can be a long way from where you end up sitting. One of the recommendations for next year is to have power strips for pre-con attendees. That’s great, but how will you stay juiced during the actual conference? You’ll need a power strip with a long reach, so come prepared.
  • If you want to present a regular session but aren’t an official alternate, be an unofficial alternate. I was amazed to hear how quickly PASS burned through their alternates. As a lightning talk speaker, I had access to the PowerPoint template. I could have styled my presentation ahead of time and used the prep time that day to rehearse. Next year, if I’m a speaker I’ll have a second deck ready and styled. You should too. Even without the official template, you can still make sure your deck and demos are ready for a large room and audience with ZoomIt or zoomed-in screenshots.
  • Buy the DVDs. You can’t be everywhere and see every session. Or can you? You can, and for the bargain price of $125 + shipping and handling. ORDER NOW! (Update: the $125 price was valid until the end of the Summit. The current price for attendees is $195 — a great deal just the same.)

Don’t:

  • Bring dress clothes, unless you have a specific reason. I wasted baggage mass on a nice shirt, pants, and dress shoes. You’ll be on your feet so much, you’ll want good walking or running shoes to keep your feet happy. Also, the Summit is CBC on the dress compass: casual-business-casual, close to due casual.
  • Spend any time in your hotel room unless it’s transition time or you need a nap/shower. Unless there’s a networking event going on in your room, all the action is going on somewhere else. Use your hotel room for sleep and refreshing.
  • Forget to turn your phone off before a session begins. Don’t rely on a mute switch — turn the ringer volume down to zero instead. That way if the switch flips accidentally, the ring still won’t be audible. If you leave your phone on, or worse yet — answer it, the audience will judge you. Oh, how they will judge you.
  • Feel like you have to attend a session in every time slot. Your brain will start overflowing mid-day Thursday if you’ve been pouring session after session into it. Skip one slot here or there and go talk with other people, see the vendor exhibits, or reflect on what you’ve learned so far. Buy the DVD’s if you’re afraid of missing out on something. (Remember, I told you to ORDER NOW!)

In closing, I’m grateful, truly grateful for the adventure I had at this year’s PASS Summit and to the people who helped it unfold as it did. I got to reconnect with old friends, make a lot of new ones, and scratch the year-long itch to be at the world’s largest and greatest SQL Server conference. I got the opportunity to present twice (which I have to believe is an extremely unusual occurrence for a first-timer), and enjoyed every second of it. I can’t wait for the next adventure to begin.

Filed Under: Career, PASS Summit, Presenting

Subscribe now!

Don't miss new posts as they publish. Enter your e-mail address to subscribe!

Your e-mail address will stay quietly between us, like that time I set the carpet on fire by accident.

Copyright © 2025 · Outreach Pro on Genesis Framework · WordPress · Log in