Categories
Programming What I’m Up To

Fix the ChromeDriver 103 bug with ChromeDriver 104

The ChromeDriver 103 bug

If you had an application or script that uses Selenium and ChromeDriver to control or automate instances of Chrome or Chromium, it’s probably not working right now. Instead, you’re probably seeing error messages that look like this:

Message: unknown error: cannot determine loading status
from unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)
Stacktrace:
0   chromedriver                        0x000000010fb6f079 chromedriver + 4444281
1   chromedriver                        0x000000010fafb403 chromedriver + 3970051
2   chromedriver                        0x000000010f796038 chromedriver + 409656

...and on it goes...

The culprit is ChromeDriver 103, and I wrote about it a couple of days ago in a post titled Why your Selenium / ChromeDriver / Chrome setup stopped working.

ChromeDriver 103 — or more accurately, ChromeDriver 103.0.5060.53 — works specifically with Chrome/Chromium 103.0.5060.53. If you regularly update Chrome or Chromium and use ChromeDriverManager to keep ChromeDriver’s version in sync with the browser, you’ve probably updated to ChromeDriver 103.0.5060.53, which has a causes commands to ChromeDriver to sometimes fail.

The fix

Luckily, the bug has been fixed in ChromeDriver 104, which works specifically with Chrome 104. This means that if you update to Chrome and ChromeDriver 104, your Selenium / ChromeDriver / Chrome setup will work again.

The challenge is that Chrome 104 is still in beta. As I’m writing this, the Google Chrome Beta site is hosting an installer for Chrome 104, or more accurately, Chrome 104.0.5112.20. The application has the name Google Chrome Beta and is considered a separate app from Google Chrome. This means that you can have the current release and the beta version installed on your machine at the same time.

Once you’ve installed Chrome Beta, you just need to make your Selenium/ChromeDriver application or script use the appropriate version of ChromeDriver. Here’s how I did it in Transmogrifier, my Python script that helps me assemble the Tampa Bay Tech Events list:

from selenium import webdriver
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.chrome.service import Service
from webdriver_manager.chrome import ChromeDriverManager


// 1
option = Options()
option.binary_location='/Applications/Google Chrome Beta.app/Contents/MacOS/Google Chrome Beta'

// 2
driver = webdriver.Chrome(service=Service(ChromeDriverManager(version='104.0.5112.20').install()), options=option)

Here are some explanation that match the number comments in the code above:

  1. These lines create an instance of the Options class, which we’re using to specify the directory where the Chrome beta app can be found. We’ll use the instance, options, when we create driver, the object that controls the Chrome beta app.
  2. This constructor creates a WebDriver.Chrome object which will control the Chrome beta app. The service parameter specifies that the driver should be an instance of ChromeDriver 104, and that it should be installed if it isn’t already present on the system. The options parameter specifies that ChromeDriver should drive the version of Chrome located at the directory path specified in the option object: the Chrome beta app.

Once that’s done, I can proceed with my script. Here’s a simplified version of the start of my Transmogrifier script:

from bs4 import BeautifulSoup

// Load the web page whose URL is `url` into
// the browser under script control
driver.get(url)

// Execute any scripts on the page so that
// we can scrape the final rendered version
html = driver.execute_script('return document.body.innerHTML')

// And now it’s time to scrape!
soup = BeautifulSoup(html, 'html.parser')
// ...the rest of the code goes here...

Hope this helps!

Categories
Entrepreneur Florida How To Podcasts What I’m Up To

Everything you need to know to win StartupBus is in this podcast, part 5

The title of this post should be a big hint: Everything you need to know in order to win StartupBus North America 2022 is contained within a podcast. This is the third in a series of posts covering the “Startup Bus” series of episodes from Gimlet Media’s Startup podcast, which covered the New York bus’ journey during StartupBus 2017.

Did you miss the first four articles in this series? Here they are:

I’m posting this series as a prelude to StartupBus 2022, which takes place at the end of July. I was a contestant — a buspreneur — on the Florida bus in 2019, which made it all the way to the finals and finished as a runner-up. Now I’m a coach — a conductor — on the 2022 edition.

