Blog Post

SQL New Blogger Challenge: Week 2 ideas

,

Week 1 of the November 2015 SQL New Blogger Challenge is behind us, and I saw some great posts. Now, start thinking ahead to Week 2!

If you need an idea of what to write, it never hurts to follow the crowd. One of the traditions we have in the SQL Server community is T-SQL Tuesday, started several years ago by Adam Machanic. Each month, a different host throws out the topic on the first Tuesday of the month, and everyone participating has a week to write a post on that topic. Posts are due on the second Tuesday of the month.

This month, Mickey Stuewe is hosting, and the topic she chose is “Data Modeling Gone Wrong”. Pull out your stories about horrible data structures you’ve seen, or write something about how to avoid or mitigate problems with data structures. Anything goes, as long as it’s somehow related to the topic. Just make sure to follow the rules in Mickey’s post so people can find your post.

What? You don’t have any good ideas for this T-SQL Tuesday topic? That happens. Another idea is to review Steve Jones’s list of past T-SQL Tuesday topics. There are 71 other ideas on that list, so there’s sure to be something you can write about.

Don’t forget about our rules:

  1. Write – and publish – at least one post per week during the month of November.
  2. Weekly posts should be published by 11:59 PM each Tuesday (November 3, 10, 17, and 24). This week’s post will be due on November 10.
  3. Posts must be published on some sort of public forum. This can be your own website, Tumblr, WordPress.com, Blogger, LinkedIn – anything, as long as it’s public.
  4. Write on any topic you want.
  5. Tweet your posts after they’re published using the hashtag #SQLNewBlogger.

If you do decide to participate in T-SQL Tuesday this week, make sure to follow their rules, as well. (They’re very complementary.)

Go, write! I look forward to seeing what you come up with!

 

Rate

You rated this post out of 5. Change rating

Share

Share

Rate

You rated this post out of 5. Change rating