Because it’s been in the news – and not just for our current administration; this comes up a lot – I thought I’d look at the Justice Department, and comment on its “independence.” This came up in a recent conversation with a British friend of mine, who drew some interesting parallels I hadn’t realized. Anyway…

Picked up one of these three-in-one Qi chargers (I got it from Amazon, but it doesn’t appear to be listed anymore) and couldn’t be happier with it. If you’re embedded in the Apple ecosystem, it’s perfect:

OK… so, I’m wondering if there’s room in the world for some kind of monthly “IT BYOB” video chat. I’m going to state some of my assumptions; you can like/dislike to let me know if I’m on-base or off-base. Here we go:

I love little more than Armchair Imagineering. And although I recognize how freaking busy WDI is these days, and how much capital Disney is sinking into their parks worldwide… I have needs.

On the heels of yesterday’s lament about why writing tech books is so hard, I thought I’d lay out the typical process that an author has to go through to get a book published. Now mind, this is kind of an “archetype” process; I’ve worked with a half-dozen publishers in my career, and they all have slight variations on this.

I’ve written a couple of dozen traditionally published IT books. I’m super-proud of like four of them. If you’re considering setting out to write a traditionally published book, know that it’s hard. Here’s why.

I’ve decided to embark on what will doubtless be a months-long project: a book that covers the history of PowerShell, from its earliest inception to the shell we all know and use today. But I want to do more than just document the dry facts: I want to capture the impact.