Here’s episode 5 of the podcast series…

…and here are the lessons I took away from this episode:

  • A lot of what makes success is just showing up. At the start of the episode, podcast host Eric goes for an early morning walk with Colleen Lavin of team Daisy and discovers that she was nce the Illinois Knights of Columbus free throw champion for girls age 14. Here’s how she tells the story:

COLLEEN: I was like getting my school volunteer hours, helping my dad at the free throw contest, and I was in the right age range, so he made me compete. I made two baskets, because I was not a basketball player. But no other girls in my age range showed up, and he made me go to the next competition and no other girls my age range showed up. Finally, I was almost sent to D.C to compete in the nationals after making a total of like four baskets.

ERIC: Because nobody had showed up?

COLLEEN: In my age competition!

  • Be prepared for possible twists in the finals. Elias Bizannes, the creator of StartupBus, loves drama. In the 2017 competition, even though there were five finalists, Elias decided to create a sixth team made up of people from teams who didn’t make it into the finals. The team would create a blockchain-powered voting app. Why did he do it? In his own words…

To mess with people to be honest. Because that’s what we do with StartupBus, we push them and we break them. And what happens is this remarkable thing comes out when people go beyond the limits they think they can, they actually step up. And so by introducing a new team, it was gonna add another level of competitive threat to the finals.

  • The finals will feature far more polished pitches and apps: “From the moment the pitches begin, it’s apparent. This is a very different level of competition than yesterday. The presentations are all well-crafted. Each of the products makes sense. You could imagine people making these pitches to actual investors.”
Categories
Entrepreneur Florida How To Podcasts What I’m Up To

Everything you need to know to win StartupBus is in this podcast, part 4

The title of this post should be a big hint: Everything you need to know in order to win StartupBus North America 2022 is contained within a podcast. This is the third in a series of posts covering the “Startup Bus” series of episodes from Gimlet Media’s Startup podcast, which covered the New York bus’ journey during StartupBus 2017.

(Did you miss the first three articles in this series? Here’s part onehere’s part two, and here’s part three.)

I’m posting this series as a prelude to StartupBus 2022, which takes place at the end of July. I was a contestant — a buspreneur — on the Florida bus in 2019, which made it all the way to the finals and finished as a runner-up. Now I’m a coach — a conductor — on the 2022 edition.

Here’s episode 4 of the podcast series…

