Labs: The Science Of Allocating Dev Resources In 2023

**Eran Shitrit** (0:00)
Dan, think about it, like visualize, I'm coming to you as a COO, I'm asking for more resources for my initiative.
It's one thing to say, hey, initiative number two, hey, I have a quality problem there. You would say, okay, I need more data. Totally natural response, right? If I zoom in on this initiative and show you, hey, you know what, Dan? Look, over the last six months, my open bug rate trend is this.
Now we're having a totally different conversation, and say, hey, you know what, Eran? Yes, I can totally support putting two more QA people, all engineers that are focused on quality, now understand, yeah, we want to be more predictable. We all understand that we have a quality issue.

**SPEAKER_2** (0:39)
Want to reduce your team's code review time by up to 40% without touching your budget? GitStream is the new free dev tool from LinearB that eliminates a key bottleneck in your team's workflow, pull requests and code reviews.
After reviewing the work of over 2,000 dev teams, LinearB's engineers and data scientists found that pickup times for code reviews were lasting four to five days longer than they should be. The good news is that they found these delays could be eliminated in four key steps. First, by adding context to every pull request, such as estimated time to review. Second, automatically assigning the right reviewer and number of reviewers to pull requests. Third, having code review automation that auto-request changes.
And finally, by automating PR approvals and merges. To learn more about how GitStream works and to try it out free for your team, please visit gitstream.cm or search for GitStream in the GitHub Marketplace.

**Dan Lines** (1:35)
Hey, what's up everyone? Welcome to Dev Interrupted. I'm your host, Dan Lines, COO at LinearB. And today I'm joined by Eran Shitrit, VP of Product at LinearB.
Eran, welcome to the show, man.

**Eran Shitrit** (1:51)
Hey, Dan, happy to be here. Feels like so privileged to be in Dev Interrupted. I know you for a year and a half. What took you so long, Dan?

**Dan Lines** (1:59)
I know, oh my God. So it's like, it's your first appearance on DI with a special treat for everyone. You and I go way back.
And that's why it like feels so good to finally have you on here. And for listeners who are new to the show or haven't listened to a lab session before, these labs episodes, they're where we take a little bit more of a behind the scenes, like insights, research generated by LinearB. We use that to discuss some of the things that are going on in dev. Sometimes talk about like trends across the industry. In the past, we've covered things like best and worst programming languages for dev workflows.
Actually, a really cool one, data behind pull requests, like all this in-depth data of what's happening with PRs. We also did a metrics benchmark for engineering teams with Ori, so totally recommend checking all those out. Great topics.
But today, our topic, we'll be looking at R&D and project allocation. And that's where Eran comes into play. So like Eran, one of the leading researchers on how like modern dev orgs work or could work and discuss why project allocation has become such an important issue for engineering teams. In fact, last week, LinearB hosted a workshop. This is amazing, y'all gotta check it out. Workshop on Scaling Developer Efficiency. It touches on how we think about project allocation. We had like a few thousand people in the DI or like engineering community join. So, you know, we'll definitely post that link. Everyone check it out.
But let's jump in today's conversation with Eran. Eran, why don't you give yourself kind of like a formal introduction, who you are and what you do at LinearB.

**Eran Shitrit** (4:01)
Thanks, Dan. So in LinearB, I'm the VP of product running the product and UX organization. Came from a background of between like 10 or 15 years. 15 years of product leadership, leading been a year and a half in LinearB, which is a treat. It is amazing ride outside of my compo zone. I love it.
But my former 15 years were actually leading cyber and data protection products from conception. Before that, I was actually doing a lot of cyber and a little bit of enterprise risk management.
And as I will like to call it before, before that, going back to the previous millennial, which gives away a little bit of my age, I was starting as an IT and managing networks and computers and servers for system, back in the 1997 days.

**Dan Lines** (4:50)
Wait, no way. I didn't even know that about you. You started out in like the network game?