Well, here it is, Day 30 of the #vdm30in30.

Here’s some stats on the last 30 days of posts:

  • 23,343 Words
  • 213,374 Characters
  • 238 Sentences
  • 29 Paragraphs
  • 1 hr 25 mins Reading Time
  • 2 hrs 10 mins Speaking Time

Most used words:

  • puppet 264 (4%)
  • provider 116 (2%)
  • puppetlabs 93 (1%)
  • package 90 (1%)
  • should 87 (1%)
  • code 85 (1%)
  • cockpit 85 (1%)
  • opt 84 (1%)
  • executed 80 (1%)
  • run 79 (1%)

Not sure how accurate that is because there’s a lot of code snippets in there, but seems about right: Each post was roughly about 750 words or so.

How did it go?

Honestly, it was sort of stressful a lot of the time.

Thinking of a good topic, then getting a rough idea into a blog post and posting it is hard to do, every day for 30 days straight.

For most of the month I was 3 or 4 posts behind and desperately catching up.

It forced me to write up a bunch of semi-formed ideas for blogs in the super early stages, as I was getting more behind, forcing them out to the surface and it was a great way of picking up a bunch of half-completed blogs I had in drafts for months.

My post on the Puppet RAL, which was intended to be a single post but bloated out into 4 posts helped.

Plus a load of issues I actually worked on during the weekday ended up being good topics for blogs also, such as the work on JMX, debugging Puppet and sigkill, all of which came out of conversations with customers or people from the community.

Would I do it again?

Hmm, not so sure on that one. It was a great experience, but it was pretty draining near the end. Maybe next time I’ll go for VDM15in30!