My hometown SQL Saturday: Albany, NY, July 29

My local SQL user group is hosting SQL Saturday on July 29, a week from this Saturday!

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!

 

Advertisements

So, what’s in it for me… I mean, the company?

The Facebook “Your Memories” feature can sometimes be an interesting thing.  Yesterday, this memory from four years ago came up on my Facebook feed, and it’s one I want to share.

I think I’ve discovered the secret to great interviews — and I’m sharing this for the benefit of other job seekers like me.

Based on some resources that I’ve read (including “What Color Is Your Parachute?”), most job seekers go to an interview wanting to know, “what’s in it for me?” What they *should* be doing is asking the company, “what’s in it for them?” In other words, ask the company what they want and what you can do to fulfill it. Sell yourself on the precept of what value you bring to the company.

For the past two days, I’ve gone into interviews with this mindset, and it has served me well. It’s one of the reasons why I feel like I aced yesterday’s interview. Also, during this morning’s interview, I asked the question, “what are intergroup dynamics like? What other groups do you work with, how are the relationships, and what can I do to improve them?” When I asked that, I saw nods around the room that said, “that’s a good question!”

It’s too soon to say whether or not I landed either job, but I feel like I interviewed well, and I feel like I have a fighting chance.

Ever since I had this revelation four years ago, I’ve used this approach in every single job interview.  I won’t say that I aced every single job interview — I didn’t — but this mindset has made for better interviewing on my part.

Let me back up a little before I delve into this further.  It’s been often said that you should never not ask questions at a job interview.  Asking questions demonstrates that you’re interested in the job.  I’ve heard stories where a job candidate completely blew the interview simply because he or she did not ask any questions.  Not asking questions demonstrates that you’re indifferent toward the company or the job.

That said, it’s also important to ask the right questions.  Never ask about salary or benefits (as a general rule, I believe that you should never talk about salary or benefits, unless the interviewer brings it up).  If at all possible, try to avoid questions that ask, “what’s in it for me.”  Instead, ask questions that demonstrate, “how can I help you.”

Employers are nearly always looking for value, and their employees are no exception.  When interviewing potential candidates, they look to see what kind of value the candidates offer.  For me, I go to every job interview with a number of questions that I’ve formulated in advance — questions that demonstrate I’m interested, and I want to help.  For example, one question I always ask is, “what issues does the company or organization face, and how can I help address them?”  I’m asking what I can do for them.  It shows that I’m interested, and it shows that I’m willing to lend a hand.

For your reference, I found this information in my local library.  A couple of books I would recommend include the most recent edition of What Color Is Your Parachute? and Best Questions to Ask On Your Interview.  Among other things, these books provide ideas for questions for you to take with you to the interview.  Much of this information is also available on the internet; do a search and see what you can find.

I would also consider attending seminars and conferences, if you are able to do so.  For example, Thomas Grohser, one of my friends on the SQL Saturday speaker’s circuit, has a presentation called “Why candidates fail the job interview in the first minute.”  I’ve sat in on his presentation, and I would recommend it to any job seeker.

I won’t say that this mindset guarantees that you’ll get the job, but it will increase your chances.  This approach shows the interviewer that you’re interested, and you can add value to the organization.

Best of luck to you in your interview.

No rest for the unemployed

A while back, I wrote an article that I affectionately refer to as the “job hunter’s survival guide.”  One of the things I mention in the article is to “keep busy.”  In my current state of unemployment, I’ve discovered that I’m busier than I ever thought I would be.

First, there’s the job hunt itself.  I’ve often told people that “looking for a job is a full-time job.”  I have yet to disprove that theory.  My work days have been spent working on my resume, applying to positions, touching base with my networking contacts, interviewing, taking assessment exams, following up on leads and applications, and so on.  That makes for a lot of work, and it makes up a good chunk of my working hours.

Second, there are a number of things with which I’m involved.  I’ve said before that getting involved is a good thing for multiple reasons.  Since my former employer and I parted ways, I’ve been to two SQL Saturdays (including one in which I presented), and am scheduled to present at a third one in July.  I’ve rehearsed with my wind quintet.  I’m involved with my local SQL user group.  I work out at the gym.  I also have a number of things with other groups (such as one of my alumni groups) that I need to address.

