Are you the only one doing what you do where you work? When people have technical questions — particularly about data — do they come to you and only you? When you’re stuck on a code or architecture issue, is it solely up to you to figure it out? If so, keep reading.
(If not, why not just keep reading anyway?)
I’ll be presenting at this weekend’s SQL Saturday here in Denver and in a refreshing break from the norm, I won’t be talking about Reporting Services. Instead, I’ll be leading a professional development panel discussion on surviving and thriving as the only technical resource at your company. I call it, “What To Do When It’s Just You.” I’ve spent the last eleven years as the only developer doing what I do. Along the way, I’ve learned better ways of managing time and expectations, solving problems, and recognizing when you’re going to burn out.
However, it won’t be just me giving my own advice on these topics. Also sharing their insight will be Carlos Bossy (t | b), independent BI consultant; Mike Fal (t | b), DBA and blogger; and Glenn Berry (t | b), SQL Server MVP and Principal Consultant at SQL Skills.
Carlos, Mike, Glenn, and I delivered this same session at the Denver SQL User Group meeting back in May. Here are a few comments we got on our event forms:
“I almost feel like those guys could talk for the entire meeting and it would still be valuable.”
“Good insight into solo gigs. Great tips!”
“[This] presentation was one of the best the [Denver User] group has done.”
“Loved the discussion panel!”
If you haven’t signed up to attend SQL Saturday, there’s still time! If you’re already signed up, I hope to see you at our session.