Flack wrote:Here's my review of the show from a listener's perspective.
The show begins with 18 1/2 minutes of Skype troubleshooting and Ben getting upset at people for dialing in.
It could be worse, it could be 18 1/2 minutes of dead air. That first time it happened that 18 1/2 minute gap became very famous.
Lest anyone forget, and it's on the tape of the "secret test" with me and Jonsey (and sorry I kept calling you "John-say" instead of "Jones-ay", it's how I thought it was pronounced), where Don specifically invited me to call in at the original time the show started, 11pm EDT, and requested me to do so.
Flack wrote:If it were me, I would cut the first 20 minutes off the show and post them separately. I can't imagine the average listener getting through that part and making it to the show.
I agree, technical glitches of more than say 30 seconds should be deleted. Less than that, they can be funny.
Flack wrote:People's voices sound ok at 96k. Music sounds terrible at 96k. From 18:30 for almost 4 minutes we hear a scratchy song that nobody knows and is not named. (Correction: the song and artist are named at 65 minutes into the show.) At around 22:30 the Rush into kicks in. It sounds great.
On the mic, Ben sounds very natural. He sounds like he's been doing this for a long time.
Absolutely, he sounds better on audio than I do. I sound terrible.
[ PORTION DELETED ]
Flack wrote:Overall I thought it was a good first effort. I think a little bit of streamlining it will get better.
I think he did great. I have a suggestion on something he can do to make things better and I have a story about why I think the suggestion works.
At one place I had a job where we were moving everyone from Windows 3.1 to Windows 95. It was my job to copy the system image onto each machine which had all the standard software that everyone was issued, which was not the same as the image on the machine, so I had to wipe it and install the replacement image. Then, for a specific user, I had to install any custom software they had, log into the particular Novell server with their user name and password so it would be automatically set, set their CC:MAIL address, and other things.
I knew how to do it, and after I'd done it about ten times, I created a checklist. Which helped because at one point I was sometimes doing two and three machines a day. (Feeding diskettes can be done on several machines). So I would go down the checklist I created, and when I ran out of items it went to the other guy in the office, John, who, while the person was out getting training on Windows 95 and away from their desk, would remove the user's computer from their desk, copy the local files and such off their computer onto the network, would take the computer I'd set up for them, copy the user's files back from the server, then return the new machine in place of their old one, hook it up and when the person came back from training, they had a brand new Windows 95 machine with all the settings exactly as they had left their original machine. He'd put their old computer in storage for two weeks in case someone noticed a file was missing, before wiping the hard drive.
The result was that John and I installed 65 machines perfectly, and exactly one came back because the customer messed up the settings on it after we delivered it. Not one had an error in anything we did.
The other team with two guys, in the same period of time, installed 5 machines and every single one they did came back because something was wrong.
So the motto of this story was, by using a checklist I never missed anything.
So, given the above story, I seriously recommend that you create a checklist or a script, and stick to it. Give potential time limits and if you're running over on something else so that something on the checklist might not get done, cut whatever is happening right then and there so you can get it all done.