When I started the music4dance blog nearly a decade ago, I considered including a technical component by writing about the challenges of building and maintaining the site. A good friend talked me out of doing that, and I still think it’s the right decision. I’m assuming most of the audience for this blog isn’t particularly interested in what I’ve done to build the site. You’re interested in what you can do with the site, learning more about the relationship between music and partner dancing, and how to find music to dance to. If I’m wrong about you, please let me know; if I get more than a few direct responses, I’ll set up a poll and consider a pivot based on the results.

I am disappointed I never got around to spinning up a technical blog. I’ve learned much over the years while building and maintaining this site. And I generally feel the need to share when solving technical problems. Now that I’m not leading a team of engineers, I’ve given up my primary outlet. So, it finally tipped the balance, and I’ve started some technical writing.

I decided to use medium.com to host my technical writing. That removed the barrier to entry of setting up another site and spinning on what technology to use, and I’ve been happy with the platform. The first series of posts is only tangentially music4dance related but is still motivated by this project. I use a simplified version of the tempo counter applet from the website to compare the experience of writing that app on several multi-platform frameworks. In addition, I took the opportunity to write about my experience in helping build the foundation for Microsoft’s version of that solution. So, if you have a technical bent, please take a look – the first post is “Which Multi-platform framework should I use to write my app?” And if you like it, please do the things that help spread the word. With medium, those things are to clap, follow, and share the link with friends.

As always, I’m very interested in your feedback and read every comment and email. So please share any thoughts and ideas about this post or about the site by commenting below or using other feedback mechanisms listed here. In addition, if you enjoy the site or the blog (or both), please consider contributing in whatever way makes sense for you.