…and here are the lessons I took away from this episode:

  • If you can find teammates that are on your wavelength, you can achieve a lot. Although they’re on the Florida StartupBus and not the bus that the podcast is covering, they remain a source of fascination for Eric, the host. Not only do Robert Blacklidge and Trey Steinhoff get along so well, but they also work so well together, and the synergy will take them far together. (Full disclosure: I worked with Trey at Lilypad, and can vouch for the fact that he is a great teammate. I also know Robert and can understand why he and Trey got along so well.)
  • A conflict within the team doesn’t have to destroy the team; in fact, not only can conflicts be resolved, but they can even strengthen a team. Ash from the Denari team had rubbed many of his teammates the wrong way, and there was talk of kicking him off the team. Things have turned around in this episode: everyone’s getting along, and Ash is considerably less acerbic — even optimistic-sounding.
  • The StartupBus format borrows some of its ideas from reality TV game shows, which means that there can be intentional confusion. “The teams have been getting different information about the competition all day. They’re hearing conflicting things about timing, about whether or not pitch decks are allowed. And this confusion, it all feels weirdly intentional.”
  • StartupBus is supposed to be a challenge. It’s not supposed to be easy, and as anyone who’s done it before will tell you, it can be gruelling at times. And that’s a good thing — if StartupBus works as designed, you shouldn’t be exactly the same person at the end of the ride. As one of the Denari people puts it: “This is a Navy SEAL training program for startups. This is like we’re going to push you to that to the limit of your mental strength, like every single person on their team is that like living in a role that’s very different from what they walked on the bus wanting to do.”
  • Speaking about come out of StartupBus a little different, you can see some of the buspreneurs’ change — they’re more certain, more directed, more convinced of their ability to change their personal course through life.
  • You can most definitely incorporate singing and music in your pitch. The pitch for singing telegram startup Yeti featured one of their buspreneurs in a full Marilyn Monroe costume, singing Katy Perry’s Firework, but with StartupBus-specific lyrics. I also did that with the accordion at StartupBus 2019.
  • You can also use audience participation in your pitch. Tampa-based CourseAlign did that by asking the audience for a show of hands, using questions that would get a specific kind of result.
  • Be ready for tough questions. During the Q&A section of their pitch, Denari — the Blockchain-powered GoFundMe-like startup — is asked how they plan to prevent their system from being turned into a money-laundering platform.
  • Don’t be too hard on yourself. After getting that tough money-laundering question, Colleen Wong, who’s been leading Denari, felt bad about her answer and said that she didn’t feel that she was a good leader. Eric the host had to reminder her that she did the near-impossible — “Are you kidding me?! Have you, like, seen yourself this week?! …You, like, pulled together the, like, craziest team on the bus. It was a great thing.”
  • Anything can happen in the judging room. Eric the host was invited into the judging room to record a reenactment of judges’ discussion as they tried to decide who would move the next round. But as they reenacted their discussion, they started changing their minds. The judging process can turn on a dime.
  • There is a downside to making it into the finals: It means that although you’re in a party town, you can’t party. You’re going to be working on your product and your pitch for the finals. Trust me on this one — I was in New Orleans, one of the best party towns in the country, and I spent Saturday night with my team working on our startup.

Categories
Programming What I’m Up To

Why your Selenium / ChromeDriver / Chrome setup stopped working


Update: You’ll also want to see this follow-up article — Fix the ChromeDriver 103 bug with ChromeDriver 104.


If you run applications or scripts that use Selenium to control instances of Chrome via ChromeDriver, you may find that they no longer work, and instead provide you with error messages that look like this:

Message: unknown error: cannot determine loading status
from unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)
Stacktrace:
0   chromedriver                        0x000000010fb6f079 chromedriver + 4444281
1   chromedriver                        0x000000010fafb403 chromedriver + 3970051
2   chromedriver                        0x000000010f796038 chromedriver + 409656
3   chromedriver                        0x000000010f7833c8 chromedriver + 332744
4   chromedriver                        0x000000010f782ac7 chromedriver + 330439
5   chromedriver                        0x000000010f782047 chromedriver + 327751
6   chromedriver                        0x000000010f780f16 chromedriver + 323350
7   chromedriver                        0x000000010f78144c chromedriver + 324684
8   chromedriver                        0x000000010f78e3bf chromedriver + 377791
9   chromedriver                        0x000000010f78ef22 chromedriver + 380706
10  chromedriver                        0x000000010f79d5b3 chromedriver + 439731
11  chromedriver                        0x000000010f7a147a chromedriver + 455802
12  chromedriver                        0x000000010f78177e chromedriver + 325502
13  chromedriver                        0x000000010f79d1fa chromedriver + 438778
14  chromedriver                        0x000000010f7fc62d chromedriver + 828973
15  chromedriver                        0x000000010f7e9683 chromedriver + 751235
16  chromedriver                        0x000000010f7bfa45 chromedriver + 580165
17  chromedriver                        0x000000010f7c0a95 chromedriver + 584341
18  chromedriver                        0x000000010fb4055d chromedriver + 4253021
19  chromedriver                        0x000000010fb453a1 chromedriver + 4273057
20  chromedriver                        0x000000010fb4a16f chromedriver + 4292975
21  chromedriver                        0x000000010fb45dea chromedriver + 4275690
22  chromedriver                        0x000000010fb1f54f chromedriver + 4117839
23  chromedriver                        0x000000010fb5fed8 chromedriver + 4382424
24  chromedriver                        0x000000010fb6005f chromedriver + 4382815
25  chromedriver                        0x000000010fb768d5 chromedriver + 4475093
26  libsystem_pthread.dylib             0x00007ff81931a4e1 _pthread_start + 125
27  libsystem_pthread.dylib             0x00007ff819315f6b thread_start + 15

