LinearB
LinearB
  • 104
  • 46 998
How to Set Goals to Achieve Your Dual Mandate
Yishai Beeri CTO at LinearB and Dan Lines, COO and co-founder at LinearB, discuss about the advantages of a bottom-up approach, which empowers teams to set their own goals and metrics tailored to their specific ways of working. This fosters autonomy, accountability, and a positive culture.
You'll also discover when a top-down approach is beneficial, such as focusing on company-wide initiatives or ensuring alignment across teams. The video offers practical guidance on how to combine these two approaches to achieve a balance that meets your organization's needs.
If you're a developer or engineering leader looking for strategies to set effective goals, this video provides valuable insights and practical takeaways.
Subscribe to our Newsletter ►► linearb.io/blog/#subscribeformore
#engineeringleadership #trending #engineeringteams #startup #enterprise #productivity #stakeholders #planning #data
Переглядів: 17

Відео

The CTO Board Deck Template and How to Present Engineering Data to Your Board
Переглядів 6514 днів тому
Yishai Beeri (CTO at LinearB) and Dan Lines (COO and co-founder at LinearB) dive into the details of a practical CTO board deck template that empowers engineers to confidently present key data to leadership teams. The template is designed to be concise and impactful, focusing on two critical sections: Engineering Health and Key Investments. Subscribe to our Newsletter ►► linearb.io/blog/#subscr...
Starting Your Engineering Metrics Program
Переглядів 42628 днів тому
In this workshop, we walk you through how to drive an average 47% reduction in cycle time via your engineering metrics program and provide you with free resources and tools to get started. A robust metrics program provides holistic visibility into engineering health, predictable project delivery, and a great dev experience. But it’s not always obvious how to build the right software metrics pro...
Modern Practices for Goal Setting in Software Engineering
Переглядів 6472 місяці тому
Too often engineering leaders are forced to guess at delivery timelines because they don’t have the data needed to make informed predictions. The result: inaccurate forecasting, missed milestones, and failing to meet promises made to the business. This workshop shares the best practices we've discovered while working with over 3,000 orgs to track their KPIs and set goals effectively. With this ...
How Syngenta Built a Robust and Transparent Career Ladder for Engineers
Переглядів 312 місяці тому
Join Conor Bronsdon in this interview with Jason Krohn, Global Head of Delivery at Syngenta, where they are talking about how Syngenta built a robust and transparent career ladder for engineers Get started using LinearB ►► share.linearb.io/get-started-24 Subscribe to our Newsletter ►► linearb.io/blog/#subscribeformore #ublockingbottlenecks #podcast #engeneering #engeneeringteams #career #career...
Improving Cycle Time by Unblocking Bottlenecks in QA and Collaboration
Переглядів 533 місяці тому
Improving Cycle Time by Unblocking Bottlenecks in QA and Collaboration
Measuring Impact: GenAI Code
Переглядів 5373 місяці тому
Measuring Impact: GenAI Code
DORA & LinearB present: Insights into the 2023 Accelerate State of DevOps Report
Переглядів 7356 місяців тому
DORA & LinearB present: Insights into the 2023 Accelerate State of DevOps Report
2023 Engineering Benchmarks Report Webinar
Переглядів 7958 місяців тому
2023 Engineering Benchmarks Report Webinar
How We Cut Our CI Pipeline In Half
Переглядів 2028 місяців тому
How We Cut Our CI Pipeline In Half
Programming Languages: Longest vs Shortest Lifespans
Переглядів 689 місяців тому
Programming Languages: Longest vs Shortest Lifespans
gitStream Now Estimates How Much Time Your Team is Saving
Переглядів 2199 місяців тому
gitStream Now Estimates How Much Time Your Team is Saving
Improve: Using Engineering Metrics to Accelerate & Report Roadmap Delivery
Переглядів 60210 місяців тому
Improve: Using Engineering Metrics to Accelerate & Report Roadmap Delivery
Why the Best Engineering Teams Keep Their PR Size Small
Переглядів 13310 місяців тому
Why the Best Engineering Teams Keep Their PR Size Small
Automate: Pre merge Workflow Automation for Dev Efficiency
Переглядів 46011 місяців тому
Automate: Pre merge Workflow Automation for Dev Efficiency
The Data Behind LinearB's Compounding Efficiencies Research
Переглядів 3211 місяців тому
The Data Behind LinearB's Compounding Efficiencies Research
Benchmark: Building an Engineering Metrics Function
Переглядів 1,5 тис.Рік тому
Benchmark: Building an Engineering Metrics Function
The Future of Ops is Platform Engineering
Переглядів 198Рік тому
The Future of Ops is Platform Engineering
gitStream Worshop: How to Apply a Rule - Approving Safe Changes
Переглядів 76Рік тому
gitStream Worshop: How to Apply a Rule - Approving Safe Changes
Why Syngenta Chose LinearB Over Competitors
Переглядів 145Рік тому
Why Syngenta Chose LinearB Over Competitors
What is Cycle Time (aka Lead Time for Changes)?
Переглядів 167Рік тому
What is Cycle Time (aka Lead Time for Changes)?
What is Deployment Frequency?
Переглядів 100Рік тому
What is Deployment Frequency?
What is Mean Time to Restore (MTTR)?
Переглядів 198Рік тому
What is Mean Time to Restore (MTTR)?
What Is Change Failure Rate (CFR)?
Переглядів 169Рік тому
What Is Change Failure Rate (CFR)?
DORA Metrics Defined
Переглядів 2,8 тис.Рік тому
DORA Metrics Defined
gitStream Workshop: How to Install gitStream
Переглядів 218Рік тому
gitStream Workshop: How to Install gitStream
How FloSports Uses LinearB to Improve Their Engineering Efficiency
Переглядів 242Рік тому
How FloSports Uses LinearB to Improve Their Engineering Efficiency
Production Incidents Are A Learning Opportunity
Переглядів 34Рік тому
Production Incidents Are A Learning Opportunity
gitStream Workshop: Getting Started with Workflow Automation
Переглядів 960Рік тому
gitStream Workshop: Getting Started with Workflow Automation
How to Deliver More Business Value as an Engineering Team
Переглядів 63Рік тому
How to Deliver More Business Value as an Engineering Team

