Thanks to everyone that came to my talk at SQL Bits.
Powerpoint here for download.
If you have questions, reach out.
Thanks to everyone that came to my talk at SQL Bits.
Powerpoint here for download.
If you have questions, reach out.
I wrote the other day about a culture of allowing mistakes. We know mistakes are going to happen, so we ought to accept them. Even stupid ones. I make them at times, my wife does, my kid does, so I have been working to not get upset and emotional about them. Instead, hold someone accountable, let them fix things, and try to do better in the future. It’s what I’d want, and what I am trying to do with my family, friends, kids I coach, and others.
Many of us share knowledge and information. One of the reasons I love events like SQL Saturday is that others share their knowledge. I especially appreciate is when someone shares a solution and how or why they build it. Hearing their stories, the reasons for their decisions, and what works well is great. I learn in a similar way from blogs, which is why we syndicate blogs at SQL Server Central and include them in the newsletter.
By the way, if you have a blog and want to syndicate it (full feeds, please), contact the webmaster or submit an article.
We want to share knowledge, but we should also remember to share mistakes. We make wrong turns, and sometimes others might not take our advice because we recommend them. Instead, they might go down the same wrong path as we did previously. They might make the same mistake we did. Sharing and showing how a decision didn’t work well can be a powerful and valuable story. We all respond well when we empathize, and most of us can empathize with a mistake.
Almost every interview I’ve been in has asked me about a mistake, misstep, or other error that I’ve corrected or learned from. Usually, there is some variation on “tell me about a difficult situation” that you need a story about. In a technical interview, this might be based on a programming or database administration problem. In other interviews, this might require you to think about interactions with others.
In any case, I encourage you to keep stories handy for interviews or reviews. I’d certainly also suggest that you blog about them. Writing is a valuable communication skill we all need, especially in these days of mostly remote interactions. Practice writing, get better at presenting your thoughts, and learn to share stories that will help others in their journey to be a better professional.
Steve Jones
Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.
There are plenty of people changing jobs in this economy. In fact, I keep hearing that companies are struggling to find people, though many of them are holding off making offers and looking for qualified people. Unlike the early 90s when anyone with an MCSE got hired without too many questions, companies are being picky today about who they hire.
I saw recently that Brent Ozar wrote his monthly post asking about who is hiring in the database community. There are a number of comments already with job listings, and I’m hoping there are more that appear when this publishes. If you know of a job, post a comment. The wider you spread the news, the better chance you’ll get a person that best fits the position.
There is always opportunity in any market, but there is also competition. Everyone that I talk to who hires people has to go through a lot of resumes and CVs. They sometimes can’t find a person with enough knowledge, and sometimes they can’t find someone who fits in with their culture. Like it or not, getting along with others and fitting into a culture is important. This is still true even in the remote work-at-home structure that has grown in many companies. We still need a team of people working together.
I am an advocate of working on your skills and improving them over time. I’m also a fan of ensuring you are showcasing your skills on your resume and on a blog. I think #SQLNewBlogger is a great way to start preparing for the next position you want, not the one you have now. I have written many posts as examples of how to explain what you’ve learned. You can start that now, rather than being in the situation of Ken, who had his job eliminated.
Spend some time growing your career this year. Balance that with family, hobbies, faith, and friends, but don’t neglect your career. Your employer will, so it’s up to you to manage a career yourself. After all, if you need a job, do you want to get that great paying remote job or get stuck with a job offer that wants you back in an office every day?
And when you get a new job, be ready to hit the ground running and impress your employer. Show them they made the right decision by hiring you. There have been some good posts on getting started at a job. Aaron Bertrand wrote about his first 30 days and Tracy Boggiano is doing a series. I’m really looking forward to what Tracy shares about her new gig.
Maybe you want to write about how you’d start your job over again or maybe how you’d attack a new job if you got one. That could be the type of post that impresses someone enough to hire you.
Steve Jones
Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.
Outside of coping tips, I’m gonna take a break from blogging. I’ve been aiming for 3 posts a week, and mostly keeping there, but it’s created a little stress and I need to handle a bit more stuff at the ranch, so not as much time outside of work for blogging.
I also have some work work to take over. We have a surprising amount of sabbaticals this summer, and some staff changes, so I need to take on a bit more in July/August.
I’ll likely blog here and there, but not consistently.
Of course, I’m sure tomorrow I’ll get 10 ideas for post and this will go out the window, but look for less for a few weeks at least.