It turns out that there’s a bug in version 103 of ChromeDriver, which works specifically with version 103 of Chrome. This bug causes commands to ChromeDriver, such as its get() method, which points the browser to a specific URL, to sometimes fail.

The quick solution

While this bug exists, the best workaround — and one that I’m using at the moment — is to do the following:

  1. Uninstall version 103 of Chrome.
  2. Install version 102 of Chrome.
  3. Install version 102 of ChromeDriver.
  4. Disable Chrome’s auto-update and don’t update Chrome.

How I encountered the bug

This happened to me on Wednesday. Earlier that day, I saw the “Update” button on Chrome change from green to yellow…

…and my conditioned-by-security-training response was to click it, updating Chrome to version 103.

Later that evening, I started assembling the weekly list of tech, entrepreneur, and nerd events for the Tampa Bay area. You know, this one:

When I started putting this list together back in early 2017, I did so manually by doing a lot of copying and pasting from Meetup and EventBrite pages. However, as the tech scene in Tampa grew, what used to be an hour’s work on a Saturday afternoon starting growing to consume more and more of that afternoon. I’d watch entire feature-length films in the background while I put them together. It became clear to me that it was time to add some automation to the process.

These days, I put together the list with the help of “The Transmogrifier,” my name for a collection of Python scripts inside a Jupyter Notebook. Given a set of URLs for Meetup and Eventbrite pages, it scrapes their pages for the following information:

  • The name of the group organizing the event
  • The name of the event
  • The time of the event

In the beginning, scraping Meetup was simply a matter of having Python make a GET request to a Meetup page, and then use BeautifulSoup to scrape its contents. But Meetup is a jealous and angry site, and they really, really, really hate scraping. So they employ all manner of countermeasures, and I have accepted the fact that as long as I put together the Tampa Bay Tech Events list, I will continually be playing a “move / counter-move” game with them.

One of Meetup’s more recent tricks was to serve an intermediate page that would not be complete until some JavaScript within that page executed within the browser upon loading. This means that the web page isn’t complete until you load the page into a browser, and only a browser. GETting the page programmatically won’t execute the page’s JavaScript.

Luckily, I’d heard of this trick before, and decided that I could use Selenium and ChromeDriver so that the Transmogrifier would take control of a Chrome instance, use it to download Meetup pages — which would then execute their JavaScript to create the final page. Once that was done, the Transmogrifier could then read the HTML of that final page via the browser under its control, which it could scrape.

Creating an instance of Chrome that would be under the Transmogrifier’s control is easy:

# Python

from selenium import webdriver
from selenium.webdriver.chrome.service import Service
from webdriver_manager.chrome import ChromeDriverManager

driver = webdriver.Chrome(service=Service(ChromeDriverManager().install()))

The single line of code after all the import statements does the following:

  • It launches an instance of Chrome that can be programmatically controlled.
  • It has ChromeDriver check to see if it is compatible with the Chrome instance. If not, it installs the compatible version of ChromeDriver.

This is where my problem began. ChromeDrive saw that I’d updated to Chrome 103, so it updated itself to version 103.

Here’s the code where the bug became apparent:

print(f"Processing Meetup URL: {url}")
driver.get(url)

About one time out of three, this code would do what it was supposed to: print a message to the console, and then make Chrome load the page at the given URL.

But two out of three times, it would end up with this error:

Message: unknown error: cannot determine loading status
from unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)
Stacktrace:
0   chromedriver                        0x000000010fb6f079 chromedriver + 4444281
1   chromedriver                        0x000000010fafb403 chromedriver + 3970051
2   chromedriver                        0x000000010f796038 chromedriver + 409656

(...and the stacktrace goes on from here...)

