I made a post on Sunday, and it triggered a nice stream of comments from people on micro.blog, all of which appeared as comments on my post. Cool! It looks like the webmention support on both ends is working well. As another step in WordPress/micro.blog integration, I am adding my comments RSS feed as a cross-posted feed. After I post this, I will add a comment and see if that appears on micro.blog. Let’s see what happens!
Andy
Wither the history of podcasting?
This week, I listened to episode 167 of the Radio Survivor podcast, titled “Alternative Histories of Podcasting“. The guest was Andrew Bottomley of SUNY-Oneonta, and the conversation covered the “popular” start of podcasting (Dave Winer, Christopher Lydon, Adam Curry, et al), and a look at audio available on the Internet before the 2004-2005 time period. The hosts seemed to take issue with defining “podcasting” as the technical tools making it possible to subscribe to audio files (podcasts) and easily load them to mobile devices (MP3 players, smartphones). I do not deny that the examples that Dr. Bottomley gave of Internet audio files pre-2004 were correct, but I think there is a reason why they were not called podcasting – because there was no “pod” available! For better or worse, the iPod was the first convenient audio player, iTunes was the first convenient way to get audio on a device, and the name “podcasting” grew out of the development of these tools and other tools of audio production and distribution.
I hope that Dr. Bottomley will document his research in this area (seems like he is working on a book). However, I am more interested in finding good podcasts to listen to, and playing around with creating podcasts myself. As Dave Winer has pointed out, creating and distributing podcasts is an open platform – anyone can do it. People can disagree on “who was first” or “what is a podcast”, but I want to focus on the practitioners, the people who are creating podcasts, no matter what the topic.
Knowledge wiki examples
Chris Aldrich posted about an interesting knowledge wiki using Github as the storage of the original content and using Gitbook to render the content. I have a federated wiki instance I have been using for some topics. Chris Aldrich also mentions that his own site serves as a commonplace book, capturing information that interests him. I think this variety of tools and practices is good to see. I have used a weblog in the work environment as a knowledge capture tool, then migrating some content to a wiki. My main observation is a common one: you get out of it what you put into it. If you don’t do much, any tool you use will not be very helpful. If you contribute content on a regular basis, the value will grow and grow over time. Which will you choose?
The effect of music in our lives
Earlier this week, I read a terrific post by Ron Chester on the effect of silence at the end of the performance of a piece of music. I sing in a church choir, and there have been many times that a short silence at the end of a piece can really bring home the feeling of richness to the experience. During the past weekend, I also had two musical experiences that reminded me of the power of live music. I sang at a church retreat, and attended a community band concert. In the retreat, I was moved to tears at one point by one of the songs as I sang. At the band concert, several of the pieces were ones I had played when I was in band in high school or college, and the pieces brought back fond memories of making music with a group. It also helped that the band was excellent, easily the best community band I have ever heard. All of these experiences helped to remind me that having music in my life is an uplifting experience, one that I want to continue to have.
Stars and Stripes Forever – It’s the law!
The Stars and Stripes Forever March is the national march of the United States of America. It’s not just a good idea – it’s the law!
See this article for more background. Also, the Marine Band website has free downloads of Sousa march recordings – neat!
Three tips for satisfying the users of your products
Capturing these so I don’t lose these:
- Make users happy with your product as quick as you can
- Help your users as much as you can after that
- The simplest way to create value online is to save the user time
How embedded software projects run into trouble
Jack Ganssle has written articles for his top ten list of how embedded software projects run into trouble. Most of this could apply to any software project! Here are the links:
- Unrealistic schedules
- Quality gets lip service
- Poor resource planning
- Writing optimistic code
- Weak managers or team leads
- Crummy analog/digital interfacing
- Bad science
- The undisciplined use of C and C++
- Jumping into coding too quickly
- Not enough resources allocated to a project
When I read this, I decided to start working on the asset that is my weblog. I will strive to post something daily, even if it is only a link….
I would like to try this out!