Pardon the self-indulgent meta-blogging.
My boss has a blog post about his fondness for Twitter. I had noticed that a lot of my less formal blogs seem to have gotten quiet recently — this one included.
For my part, there was a lot of blog posts that were simply passing thoughts or sharing links I bumped into (link Refactr’s blog post that made me cranky) — those got moved onto my Twitter stream, because it was easier to share them there, and nobody’s complained about missing them.
This leaves just the more thorough blog posts on topics (like Groovy’s list#flatten and the status of Ruby’s libxml) and reasonably significant announcements (like presentations I’m giving).
The topics posts have gotten a bit slow because they take a lot of work to do right (where I define “right” to include 7 Useful Things and Development Acceleration), and I’ve been busy with work on one hand, moving to Durham on the other hand, and trying to launch a website on the third hand.
If you’re missing my link posts, check out my shared items page. If you just can’t get enough of me, subscribe to my feed on Twitter.
(Oh, and BTW, if you haven’t seen this profound truth, you should.)
(Also BTW, if I ever get around to doing my Web 2.0 podcast, I want to be sure to interview the producers behind “Rate My Space” and Paul Douglas. And John Cluberson and Roy Blunt and Tim Ryan. And Arianna Huffington and John Cusack.)
One Comment
John sums up telepresence from a network perspective, “Telepresence is an interactive real- time application, which means it is delay sensitive, loss sensitive and jitter sensitive. This sounds familiar: it is just like VoIP, with the one difference being that it has huge bandwidth requirements.” It’s that last part that makes things more difficult. No form of QoS can allocate bandwidth that doesn’t exist and it doesn’t have provisions to force the application to downscale the experience based on realtime metrics. …