This happens when executing several driver.get(url) calls in a row, which is what the Transmogrifier does. It’s executing driver.get(url) for many URLs in rapid succession. When this happens, there are many times when Chrome is processing a new ChromeDriver command request after a previous ChromeDriver session (a previous web page fetch) has already concluded and detached. In this case, Chrome responds with a “session not found” error. ChromeDriver gets this error while waiting for another valid command to complete, causing that command to fail. (You can find out more here.)

In the end, my solution was to downgrade to Chrome 102, use ChromeDriver 102, and keep an eye open for Chrome/ChromeDriver updates.

Categories
Business Career Podcasts Programming What I’m Up To

Talking about personal agility and the Great Resignation on the “Arguing Agile” podcast

You should be a regular listener/viewer of the Arguing Agile podcast, a YouTube show hosted by Tampa Bay techies Brian Orlando and Om Patel that features local techies talking about software development, agility, and everything in between, completely unscripted and unrehearsed — just real conversations about real tech work. In the past year, they’ve published 66 episodes, the latest of which features…me!

In this episode, titled Personal Agility and the Great Resignation, we talk about doing work in the brave new world of post-2020 and discuss things such as:

  • 0:00 Intro
  • 0:24 Topic Intro
  • 0:59 Reasons for In-Person Gathering
    • Working remotely still requires some in-person gathering, because as they saying goes, sometimes, “you have to be there.”
  • 4:19 Team Bonding, Positive Vibes
    • The power of team-building ceremonies and exercises, and why they have to be meaningful and not just “doing team stuff for team stuff’s sake.”
    • In the past couple of months, I’ve had my first chances to meet with my team at Auth0 (Developer Marketing) after working with them for a year and a half — first at a small summit in Salt Lake City, and last week in London.
  • 8:40 Work, Life, & Sustainability
    • Earlier in your life, it’s much easier to work ultra-hard in the quest to advance your career, but you can’t do it for an extended period. This is the exact thing that generates mid-life crises, and physical and mental health issues.
    • Brian: “Jack Welch said a lot of stuff.”
  • 15:50 Interviews: Vetting Companies
    • During a job interview, you shouldn’t be the only one being interviewed. You should also be interviewing them!
    • How can you tell if a manager is a “Rick” looking for another “Morty” to add to his “Morty Army?”
    • I talk about a Chris Voss technique where you look at the reactions on the face of the person who isn’t speaking to get the truth.
  • 19:55 Segue on Microsoft
    • We talk about my time at Microsoft where I was a Windows Phone Champion, Albert Shum’s design for its “Metro” UI, and Microsoft’s thinking during the Ballmer era: “The mobile platform is the desktop platform, but lamer.
    • I was at a gathering of P2P people at Microsoft in 2001 that was attended by Tim O’Reilly and Dave Winer, where we were told that “IE6 will be the last browser, because the future is applets.
    • A story from my time at Cory Doctorow’s startup where how I show how hard it is to predict the future.
  • 25:51 Learning
    • A story from how I landed my job at Auth0, where I had to learn about an unfamiliar platform very quickly.
    • The importance of communication when working remotely and keeping Conway’s Law in mind.
    • Strip away the technology, and a teacher from hundreds of years ago would still recognize a present-day classroom and the lecture format.
    • We share stories about learning by doing, with Om talking about his daughter at med school and me talking about a story about the Logo programming language, where children learned beyond what they were being taught.
  • 31:12 Time to Think
  • 37:34 Evolution of Technology & Skills
    • Our first computers: I had an Apple //e and Om had a Spectrum ZX, two serious Generation X machines.
    • I learned how to program at a computer store that tolerated my hanging out: Batteries Included, in Toronto.
    • Learning new languages: Python and Lingo, and picking up new languages to get the job done. This may be the first time on the podcast series where the languages Lisp and Prolog get mentioned.
    • A question that Brian asks during interviews: “Tell me about a time in the last 18 months where you did something to update your skills.”
  • 44:55 Solving Problems
    • Software isn’t a what, it’s a how. If you make software for an industry or field, you’re not in the software industry, but the industry or field that you’re making the software for.
  • 47:51 Personal Agility
    • Between the pandemic and the current economic situation, you need to develop personal agility to survive and thrive in the current job market.
    • A number of people who participated in the Great Resignation left their jobs without having another job to jump to.
    • About not participating in what Scott Galloway calls “the menace economy”: “I want to earn fair profit for my effort, but I don’t want to do it by stepping on somebody’s neck.”
  • 53:24 Monkeys, a Banana, and a Ladder
    • When talking about organizational culture, you’ll eventually come across the “Five Monkeys Experiment,” which we discuss.
    • How office architecture mirrors office organization, culture, and hierarchy — and how remote work systems’ architecture will do the same.
    • The new generation of workers will probably have to be more adaptable than any previous generation.
  • 1:02:18 Returning to the Office
    • The majority of a developer’s day requires focus time, and that isn’t often achievable at the office.
    • The true hurdle may not be technology or office space, but organization discipline.
    • It’s quite possible to kill time unproductively at the office — we’ve all seen this.
    • “If you signed a ten-year [office space] lease in 2018, you’re probably really anxious to get people back in there.”
    • “Butts in office chairs” is the new “lines of code” metric.
  • 1:08:43 The Future
    • There’s so much traditional culture force behind the way work is done. Ebenezer Scrooge’s accounting office in A Christmas Carol isn’t all that different from its modern-day counterpart.
    • Om: “I like to see a sitcom called The Home Office.
  • 1:13:00 Wrap-Up
