High Signal Podcasts Evidence ledger
Method
Browse
← Back to evidence

Evidence receipt / commitment

Published · transcript-backed

Inbal Shani: commitment

1 Dec 2023 Lenny's Podcast The future of AI in software development | Inbal Shani (CPO of GitHub)

“When we started thinking about AI, it was with the idea to make developers much more productive.”

— Inbal Shani

Source trail

Everything needed to verify it.

Speaker
Inbal Shani
Attribution
Verified speaker
Claim type
commitment
Recorded
1 Dec 2023
Publisher
Lenny's Podcast

Transcript context

…Is there an example of that that comes to mind of someone that did that incorrectly or wasted a lot of time? It's not necessarily examples, but I've been talking to some of our customers and they're coming to us. "We heard about AI. What do you think we should do with AI? And how should we adopt AI? And can we learn from your experience?" And I'm sharing our experience. When we started thinking about AI, it was with the idea to make developers much more productive. And what are some of the things that we've seen? That developers have multiple tasks on them and they don't have enough time to spend on coding. So how can we give them time to spend more on coding and what are some of the coding element that we can automate? And from that comes the need to, okay, let's incorporate OpenAI, let's incorporate ChatGPT, let's connect all of them to help create that tool that helps developer be more productive and is AI based. So I'm sharing how we went through that journey to think about how to use AI. I see a lot of the times light bulbs with the customers like, "Oh, we didn't think about it like that." It's more about we wanted to plaster AI on a lot of things versus I have this workflow and it requires a lot of manual work, or it requires a lot of configuration. Maybe I can think how to incorporate AI into that and really shorten the time or make it seamless or make it less friction for developers to adopt that tool and so on and so forth. So it's really sharing more how we are thinking about it and helping our customers to understand the same. Along the same lines, you're talking about how you think about it with your teams. It feels like your product teams are probably living in the future of how other product teams will operate because you have access to stuff everyone else doesn't necessarily have access to. They probably adopt these tools a lot faster than the other teams would. What are some ways that your product teams operate that other teams may not yet be operating?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.

Search evidence