YouSaid · the spoken record

Inbal Shani

lines on the record
56
first
2023-12-01
most recent
2023-12-01
sittings or episodes
1
sources
podcast

Every line below is reproduced as it was said and linked to the record it came from. Nothing here is summarised or generated. Directory · Search · Corrections

  1. If you can share a similar experience or a story that you think will be helpful for me as I'm thinking about, what does that mean being chief product officer for GitHub? Any tips and tricks on how you use GitHub? So maybe I can learn or share your experience and story so I can learn from your experience as well.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  2. Lots of interesting sessions and talks from Universe. So if people want to learn more about what is it that we're doing, how we're thinking about AIs there, LinkedIn is likely the best social media platform to find me where I have a chance to talk to a lot of people. These are the best places.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  3. I think if you don't take risks, you cannot create a future. I forgot who said it. I think it's from one of the animation monkey Luffy, if I remember. But it basically summarized the life model that you have to take risks, you have to experiment. If you feel comfortable, it's not a good thing. You always need to feel uncomfortable to stretch yourself to go to the next thing. So that's something that I've done, you just heard about my career story from applied scientists to chief product officer of GitHub. Like, who knew?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  4. I think the first question that I really like to ask is what is the most innovative thing you have done and why do you think it's innovative? And it's really interesting that there are some people that think they need to answer about the biggest invention that they've done. And there are some people that are very vulnerable and they talk about something very personal that they have innovated. And it talks a lot. It shows a lot of their character. And I think the second question that I like to ask a lot is give me an example in a time where you had a disagreement with your manager, you're in the line with your manager. And then what did you do about it and how did you go? Because it showcased a lot about your character. And are you willing to stand your ground and push up when you need to? And then what is that communication skills that you have, your influential skill that you have?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  5. I like a lot of fantasy and I like a lot of history based movies and theories There is a recent one that came up on Netflix. All the lights we cannot see. Amazing. So well produced really tells an interesting part of the history of World War II.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  6. Failing forward by John Maxwell The Flywheel from Good to Great by Jim Collins, and a recent book that I read that is called Dare to Lead Like a Girl by Dahlia Feld

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  7. For me, it's an exciting moment in time. I've been celebrating my first year in GitHub and my first GitHub universe on stage last week. It was amazing experience for me to meet our customers, our partners and talk a lot about the importance of developer experience, REI Power platform, and how we're shaping the future. So I'm in a very exciting part of my journey with GitHub. You don't get here if you don't make some mistakes and you do some learnings and you have some successes and then you take the right turn and sometimes you take the wrong term, but you find your way to a place that makes you happy and feel fulfilled as a product leader.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  8. Right. It's very common because we are human beings. We think that if we're coming, we have our experience. We're coming to an EU space and you immediately see all the things that are not working or all the things that need to be fixed. If you're working in the same space for a long time in the same team, you often don't see these gaps anymore because you got used to living with them. So as someone you, you're coming in, you immediately see all these holes and cracks and it's like, okay, here's all the things I need to fix. But you have a team that has been there for a while. So how you find that bridge to communicate between the things you see and the things that they think is fine. Like why aren't driving these change? It's been working. Don't fix it.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  9. When I was leading the location-based services team. And I think for me, it was one, it was the first time I was working in an international company. So really figure out that my character not always fly with every culture that exists. So how am I adjusting to that? And the second thing is that they were very accustomed in working in a specific environment, in a specific way. Yes, I was hired to drive change. But one, the team doesn't have to accept that's your job to drive change. And also they're not necessarily on board with the fact that you're here to drive chain. So how you take them with you through that journey was a big learning. And being able to communicate in a general way. Way of communicating to drive clarity, that was a big learning.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  10. And I've seen that when I started doing that without building that understanding of why we need to do a change or why this is a problem that we need to go and fix it, then you don't take people with you through that journey. So really analyzing that not everyone appreciates change the way you are. Not everyone has that mindset of the Go-Go. Let's go do it. And really figuring out taking a step back and assessing what is happening so you can take the team with you on that journey of changing. That was for me the biggest learning and likely a lot of the not supportive feedback I got from the team at that time was what you're moving too fast. Slow down. Explain the why. Why are we doing that? How should we move forward?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  11. I'll call it the biggest learning because I'm not a believer in failure. I'm a believer in learning. And every time you fail, it's a big learning. And I prefer to look at that as opportunities. I think like biggest one was likely early on when I started being a leader and manager of a team. I'm a very go-go-go person. And I have a lot of energy. And when I'm coming to something and I see all the issues that need to be fixed, it's like, okay, let's take the toolbox out. Let's go fix everything. And that includes driving change.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  12. And learn from different people, but also looking up, looking across and looking down into the people that I manage and what are the things I could learn from them? What are some of the skills that they have that are not necessarily in my toolbox and how can I adopt them? What does success look like and what are some of the things that make people unhappy? And you don't necessarily want to have these tools in your toolbox. So it's a lot of what, yes, and what's no in a combination.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  13. System and all of that, and how is it eventually being displayed? So that requires me to think from the get-go on the bigger solution, not just my component. So I think that's one. The second thing is really thinking about the people and change management and how you take people with you. Because a product manager role is a very influential role. And a lot of the things you do is influencing other people. Although everyone thinks that as a product manager, you get to do things. You get to write papers. But you need to influence the engineering team to build a product that you want them to build. You need to influence the revenue team to go with a go-to market and sell the product the way you envision it. So there's a lot of influencing happening. You need to understand how to do that. And building that skill set as a product manager from the get-go is very critical. So for me, it was the fact that I was fortunate enough to do different roles in the industry.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  14. Combination It's never one thing because the role of the chief product officer is so broad. You're not just the head of products. And that's the mindset that is now evolving in the industries that a chief product officer is more than just the head of product. They need to have a business thinking. They need to understand their goal-to-market strategy. They need to understand the sales play. They need to understand how engineering or building products. It's not just about let me write a set of requirements or think about the vision and the futures, how all these components in the company are operating together to build that product. And some of that you learned from looking into the leaders that you work for and see how they're thinking. From my first box in the aerospace industry, I learned how to think system, not to think just on the problem that I'm solving right now, but how the problem that I'm in charge in solving that filter that I'm responsible in tuning is connected to their control system.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  15. The things that are now in Horizon 1. So I think in GitHub we found the right balance between having the right people, having the right mindset, but also creating that synergy between the future thinking to how we make it real. So we have a strong relationship, especially between the product team and GitHub Next, to make sure that these relationships are ongoing. ideas are flowing both ways.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  16. I think there are two elements for that. One is having the right people with the right mindset on the team, allowing them and giving them the bandwidth and freedom to innovate. And the second thing is that we're focusing on making things real. So we're not keeping them far or in disconnect from the product and engineering. There's a lot of synergy. There is a lot of discussion because what happens in teams that are not successful, at least from what I've seen, one, that the team is becoming basically an early university. They write papers, but I think it's coming out of that. So nothing finds its walls to production. So if you don't introduce that, how do we take it to production from day zero when you're thinking about a new idea? Then it's rarely that it will go through that hump cycle and itself in production. And the second thing that companies tend to use these teams is too much tactical. And here is that we need something in six months go invented right now. And then they're basically creating another engineering or producting to think about this.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  17. They're basically applied scientists, research scientists that are working together and they're really thinking about three, five years horizon. They're not thinking about the right now. They're thinking about what is the future for software development is going to look like. They have the writing papers, they're running experiments, they're doing POCs, their job is to invent the future. But again, it's really a synergy because they're talking to the product, to their engineering, so they're getting ideas from that. They're talking to customers or we're sharing feedback. So that's our GitHub next. It's basically our research team.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  18. You're losing that organic fork, that is humanity. Imagine that someone say you have 15 minutes a day to be creative. I don't think it's the poll. So it's encouraging that thinking more than structurally.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  19. Allocate a specific bandwidth? Can we do a POC? Do we do that in that team? Do we do it as a reteam? So we keep it flexible and we also have a research team, which are GitHub VNX that basically that's their day job is to think about the next big innovation. But in GitHub innovation is coming from everywhere it's coming from. Our field team that are talking to customers and are implementing different variations of GitHub for our customers and they'll come back with some feedback or an idea it's coming from the product team it's coming from the design team from the engineering team it comes from everywhere so if you try to structure innovation

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  20. It's a couple things. One, it spend time with customers and learn from your customers because a lot of the innovative ideas are coming basically from conversation with customers because they're sharing with you their frustration. They're sharing with you what they would like to have. They're sharing with you what will be an amazing invention for them. So that's the first thing is creating that mechanisms. And we spend a lot of time talking to our customers and also talking to our community. We're fortunate to be the home for all developers and home for all open source, large open source foundation and small open source foundation are running on top of GitHub. So that's another feedback cycle that we have to really gather those ideas and those asks to help us shape the future. And then the second thing is really about the team speeching idea is like I have this idea. I've been doing some research. Here is a paper that describes what is it that I want to do and then we figure out, okay, when can we fund it? How can we fund it?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  21. Have to create that bandwidth for the next generation, the next innovation. And if you didn't have a chance to see the two-day keynote in universe, I highly recommend because we basically shared our next vision for co-pilot with co-pilot workspace. We also had Satya Delan stage, and he was very excited. It's like, oh my God, GitHub, if you build that, this is amazing. So you see that we keep on putting this vision forward again and again, at least six months to a year before we even have something in the market because we're already thinking, we're already innovating, we're already on the next thing.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  22. It's a lot about that. It's a lot about creating that bandwidth for the team to innovate and experiment and carving that time out, but also being okay that not every experiment is going to be successful. So the sheep to learn or the fail forward, these are the philosophies that I believe in. If you don't try, if you don't experiment, you will never innovate. And if you don't fail, you will never learn from your mistakes. You'll never learn from your experience. So you will not progress forward. So really creating that ability to experiment, the same that we have done with Copilot or we've done in GitHub Advanced Security or even the way GitHub was created. It's all that innovative thinking that the teams have that are thinking about what is that next generation use case case? What is the future developer will need to be happy, to be more productive, to do their job in a world that software development is changing so fast?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  23. High safety regulation, all of that, being developed on the ChatGPT, you know, I might be wrong, but I think that eventually we will find ourselves in the world of hybrid models and multimodals where there will be several LLM models coming together because each one of them will have their own benefit. And then there's going to be a niche AI or a more configurable customized model for specific use cases. So that's my prediction of the future. But in 10 years from now, we'll all be smarter.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  24. I think we have pivoted very hard towards a generative AI and generalized AI can solve everything. I believe that the future is going back to scale back a bit to the niche AI. So we will live in a hybrid world where you still have specific AI models that are solving very specific problem, where the generative AI will have its limitation. You know, it's a general purpose tool. So it can be as good as the data sets, but it also tries to find some statistical recommendation of is it good, is it not good? So it's limited by the training set that it has, and it's trying to solve to be everything for everyone. There are going to be areas where you still need to train models. For example, I spend my time in the aerospace industry and the automotive industry. I don't see self-driving models that require so much delicate, specific models, tuning.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  25. I grew up in a world of Nishi where you have to be an expert and you need to be trained for years understanding how to tune a model, what is the right output, and you need to understand how to build a simulation to Terseid, how to induce data, focus on optimization. Seen the evolution of AI throughout the year with all the tacking devices and the conversational AI. And then it started as a single term. It came up as a multi-term. So I started seeing that trend of more democratizing AI, but I didn't expect that boom of generative AI. To you as AI. So for me, that was a ha moment like this is interesting. So, what's next?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  26. A little bit. No, I mainly playing with my older son. So he has more time to code, but sometimes I enjoy spending time with him and kind of brainstorming and talking about things and architecture. I think recently, a few months back, he did a project on sensors and sensors integration. And he came across Kanmon Filter, which was the thing that I used to do many years back. And he's like, okay, what is it? And how is it done? And then we went through that and I helped him kind of think about the structure and the sensors fusion and all of that. And then sometimes I'm like, okay, move aside. Here you go. This is how you.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  27. To delegate to a higher obstruction tool. And that's exactly the way I think about AI. You pick and choose how you want to use it. There is no global way that is the absolute truth that everyone has to follow. You need to think how you use your tools to do your job in a way that you're still keeping the things that make you happy. On the other hand, use AI to do the things that you less enjoy. Maybe you like writing functions, but you don't like writing testing. So generate unit testing and so on and let AI do its job for you and you still focus on the things you enjoy.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  28. And we have a scenario in mind how you should use them. But what we're seeing is developers are using them very differently. Everyone is choosing their own slaver on how to use the tools. There is no right and wrong way to use it. It's a tool. It's a language. When I was learning how to code, I used to code in C and then Java became a thing. I'm like, oh, but this is taking away my job because I used to write all these functions and all these libraries and our Java has it all. And then Python came, which is another abstraction layer. It's like, okay, so now I don't even need to think about that because Python can do all of that. So it's a matter of how you use the tools and what you use them to do. There are areas that I will still go and write in C even today. I don't trust someone inverting metrics for me in an efficient way if it needs to run on a very small CPU. So I'll do that myself. On the other hand, there is going to be elements that I'm going to do.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  29. I think each developer has their Their own part that they enjoy doing. And you don't have to use co-pilot to worry your simple code. You can use copilot through a chat experience and use them as an AI assistant and brainstorm. We're giving you a set of tools.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  30. Especially in the global world where we are, where we see communication is an ongoing challenges between different personas that are taking part in coming up with an idea. And basically we see AI and in our view is co-pilot becoming that next natural language conversation that translator that helps bring everyone on the same page because it's creating that universal conversation language. Same with math used to be.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  31. I'm thinking about that as a better collaboration tool versus a production tool. Because right now a lot of the time where we see challenges in articulating ideas is the communication. It's the clarity of thoughts. So if we can leverage AI to improve collaboration and you basically put a drawing in front of co-piloting, it helps tell the story of what is it that you're asking your developers to do. It shortened a lot of cycles in the back and forth. So what did you mean? Did you mean the button here or did you want to pink or did you wanted that application or did you want a data operating system? So if copilot can help refine communication and it's becoming likely the best collaboration tool that exists in the market.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  32. Right. I think one of the things that we're talking to customers and we're trying to figure out how we articulate is instead of time, can we talk about time to value? So from the moment you put a developer on a task, how long did it take you until you realize the full potential or the full value of that if it's generating revenue, if it's induction, if it's time to market? You can define your time to letter in different ways. But eventually you're investing in AI tools to help your developer to be more productive, to be more efficient, to be more happy, and then easy impacting your time to value, which is something that's the business side that they're looking to measure.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  33. You can write really bad poet really fast. So it's really about how are we taking time and translating it to efficiency, to productivity, to something that are harder to measure. And then how does that lead to the varacore happiness, which is another harder metrics to measure? So the combination of all these input metrics leading to eventually developer happiness is what we're focusing on.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  34. Because we have so many users that are coming to GitHub and they're looking for that productivity gain. But one of the things we're very conscious of is we continue evolving co-pilot and AI across the software development lifecycle, across all the tools. Productivity is not the right metrics against each one of these components when we're implementing AI into GitHub Advanced Security, writing more secure code is the right element. It's like how many secrets were we able to prevent from leaking? How many issues in the code we're able to detect and find and fix before you shipped out? So I think that the world of the metrics for AI is really a big one. We are working a lot with our customers as they're asking the same questions and they're running their own experiments within their companies to figure out what is it that they want to measure. The most easiest one is time, but time is, it's funny what I'm going to say, but time is not quantifiable as a success metrics because

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  35. We are in a world that there are no right metrics. There is no one metric to roll them all. It's a combination of the things that you're looking to measure out of adopting AI. Can think about measuring quality using AI? Can you improve the code quality? Can you improve the security of your code by introducing, for example, our GitHub advanced security using AI? So there's a lot of different metrics that if you combine them together or providing you with that developer productivity, and then there's developer productivity, developer collaboration, time gain that if you're bringing them together are yielding kind of the developer happiness. The biggest area of focus for us right now is the definition of productivity

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  36. To use this tool. And the more you add friction, the more you add churn, the more you add complexity, that, of course, will not want to use their tool. We just talked about all the things that the developer needs to do in every given day. Now add to that mix, I need to learn how to adopt AI. We knew that it will not fly. So it has to be a seamlessly integration. It needs to be something that is very intuitive for developer to use to be successful.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  37. The design philosophy for co-pilot is very much aligned with the working backwards concept that I just mentioned. It's really putting yourself in the shoes of your customers and figuring out what is it that they need? How is that experience going to work for them? Is it an extra tool and if you need to ask for it and if you need to ask for it or if you need to wait for it, then developers will not adopt it. So because we develop it for ourselves first and we wanted to experiment with that, but design philosophy, put yourself at the shoes of a developer, how would you like that experience to be? You know, in 2020, we had a group of GitHub engineers that were working with the design team and we open AI GPT to really figure out how we're going to build that and how it can work to help developers to do their job more efficiently, more productively, improve their collaboration and happiness and so on and so forth. But the grounding principle was a developer needs to

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  38. We have to be the one testing our tools. If we cannot use them, our customers cannot use them for sure. So nothing is shipped before it spends enough months cooking inside GitHub. So we have to say if this is working for us or not before we put it at the end of our customers

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  39. RHR team, you see. Like it or not, it's a different question, but the idea is that we're using GitHub to run GitHub. And the product team is one of the first early adopters along with our engineering team. So, for example, when we've tested chat and we wanted to see the quality or the recommendation, the search, this is something that the product team was one of the first users to go and figure it out. Is it giving me the right thing that I need to do that? Is it summarizing the PR the way I want to summarize? and so on and so forth. But we are really strong in advocating that

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  40. In GitHub in general, it's not just a product. GitHub is GitHub. I'll say we eat our own dogs. And that means that we are the first to try every feature, every capability that we're developing. And it's not just our engineering team. It spans across GitHub. So, for example, GitHub is running on GitHub. There are several blog posts and talks, even in the recent universe, we had a specific talk in terms of how GitHub is using GitHub and adopting AI across software development lifecycle. And the biggest focus for us is if we're saying that GitHub is a developer platform and it's more than that, it's a software development platform. How are we making sure that all the persona that are taking part in the development of GitHub are also using GitHub? So, for example, finance team is using discussions and posts and PRs and repos to communicate RAR numbers and so on and so forth. We have our legal team using.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  41. Shortened 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 and say.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  42. Started thinking about AI, it was 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 elements 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 and that 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.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  43. 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 AI?

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  44. I think there are a couple things. The first one is Companies expect a change to happen magically. Here's a tool. Go use it. And it's not always flying the same way across all companies. So investing time in really taking the company through a change management process. The second thing that I'm seeing is that since AI is so hyped right now, there is often the questions of, oh, what should we do with AI? So there is that sense that I have to do something with AI because if not, I'm not doing the right thing. Versus the question that for me is a big focus for my product team is what is that problem that we're trying to solve? And how can we leverage AI better to help solve the problem versus what do we do with AI? So it's really working backwards from the customer problem, from what we're trying to solve, and then realize what are the best tools that we have in order to do that work better and think through that lenscape versus, oh,

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  45. One, they can write multiple, second, they can have a break and take a breath. So we don't burn them out. And they're more happy. Third, we give them more time for collaboration and creative thinking. So that's sparks innovation. That is not something you want to cut back. This is something you want to be able to give as a gift to your developers so they're happy with you and you can retain them. They can do their job. They're productive, hence they're happy.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  46. No, let me be very clear. You cannot cut your people. You have to have a human in the co-pilot is a co-pilot, is not a pilot. And I keep on saying that sentence again and again. I think the second thing that what companies need to realize, and that's another developer experience survey that we have run recently, that throughout the years, we have added so much tasks on a single software developer from writing code, writing testing, interacting with people, collaborating with 21 people on every given week, going to meetings, waiting on builds, digging into legacy code, all of that is added to the fact that they need to write code, which is their basic work. So most developers spend less than 25, some say less than 20% of their time writing code. So if we're able to give them half an hour back,

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  47. I think Accenture is a recent one that we got where they had 88% of suggested code was retained. So we have a lot of these stats that are coming together to showcase the size and the impact of using co-pilot and AI tools for software development.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  48. Yeah, well, we have over 37,000 organizations and more than 1.5 million developers that are using co-pilot. And they're writing code based on our surveys 55% faster. So imagine that you can give a software developer even few minutes, half an hour back in every given day, how much more productive they are becoming. And also as a result, how much happier they're becoming? So we know that in a survey that we have run through our users, 85% of that participant felt more confident in their code quality and also code reviews were completed 15% faster without a profile. And we know that usually no one likes to do code reviews. So if we can help accelerate and make developers take their time in doing code reviews. And also if we think about removing frustration, then 88% felt less frustrated and more focused on their ability for coding. And that is just the beginning. We have different examples from our customers.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  49. Become much more aligned across the software development lifecycle integration with AI is something that will definitely become something that is more normal for every developer is today something that we start seeing that revolution, that acceptance, that AI tools, they need to figure out how to integrate with AI, I need to know how to use AI will become something that is more custom and we will start seeing that shifts from very early on when developers are start shaping their thinking they will start understanding all these components.

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source

  50. We find it in software development, don't get me wrong, we just find it more in the world of more senior developers and less and less in the junior developers, the junior developers when they start, usually we expect them to be able to write simple code. But if now there is an AI assistant that is helping them writing code, they can spend more time from the get-go understanding the system, understanding the environment that they are building or understanding that product that they're building, which today they don't have time because they are still learning how to code. So I think that's one element. The second element that I expect to see changes is in the world of hardware development because we know that AI has a big footprint and requires a lot of resources. And in order to be able to meet the skill, to meet the demand, we need to be able to improve our hard work, our CPUs, our GPUs, our compute, and optimization of code. And that's another area that today it's a niche of people that are spending time. And I think it will

    2023-12-01 · Lenny's Podcast · The future of AI in software development | Inbal Shani (CPO of GitHub) · IDENTIFIED FROM THE TRANSCRIPT · source