Categories
Entrepreneur Florida How To Podcasts What I’m Up To

Everything you need to know to win StartupBus is in this podcast, part 3

The title of this post should be a big hint: Everything you need to know in order to win StartupBus North America 2022 is contained within a podcast. This is the third in a series of posts covering the “Startup Bus” series of episodes from Gimlet Media’s Startup podcast, which covered the New York bus’ journey during StartupBus 2017.

(Did you miss the first two articles in this series? Here’s part one, and here’s part two.)

I’m posting this series as a prelude to StartupBus 2022, which takes place at the end of July. I was a contestant — a buspreneur — on the Florida bus in 2019, which made it all the way to the finals and finished as a runner-up. Now I’m a coach — a conductor — on the 2022 edition.

Here’s episode 3 of the podcast series…

…and here are the lessons I took away from this episode:

  • If you run into a difficult person in the morning, you ran into a difficult person. If you run into difficult people all day, you’re the difficult person. I don’t want to reduce Ash, one of the buspreneurs, to a single quality — difficult person — but his “hey, I’m just being real” approach to everyone and everything is one of the hallmarks of difficult person-ry. One of the challenges of being a difficult person is that people will work with you only if you provide value that outweighs your difficulty, and that’s not easy to accomplish. This episode gives us a deeper look at Ash. While he can be a difficult person, we get a better understanding of who he is. Which leads me to me to my next observation:
  • “The thing about StartupBus is that it really is like a reality TV show. It’s so intense that every interaction, every personality can feel like a caricature of real life.” In the previous episode, Eric the narrator observed that StartupBus feels a lot like one of those “reality TV” competition shows. In this episode, he takes the observation one step further by noting that in a high-pressure setup like StartupBus, it’s all too easy to reduce your busmates to the most obvious aspect of their personality. Remember that people are more than what you see on the surface.
  • Even though the company you’re creating on the bus isn’t “real,” it helps to get real users, and you either get them through your social network or through advertising. It’s more impressive to the judges at the finals when you can say “Even at this early stage, we already have x users for our product.” You may be working under a compressed timeline, but it’s still doable, and not only do users give you cred with the judges; users can also give you valuable feedback.
  • Pay attention to the details when you’re spending money. One of the teams paid for Facebook ads, but clicking on the ads took users to https://phishly.io when their site actually lived at plain old http://phishly.io. That was 65 dollars down the drain.
  • StartupBus may be the “wild card” that you need in your life. As Madelena Mak, one of the conductors on the bus says: “I think like lot of people who join the bus have that same feeling I felt, like that they want to be dealt a wildcard. That they want to be pushed to the limits so they can break out of their own old molds. Like they want to be something more than who they think they can be. It’s not about the bus. It’s about learning something about yourself.”
  • The pitching gets tougher. As the bus approaches the destination city — New Orleans in the case of StartupBus 2017, Austin in this year’s case — you’ll be pitching in front of judges who’ll ask questions that will require you to have thought through more angles. For example:
    • Team Daisy — the folks behind the funeral-planning app — were asked if they’d considered handling issues beyond just the funeral, such as death certificates.
    • Team Denari — the team with the app for sending cryptocurrency to people in need — got stuck on a question that exposed their blockchain-induced blindness. When they said that they could outdo GoFundMe because it services only 19 countries, one of the judges countered with “You are talking about now securities exchange over multiple countries. Maybe there are reasons GoFundMe only deals with 19. Which I haven’t heard you guys say. Is it cause they don’t want to? Because that’s kind of what it comes off as. It’s like, ‘GoFundMe is the largest one, they’re only in 19 countries.’ Why is that?”

