Evidence receipt / belief
Published · transcript-backedSpeaker unverified: belief
19 Dec 2019 Acquired Convoy (with CEO Dan Lewis)
“I think autonomous is coming for a bunch of reasons that have a lot to do with all of the things that happened besides the driving, so stuff being loaded, secured, confirmed, locked, dealing with different people along the way.”
— Speaker unverified
Source trail
Everything needed to verify it.
- Speaker
- Speaker unverified
- Attribution
- Not verified from this transcript
- Claim type
- belief
- Recorded
- 19 Dec 2019
- Publisher
- Acquired
- Episode
- Convoy (with CEO Dan Lewis)
Transcript context
…Yes, CTFU versus building new features. We do think about that. At this point in our scale, we have teams that are dedicated to thinking about tools for developers so they can more efficiently build. Effectively, if you can create the right infrastructure, give developers better tools, and make them more efficient, then they can do it properly in the same amount of time, or they have the right kind of architecture to work on. It has become part of the culture. It's about hiring the right leader. Effectively, you have to have someone who cares about that, who is going to think about that, and prioritize it. We have a really solid engineering leader and a solid engineering team who have built multiple things in the past and who have gone through the experience of infrastructure that wasn't developed correctly. It's just through experience of having lived through that. I've seen systems fail or seen things fail or seen the debt built up. I’ve been in the situations you've been describing and live through multiple cycles of that. To have a good instinct just when you need to apply more investment versus less. It's hard to quantify. There's some ways you can try to quantify, but ultimately it takes experience and judgment around to see what's happening and know when to apply it and when not to. We have a system to be more effective in doing that and then we have different stages. We now look at it and say, "Okay. This is a new thing that's going to be at this scale." We'll do it quickly, and then there's a process for it becoming more production-ready. First of all, thank you so much for coming. As an UDub student here, it's incredible to have opportunities like this come so close to home. On to my question, we hear a lot about autonomous trucking were highways and long distances seemed like the ultimate opportunity for automated driving. Where do you think Convoy plays into this future where a lot of the carriers are automated? nomous trucking were highways and long distances seemed like the ultimate opportunity for automated driving. Where do you think Convoy plays into this future where a lot of the carriers are automated? I think autonomous is coming for a bunch of reasons that have a lot to do with all of the things that happened besides the driving, so stuff being loaded, secured, confirmed, locked, dealing with different people along the way. The truck driver will still be in the truck from a very long time even if the truck is effectively driving itself? What'll ultimately happen is it'll take years for the fleet to be turned over, I think. You'll have mixed fleets. You'll have trucking companies that have some trucks that are autonomous and some that aren't. You'll have different regulations and different rules for different conditions under which they can drive in different parts of the country, maybe at different times. That complexity makes it even harder for a person without computers and without technology to optimize that system. Now you're considering even more variables. At least today, every single full truckload that's running on the highway, the driver can run 11 hours a day. That's going to change. The hours of service will change, rules will change. That's going to benefit us dramatically. It will get harder before it gets easier. On the other side of this transition, that transition will be messy, and will be in a greta position to represent that in our technology, in our data, then make optimal decisions that we can teach our technology and our [...]. Hi. I'm [...]. I'm a software engineer. Probably one question I had is that you've talked a bit about how as a product manager, you had to understand how software engineers think. Maybe there are some lessons in reverse. What you wish software engineers understood about product managers and how they think? That's a good question.…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.