This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Products and Tools

Radio 8

I’ve been playing with Radio 8 and so far I like it. The news aggregator part of it is better than it was in the past. With previous versions, I seemed to lose news on occasion, but with 8, things appear to be fine.

Radio is now more focused on weblogging than it was before. A Radio license includes hosting space for your blog, and the blogging tools are now more sophisticated. But here’s my problem with the Radio way of blogging. I have to blog from this machine. I want to blog to my own server from my laptop, my desktop, and my office and I can’t easily do that with Radio’s desktop-based system.

Scoble points out that he hates a centralized service for publishing. He wants to have everything local and publish to the server. Personally, I want a Web service for my blog. I want to have a Web interface that I can use from anywhere to edit and publish my stories. I also want a more feature-rich editor that I can use whether I’m online or offline. The editor should be something I install on the machines I use the most, and I should be able to seamlessly publish from any of them without worrying that the other machines will be out of sync. If the data is centrally stored then there’s no synchronization needed.

I use Blogger to manage this blog. The data is all stored on Blogger’s servers and then published by FTP to my servers. And I use blogBuddy as a desktop client for much of my editing.

What I would really like to do is use Radio as my desktop client and publish to my site through Blogger’s XML-RPC interface. There’s a simple example of how to connect Radio to Blogger, but it doesn’t use the Radio browser interface, which is the reason I want to use Radio in the first place.

Radio is based on Frontier’s powerful scripting language. You can write macros to make Radio do many things. So what I would like to do is wire the Radio blog editing interface to Blogger over XML-RPC. It shouldn’t be that hard except for one thing. Where’s the developer documentation? I could worm though all the code that builds the Radio interface and figure it out, but it would still be nice to have some docs so that I don’t have to. Dave, are you listening?

Update: It appears that Dave is listening. I’ve already seen those tutorials, but they don’t really get into managing the existing Radio content management system. I’ve been digging into the scripts taht power Radio and I have a few ideas, but I’d still like to see Userland document the thing. After all they are trying to encourage people to develop things for Radio.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading