High Density #2: Tim Bajarin

High Density is an interview show where we try to articulate what it means to be great. My guests offer observations and insights into the transformation of business and society through technology.

Episode 2: Tim Bajarin

Tim recalls the beginning, middle and end of the PC industry and we discuss the causes of each.

via 5by5 | High Density #2: Tim Bajarin.

  • The depth of insight Tim shared made this episode into a significant building block for what may come next. On the other hand, the interaction itself was rather awkward, as questions and answers could flow much more seamlessly. There were severe issues with Tim’s audio cutting off, which disrupted that flow. It’s conceivable that the issue was only in the file I downloaded but, even though, some of the back and forth was characterized by disruption (“I’m sorry, what?”). If there are communication issues, acknowledging them is very useful, as we route around them.
    A conversation can flow so organically that the end result far surpasses what either party had in mine. Bajarin and Dediu could have done this.

    • David Nichols

      I also had some issues with the audio cutting out – luckily I was interested enough in what Tim was saying that I kept listening. But I found myself counting “1.. 2.. 3…” on the pauses.

  • Tatil_S

    Do you edit your podcast? That is my problem with most tech podcasts. None of the hosts or guests would dream of publishing blog posts without any editing to fix typos, eliminate run-on sentences, clarify some thoughts or moving paragraphs for better logical flow, yet they don’t mind just putting it out there when the medium is aural. Umms and ahhs, guests losing their train of thought, inside jokes, random muttering while looking for that book to read an excerpt… Just think about all the editing that takes place while writing one sentence even if you don’t re-visit that sentence at all later on.

    Editing a podcast is more difficult than editing written material and it definitely is time consuming for the host, but no editing wastes the time of the listeners. Hopefully, there are more of them than the host/guest combo, so editing saves more time overall. [Just in case somebody needs a *mathematical* justification. 🙂 ]

    Anyways, sorry for the rant…

  • Mark Shorten

    Horace interesting show as ever but you should change the intro and wrap up pieces. You are speaking very slowly and it sounds painful. Stick to your natural voice which is pleasing to my ear, I hope you have not being taking advice advice from a voice coach.

    • Klasse

      I can second that. To me it sounded like you got stephen hawking to do the outro… nothing wrong with him, but its a werid contrast to your natural voice. Also I am hoping for less of the audio issues. I bet you can find someone voluntary to remove the blanks from the track if you can’t find time for that.

  • David Stevenson

    There is one important fact about Jobs’ “mellowing” as a CEO between the first and second stint at Apple: he was a (biological) father with a family the second time, so he’d have had up-front-and-too-close-personal experience with “change the world” and “legacy” experience (and Pixar was just a lot more of the same learning experience, only dealing with “creatives” and “one-hit-at-a-time” philosophy, which is not so much unlike child-rearing).

    I cannot overemphasize this enough. I’m a gay man, so I have a few dozen relationships and one-night-stands with men, and I can say that (small sample size, but I am fairly selective in the sampling) there is a very pronounced shifting towards “mellowness” in interpersonal interface and in “legacy” type issues with the biological fathers, especially with those that maintain/regain relationships with their offspring.

    I think you need to contrast this with the young bucks who were working at Apple back when Steve was there the first time (and when I worked there during the Scully era, and who work there today, apparently) who “want to change the world” through new products/technology and “working eighty hours a week and loving it”. For these people their “children” are their jobs, and as engineers their priorities and evaluation criteria can be “engineering/scientific” rather than “parenting/organic”.

    I’m not saying that one has to be a biological parent to experience this shift from engineering to organic (although I think that it helps), since I myself am not, yet have come to recognize the difference (and I hope to have incorporated the distinction in how I deal with managing people: I’ve been on both sides of the divide in actual practice, and I can say that the later is definitely more productive than the former).