Skip to main content

So this is what happens today when a network goes on strike

Those of you in the US, and those who really don't listen to government sponsored radio, may not be aware of this but our national broadcaster (CBC, similar to the UK's BBC) went on strike last week.

So Tod Maffin of ILoveRadio, who reported a number of items prior to the lockout (including a post that said "email is no more, oh so is my voice mail"), started CBC Unplugged.

The locked out workers have been doing podcasts, blogging and more. Even doing competing shows

Even the managers from within the locked out building are posting.

Some have suggested that this isn't the way to get people to appreciate them.

My brother, Keith, works for the CBC - at one time as a producer (even won some awards) and now I believe as a Manager. Haven't heard from him on this although he lives up in Yellowknife so who knows.

I'm not a big fan of strikes or lockouts but then I don't like unions to begin with. But what would be interesting would be if what Tod had talked about doing with CBC Unplugged actually came true.

Have a REAL online network - don't just gripe about your picket lines and blah, blah, blah. Show the world (and I guess your managers at the same time) that you love what you do so much that you are going to do it WHILE you're on the picket line and you're going to do it SO MUCH BETTER than the normal CBC could do it.

But enough anti-union spat, I think that it's very cool that if enough like-minded individuals wanted to get together and start a "network" for news, music, commentary anything - that they don't have to get the handouts from the government to do this. (CBC gets almost 1 BILLION dollars annually - maybe instead of looking for advertisers for the TheFoxShow, I should just go to the people who take all my money anyways)

Speaking of a "real network", I'm going to fire up the TechPodCast Network live feed. Why is this cool? Well, all 40+ members of the network upload their latest shows onto the Live Stream. As a result, you get the equivalent of "tech radio" - all day, all night.

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...