Third, even staying at home doesn’t offer a break from my to-do list.  Household chores need to be addressed — I have a long list of items around the house.  We have two cats that want attention.  Those of you who are homeowners understand the struggle.  When you own a house, there’s never a shortage of things to do.

For someone like me, I’m finding a few other things to keep me busy.  If you’re reading this article, you’re looking at one of those things.  A writer — even a ‘blog author — always has something to do if he or she has something to write about.  I also have some presentation ideas that I want to develop; hopefully, you’ll see them soon at a SQL Saturday near you.  In doing so, I’m looking for more opportunities to learn new things and keep myself up-to-date.

Staying busy is a good thing; you don’t want to be idle.  If a prospective employer asks what you did during your downtime, you can list all these things you did to keep yourself busy.  When you’re in the job market, small things like this can give you an edge.

Reinventing yourself

If there’s one thing I’ve managed to develop throughout my professional life, it’s my ability to adjust to my environment.  I’ve practically made a career out of it.  It’s an ability that has managed to keep me sane in tough situations, not to mention that it has enabled me to extend my shelf life long after my role, whether it’s because of an organization’s changing needs or my skill set no longer fits, has become obsolete.

A ballplayer with a long career (yes, here I go again with the baseball analogies) is usually able to do so by developing a new strength after an old one is no longer effective.  For example, pitchers such as C.C. Sabathia or Bartolo Colon have reinvented themselves as finesse pitchers who get batters out using guile and precision, long after their fastballs are no longer effective.  Likewise, a professional who is having difficulty keeping up with modern trends or technology may need to reinvent him or herself in order to remain relevant in the marketplace.

My recent unemployment forced me to take stock of where I am in my career and where I want to be going.  Even before my (now-former) employer let me go, I’d been asking myself some hard questions about who I was.  I had been struggling as a developer, which was making me question whether or not it was what I should — or even wanted — to be doing.  At the same time, I also considered my strengths.  What was I good at doing?  Were these strengths marketable?  Were they skills that I could offer to an organization?  Would I enjoy a position that took advantage of these strengths?

For me, personally, I discovered — or, more accurately, re-discovered — that my strengths were in writing and communication, not software development.  This revelation made me realize several things.  While I enjoyed doing development work, I found that I wasn’t passionate about it.  I was, however, passionate about writing and documentation — to the point that I began steering myself in that direction.  I became openly critical about my company’s documentation (and, in many cases, the lack of).  My SQL Saturday presentations have all been based on writing and communication.  Even in my current job search, my focus has been on positions that emphasize writing and communication over hardcore technical skills.  Having said that, I am also not discounting my technical background; my ideal position is one that takes advantage of that background.  While I am looking for something that focuses on communication, I am looking at my technical background to supplement that skill.

At this point in time, whether or not this strategy lands me a new position remains to be seen.  However, I’ve made some observations.  First, I’ve noticed that prospective employers appear to be more receptive to my approach.  I seem to be getting more and better prospective opportunities, and they are coming quickly.  Second, I’ve noticed that, in conversations and interviews, I am much more confident and assertive.  Third, I’m much more focused in my search — in contrast to job searches in years past, where I would apply to anything and everything that even remotely sounded like a position I could fill.  Finally, as strange as it may seem, I’m finding that I’m actually having more fun with this process.

It’s often been said that when a door closes, another opens.  If a current position or career isn’t working for you, it might be time to take stock and reinvent yourself.  You might discover a new mindset and a new motivation.  You might discover a new passion.  You might even find that reinventing yourself results in a new career path — one that is more satisfying and rewarding than you had ever previously believed.

SQL Saturday #638, Philadelphia

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!

Free agency

Well, after posting an article only a month ago about losing a job, I am now in that position myself.  I was officially dismissed from my position this afternoon.

Yes, I am, admittedly, a little down, but at the same time, I also feel a measure of freedom — the type where I feel like I can spread my wings and fly.  I feel good about my prospects, and I’m sure that I will be landing on my feet soon.

So, time for me to practice what I preach.

Don’t be afraid to screw up

“If you’re not making mistakes, you’re not trying.”
— Wynton Marsalis

“I get knocked down, but I get up again; you’re never gonna keep me down…”
— Chumbawamba

“You’re only human; you’re allowed to make your share of mistakes…”
— Billy Joel

“It’s not how we fall.  It’s how we get back up again.”
— Patrick Ness

It’s been said that (baseball) pitchers need to have short memories.  Whenever a pitcher makes a mistake — say, gives up a home run — he needs to shake it off — forget about it and move on to the next batter.

That being said, he needs to remember it as well.  He needs to figure out what he did wrong (e.g. “okay, he likes the fastball down and away”) and remember not to make that same mistake the next time that batter comes up to hit.  In other words, he learns from his mistake.

This pretty much happens to all of us.  We’re human.  We’re not perfect.  We’re going to make mistakes.  The issue is when we become afraid of those mistakes.  We become so afraid of mistakes that it discourages us from doing things.

Let me make one thing clear.  I’m not talking about people who willfully make mistakes, don’t care, or strive for mediocrity (which, by the way, is a huge pet peeve of mine, and one that I do not tolerate.  That’s another ‘blog post for another time).  I’m talking about people who genuinely care about what they’re doing, who want to do a good job or get better, and are putting in an effort to reach that goal.

As a part-time musician who holds a leadership position, this particularly troubles me when it comes to making music.  Someone doesn’t want to play something because he or she is afraid of screwing up.  Why?  Music is an area where it makes the most sense to make mistakes.  The time spent practicing or rehearsing music is when making mistakes makes the most sense.  It’s called practice for a reason.  It’s time spent to address areas that need to be improved — hence, why it’s important to make mistakes.  Mistakes tell us what needs work or what needs to be addressed.  Mistakes are why we rehearse.  We don’t — and shouldn’t — practice what we’re doing right; we need to practice what we’re doing wrong.

When it comes to music, I attribute part of it to stage fright.  People don’t want to make mistakes in front of other people.  I say, who cares?  So what if you make a mistake?  What’s going to happen?  Are people going to think less of you?  In all likelihood, probably not.  For what it’s worth, I’ve heard — and even seen — professional musicians make mistakes during concerts or live performances.  More often than not, they’ll keep going as if nothing happened.  No big deal.  It’s funny, but I lost my fear of performing (or speaking) in front of groups a long time ago.  I attribute it to realizing that making a mistake isn’t the end of the world.

The same holds true on the job.  Many of us are afraid to make mistakes at work.  Why?  Are we going to get fired?  Unless the mistake is either (1) very large, or (2) numerous, it’s unlikely.  How many of you have had bad days at work?  It happens sometimes.  How many of you have lost your job because of them?  I suspect, not many.

The thing is, we always want to be better at something.  Getting better means getting out of our comfort zone.  When that happens, we’re going to make mistakes.  I’ve often said that “perfection as a goal is okay.  Perfection as a standard is not.”  We’re not built for perfection.  That’s what being human is all about.  Someone once said that “one of the worst quotes ever coined is ‘get it right the first time.’  It’s stupid, because almost nobody ever gets it right the first time.”

Well, someone might say, “what about a profession where you can’t afford to make mistakes, where making a mistake can cost lives, such as doctors and airline pilots?”

For this, I point out a couple of things.  First, there’s a reason why jobs like that require extensive training and practice.  Pilots practice in simulators.  Doctors practice on cadavers and dummies.  In both cases (and probably others as well), students are closely supervised.  These days, virtual reality contributes to these practice scenarios as well.  And even then, mistakes will be made during practice.  Second, professions such as these are becoming increasingly reliant on checklists.  Checklists decrease the probability of mistakes, and are becoming increasingly prevalent in numerous professions.  (I have an idea for a presentation and a ‘blog article about checklists; hopefully, this will be coming soon.)

The ability to make mistakes is important.  We learn from them.  We get better because of them.  They make us stronger.  And once you can address them, overcome them, learn how to recover from them, or eliminate them, chances are that people will say that you’re the master at your craft, whatever that craft may be.