Thread by @wiredferret

#DevOpsLoop @editingemily: Rethinking the SDLC

#DevOpsLoop @editingemily: DevOps built on the foundation of agile to become a default, a standard that we reach for to understand what we're doing and what we should be doing.

#DevOpsLoop @editingemily: When DevOps emerged, everything -- from the application to the deployment was centralized. We are finding novel solutions and unique takes to what we have accepted and been working around in DevOps.

#DevOpsLoop @editingemily: DevOps has almost as many meanings as there are people who say they're doing it. It might mean CI, or adding tests, or "devops teams", or a separation of concerns.

#DevOpsLoop @editingemily: There isn't really a universally accepted standard of "how to DevOps", because it's a philosophy that people can use to understand their challenges and make them approachable.

#DevOpsLoop @editingemily: [I am not doing this talk justice, you should watch it]

#DevOpsLoop @editingemily: DevOps is ... an answer to the last problem, not the next one. Cloud Native is the future version, a way to approach our new problems.

#DevOpsLoop @editingemily: Let's get this conversation about the future started. We need to throw away some assumptions, step back and see what we actually have, before we can change it mindfully.

#DevOpsLoop @editingemily: The Software Development Lifecycle has been around in more or less the same format for 60 years, with updates and upgrades, but without a reimagining. We have taken it as given, and not really looked at it.

#DevOpsLoop @editingemily: The SDLC is a remnant, an artifact of a previous era. We should replace it with something that reflects the nature of our work better. We are not making goods on an assembly line, and it's time for something new.

#DevOpsLoop @editingemily: The infinity loop we use to represent the DevOps lifecycle implies linear motion. But no software project is really that straightforward. We need something that embodies the multi-threaded and asynchronous and synchronous natures of our work.

#DevOpsLoop @editingemily: The revolution model gives us a way to understand that our work is continuous and in motion, something that reflects the complexity of modern cloud-native software.

#DevOpsLoop @editingemily: There are 5 circles: Operating, deploying, automating, developing, architecture. There are 6 spokes: Observability, flexibility, scalability, testability, securability, reliability

#DevOpsLoop @editingemily: This model is drawn in two dimensions, but think of it in three -- we move between layers and spokes.

#DevOpsLoop @editingemily: We have been using personas to design our software, but maybe we should be talking about roles, instead. What is someone doing right now, not who they are on an org chart.

#DevOpsLoop @editingemily: Software development isn't a straight line, nor is it a perfect loop -- it's a complex and ever-changing dance, with twirls, loops, spins, and collaborative magic.

#DevOpsLoop @editingemily: We expect software development to be a straight line, but it never is, any more than any other growth or update cycle.

#DevOpsLoop @editingemily: I believe the next 10 years of tech will be focused on developer experience -- not just writing it, but managing it and thinking about it, modeling it.

#DevOpsLoop @editingemily: [I missed explaining large parts of that due to a technical failure on my part, but wow! this concept!]

Image of the revolution model:

#DevOpsLoop @tashadrew: Charming Pirates

#DevOpsLoop @tashadrew: Why do we even open source? Before we understand how to get adoption, we have to understand what we're doing and why.

#DevOpsLoop @tashadrew: Identifying easy on-ramps for contributors helps get open source projects going, but we need to think about user acquisition metrics.

#DevOpsLoop @tashadrew: Startup Metrics for Pirates: foundation to how people think about attracting SaaS revenue. It's a funnel-based model that goes Acquisition->Activation->Retention->Referral->Revenue.

#DevOpsLoop @tashadrew: (because it spells out AARRR)

#DevOpsLoop @tashadrew: Pirate metrics are everywhere, once you know to look for them. Net promoter scores, for example, are about referral.

#DevOpsLoop @tashadrew: Open Source user adoption shouldn't be treated like a SaaS funnel conversion. We're not getting revenue, OS has a different set of goals.

#DevOpsLoop @tashadrew: How can we prove the very real value of an open source project without making it about money/revenue/tracking? [how do we decouple value and dollars?]

#DevOpsLoop @tashadrew: Maintainer funnel: Conscious -> Helped by -> Active community member -> Re-investing -> Maintaining

#DevOpsLoop @tashadrew: Conscious - I know your project exists. Helped by - Project solved a pain point for me. Active community member - Hanging out in chat, submitting pull request. Re-investing - Being active feels good! Maintaining - My peers promote me as part of the proj.

#DevOpsLoop @tashadrew: The easier we make it to contribute, the lower the barrier, the more people we get into the funnel and community.

#DevOpsLoop @tashadrew: In open source, we need to treat the funnel-to-contributor on par with funnel-to-contributor.

#DevOpsLoop @cote: We Fear Change

#DevOpsLoop @cote: No one wants to change! But sometimes we need to. So how do we help people want to change?

#DevOpsLoop @cote: We like to believe that if we just show people the best way, they'll do it

#DevOpsLoop @cote: There are a lot of very professional diagrams and methods about how to roll out change in an organization, but the problem may actually be at the individual level. We have some models for that, too.

#DevOpsLoop @cote: Change is sometimes initiated by fear or disruption, but that is an existential crisis for companies, not individuals.

#DevOpsLoop @cote: Human motivations include: reward to balance risks, fulfillment in the work, emotional and employment safety, life improvements.