КОМЕНТАРІ

  • @johnnyz9368
    @johnnyz9368 22 дні тому

    Promo-SM 😄

  • @briancolfer415
    @briancolfer415 Місяць тому

    How to determine if a particular release produced a failure can be ambiguous. It may be a latent feature or a defect that is not noticed for weeks.

  • @briancolfer415
    @briancolfer415 Місяць тому

    The recommendateion for complete and thorough code reviews is both very specific if describing the Formal Inspection Process or very ambiguous.

  • @bernhardkrickl5197
    @bernhardkrickl5197 Місяць тому

    Guess what? At some point to further reduce PR size and get deeper reviews in a short time, you just switch to pair programming and push to mainline.

  • @briancolfer415
    @briancolfer415 Місяць тому

    Lower MTTR is correlated with more work on features and less Yak shaving and bugfixes.

  • @mosescarayol5316
    @mosescarayol5316 2 місяці тому

    Thank you for this video. A Junior software engineer

    • @LinearBInc
      @LinearBInc 2 місяці тому

      So glad you found it helpful!

  • @antonprokhorov6185
    @antonprokhorov6185 2 місяці тому

    I once heard an interesting point while interviewing Principal Engineer - big PRs for sure might bring troubles and to be very complex to review. But very small PRs are also a signal - in particular scenario from that Engineer - it was actually a sign of some level of toxicity within the team, where they were so constantly throwing review comments that weren't actually helping to make the code better, that irritated devs started doing very atomic PRs thinking "ok now you bastard won't tell me a single word, finally"

  • @Denzelzeldi
    @Denzelzeldi 3 місяці тому

    06:59 A lot of organizations are being very fixated on speed and just looking at speed right like coding time cycle time all of those things and it definitely needs to be balanced with with quality indicators. For example developers might actually write more tests with the time that they're saving which increases the the code coverage but would then also dampen the impact on speed. 07:28 You might you might even get slower [using GenAI in development] if developers get more removed from the code because they didn't write it all, so their debugging time might get longer as at the same time there's risks to quality. There's there's lots been written about the quality risks of [GenAI] coding assistance. 07:55 It is important to not overdo it. I've seen one organization that very strongly looked at adoption and [had] very high expectations from the leadership about the lift that this is going to give in terms of speed so putting very high expectations on developers to use these tools to become a lot faster and putting a lot of pressure. Adoption should be neutrally monitored, like are people actually using it because it's useful and not put on an expectation beforehand of how much lift it's going to get them... obviously if you're if you stated the goal everyone should be using this then you probably pushing people in the in the wrong way 08:58 When measuring benefits it's also important not to have a fixed [goal] like this has to be 30% or more [saving]. The industry doesn't know yet actually what the benefits are how they look at in numbers and how they balance with risks. 21:45 As we're using coding assistance and potentially get higher coding throughput to create more code per time unit, if we look at our software delivery process then we have this one part of our process of our system where we're increasing the throughput. If some people are maybe like familiar with systems thinking, what will happen if we just increase throughput in one of you know one of the parts of our system? We'll get bottlenecks. In a lot of organizations code review or pull request review is already one of the bottlenecks, so what will happen if you create more code? 22:38 At thoughtworks were're big fans of pair programming as a tool to improve team collaboration and also team flow right and you know this could actually be like one of the things to also alleviate this this bottleneck, to have pairs that work with the coding assistant. Almost like a trio programming. 23:08 GitHub calls co-pilot your "AI pair programmer" which which annoys me a lot I have to say, you know because pair programming is about is a team practice to make the team better. 27:49 We are in a hype cycle right now at the peak of inflated expectations and the higher that peak is the bigger the hangover will be and the more people are going to say quickly oh my expectations were so high they were disappointed. So I think the key here is to adjust our expectations because this is definitely going to be useful in my opinion and going to be here to stay and we just have to figure out how to properly use it so that it. 29:01 I can also confirm I haven't seen anything really impressive there yet in that area so often when I would ask a coding assistant for example how can I improve this code or something, it gives me like, you could can add error handling, you know like very like generic kinds of things almost like a checklist of like a a newbie code reviewer. There's definitely still potential maybe it also can still get better. 43:27 I've been coding for more than 20 years at this point and even today you just go on the internet and you copy and paste things when you don't know yet what to do and you stitch them together and you just want to get it to work once. So I think in a way we've we've all been doing this right, there's just a tool now that can potentially make us even faster at doing that and that might make the problem worse. But I also have faith that maybe we will all adapt to this and we will still put our hands on the hot stove and get burned and then learn from that. So those cycles will still be the same so I'm trying to be not too cynical about it.

  • @krumbergify
    @krumbergify 5 місяців тому

    Really good presentation and Q/A. I read the report(s) but this gives much more flesh on the bones. To be honest I thought that DevOps was just another bussword but after learning more I really like what it represents. It aligns very well with all my experiences as a developer.

  • @user-gu2fl7il7g
    @user-gu2fl7il7g 5 місяців тому

    How do I access these reports?

  • @DevInterrupted
    @DevInterrupted 6 місяців тому

    Killer event!

  • @harriottgaige5871
    @harriottgaige5871 9 місяців тому

    💃 *Promo sm*

  • @bching2002
    @bching2002 9 місяців тому

    I really like this video, it not just helps me to under DORA metrics but also how to implement it.

  • @agatasobasikem8578
    @agatasobasikem8578 10 місяців тому

    Great summary! Thank you that was exactly what I was looking for.

  • @kroy1570
    @kroy1570 11 місяців тому

    sorry not even understanding the post above. can you dumb it down so a Program Manager can understand?

  • @paul4ashraf
    @paul4ashraf Рік тому

    Thank you for this! Sorry I missed the webinar

  • @Tristan-mr3pk
    @Tristan-mr3pk Рік тому

    To me the value of DORA comes when paired with the capability model and the 24 capabilities from Accelerate. Without that context I think DORA looses its meaning.

  • @aliasuser958
    @aliasuser958 Рік тому

    Lots of really good nuggets here!

  • @celestinaliebrecht4679
    @celestinaliebrecht4679 Рік тому

    promosm

  • @alphonsokirk8340
    @alphonsokirk8340 Рік тому

    𝔭𝔯𝔬𝔪𝔬𝔰𝔪 😜