Categories
Entrepreneur Florida How To Podcasts What I’m Up To

Everything you need to know to win StartupBus is in this podcast, part 2

ThinkInsideTheBus - StartupBus

As the title of this post puts it: Everything you need to know in order to win StartupBus North America 2022 is contained within a podcast. This is the second in a series of posts covering the “Startup Bus” series of episodes from Gimlet Media’s Startup podcast, which covered the New York bus’ journey during StartupBus 2017.

If you haven’t yet seen the previous post, check it out! It covers episode 1 of the Startup Bus series, which introduces you to the buspreneurs on the 2017 New York bus.

Episode 2: It’s like one of those competition TV shows!

You can listen to episode 2 on its page or use the player below:

Here are my notes from this episode:

  • Eric the narrator discovers the secret of StartupBus: it’s like a reality TV show, but in real life! “When I was growing up, my family was very into a particular kind of reality tv—competition shows… I thought I’d be reporting on a hackathon. I’d find one person, going through something interesting, and we’d just see how their week played out. Pretty simple. But when I woke up in a hotel in Raleigh, North Carolina that Tuesday morning, and I saw a giant “StartupBus” decal on the charter coach outside my window, I had this realization that would have thrilled my younger self to no end: “Holy shit. I’m not just reporting a story about a hackathon, I have landed inside a real life competition show.”

    The lesson you should take from Eric’s realization: if you think you wasted your time watching Survivor, The Amazing Race, or similar shows, guess what…you didn’t! A lot of the personal dynamics on those shows is pretty much like those on StartupBus.
  • Be prepared to pitch constantly. Eric observes: “To get the day started, each team sends one person to the front of the bus to practice their pitch over the intercom. This is something that happens a lot on StartupBus—people are practicing their pitches constantly.”
  • Be prepared for surprise challenges and surprise obstacles. StartupBus borrows a big trick from reality TV shows: surprise obstacles. When the bus pulls into Charlotte, North Carolina, the New York team finds out that they’ll be pitching against two other teams — a bus that started in Akron, Ohio and another that started in…Tampa!
  • Don’t limit yourself to just software, because there’s a chance that some team on another bus isn’t limiting itself to just software. “And the Ohio bus is impressive in its own way. It turns out they teamed up with some people from San Francisco, and they’re manufacturing physical products. So they have 3D printers and computer aided design software. The whole thing feels like that scene in “The Sandlot” when the other team shows up in their actual jerseys and matching converse sneakers, and all of a sudden you realize, ‘Oh… this is some real competition.’”
  • Try not to fall into the trap of traditional gender dynamics. On one team, there’s a good news/bad news thing going on because they’re electing one of the women to be CEO; the bad news is that it’s a job that none of them particularly want, and a lot of it will be about reining in unruly behavior.
  • Have a plan for managing conflict. On another team, a “that’s just who I am” kind of guy butts head against a woman on his team. This is a pretty big topic, and I’ll write more about it in a later post. Just know that you may have to manage conflict within the team.