piannaf’s avatarpiannaf’s Twitter Archive—№ 2,357

        1. Live Tweeting the final episode of the week #TouchlabShare "Building a business case for native code sharing"
      1. …in reply to @piannaf
        Our MC @erikEzambrano setting the stage with the quote "The CIO knows where the skeletons are buried -- where the high cost that crept in over the years that can be cut back" from wsj.com/articles/cios-batten-down-hatches-as-recession-looms-11584742492 #TouchlabShare
    1. …in reply to @piannaf
      You need to have conversations with a lot of people in different roles. We're going to focus on empathizing with the Engineering Managers so you can talk more convincingly to sell the idea of #KotlinMultiplatform in your org. #TouchlabShare
  1. …in reply to @piannaf
    There are 4 key goals * Developer velocity * Rapid Testing * Minimiznig tech debt * Recruiting and retention #TouchlabShare
    1. …in reply to @piannaf
      And you'll need to understand * Developer salaries * Number of developers doing the KMP discovery work * Total number of developers * %time spent on tech debt for Android and iOS #TouchlabShare
      1. …in reply to @piannaf
        What we've seen is it typically takes a year to understand KMP well enough to adopt it without further support. And it often takes an additional year to scale the adoption across the organization. If you can increase developer velocity by 50%, there are huge gains #TouchlabShare
        1. …in reply to @piannaf
          From $1MM invested in year 1, your savings in year two is $750K so you're already 75% the way paying back the investment. Then, as you scale KMP across the org, you save about $1MM per year through gains in developer velocity. #TouchlabShare
          1. …in reply to @piannaf
            But that's just part of it. Most managers we talk to would really love to reduce Error Rates. Research says 35-50% of developer time is spent on bug fixes with 15-50 errors per 1000 lines of code. #TouchlabShare
            1. …in reply to @piannaf
              By sharing code, you reduce the surface area of possible errors and where the fixes happen. If you can share just 80% of code, you get $400,000 savings per year #TouchlabShare
              1. …in reply to @piannaf
                Reminder, these are simplified examples and your numbers will be different, but you know your numbers and you can start there. EMs need to think about the ROI as well as the Tech [see recordings from earlier in the week for tech discussion] #TouchlabShare
                1. …in reply to @piannaf
                  Dollars and Tech help EM quantify #KotlinMultiplatform's financial impact. Developer Velocity translates to improved financial returns Shared logic reduces the chance of introducing errors which means further positive financial impact. #TouchlabShare
                  1. …in reply to @piannaf
                    In Q&A now. We'll be tweeting out Q&A in the future from the @TouchlabHQ account. And, if you see an opportunity to have a 1:1 conversation to go deeper, send a message to hello@touchlab.co