Podcasts about devops building

Could the secret to organizational success be as simple as going back to basics? Gene Kim and Steven Spear's new book, Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and Amplification presents practical, grounded research on organizational management and design. Gene is the chair of the Enterprise Technology Leadership Summit and Steven teaches at MIT Sloan.Gene and Steven walk Greg through the three mechanisms of successful organizational design: slowify, simplify, and amplify. They also discuss how the field of organizational design has evolved and what still needs to evolve with management education. *unSILOed Podcast is produced by University FM.*Episode Quotes:Three mechanisms of a successful organizational designWe now have everything we need to be able to describe the three mechanisms that must be in place in any high-performing system. You got to slowify, meaning we move the most difficult problems from production into planning and practice, where work can be redone. We can do experiments. We can learn where we can simplify where we actually divide up the problems. We partition them so that they are easier to solve. And there's three dimensions of that. And then there's amplification, this overlay of how do we create a system that can amplify even the weakest signals so that when someone needs help or when there's danger that we can quickly detect and correct or ideally prevent from happening again. What the term ‘slowification' means38:39 The reason why we had to create the word ‘slowification' is that we have a lot of adages for slow down to speed up or stop sawing to sharpen the saw, and the absence of the word prevents us from doing it or thinking it. (38:46) But the whole notion is creating time to be able to solve tough problems not in production but in planning and practice. To solve architectural problems, not during the normal sprint or what have you, but actually making time for the architectural spike or the period of technical debt reduction to enable people to do their work easily and well.The wrong way to measure successA lot of these metric-driven organizations, the pit they fall into is they don't account for the return on investment of discovery. They measure activity but not accomplishment.The great advantages of technology in management educationAnd now, because we can do education at a distance, we can do asynchronous education, we can have education which is interspersed with either structured experiences or just natural experiences that people have. We can now actually teach one by one as needed as ready situation where information is pulled from the instructor to time and place and situation where it's needed, rather than being forced by the instructor in a formulation that the instructor thinks is right but may have nothing to do with the readiness of the student.Show Links:Recommended Resources:Decoding the DNA of the Toyota Production System | Harvard Business ReviewChristina Maslach on unSILOed Gary Klein on unSILOedDr. Richard ShannonRon WestrumKim ClarkNyquist–Shannon sampling theoremGuest Profile:Gene Kim's WebsiteSteven Spear's profile at MIT SloanTheir Work:Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and AmplificationGene's Books:Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology OrganizationsThe DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business WinThe Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of DataSteve's Book:The High-Velocity Edge: How Market Leaders Leverage Operational Excellence to Beat the Competition 

In the Microsoft Research Podcast series What's Your Story, Johannes Gehrke explores the who behind the technical and scientific advancements helping to reshape the world. A systems expert whose 10 years with Microsoft spans research and product, Gehrke talks to members of the company's research community about what motivates their work and how they got where they are today.Partner Research Manager and leading developer experience expert Nicole Forsgren oversees Microsoft Research efforts to enhance software engineering effectiveness through the study of developer productivity, community, and well-being. In this episode, she discusses AI's potential impact on software engineering, what she loves about tech, and how thoughtful decision making—combined with listening to her gut—has led to opportunities as a developer, accounting professor, and founder and CEO of a startup that was eventually acquired by Google.Learn more:Nicole Forsgren at Microsoft ResearchNicole Forsgren websiteQuantifying the impact of developer experience | Microsoft Azure Blog, January 2024Yes, good DevEx increases productivity. Here is the data. | GitHub blog, January 2024Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations | Book, 2018

今回は「LeanとDevOpsの科学［Accelerate］-テクノロジーの戦略的活用が組織変革を加速する」という本で紹介されている、DevOps開発と組織やビジネスのパフォーマンスとの関係に関する研究結果についてについて話しました。 LeanとDevOpsの科学［Accelerate］-テクノロジーの戦略的活用が組織変革を加速する Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations 27 capabilities https://cloud.google.com/architecture/devops?hl=ja https://engineering.visional.inc/blog/412/devops-days-tokyo-2022-after/ Your co-hosts: Tomoaki Imai, Knot, inc CTO https://twitter.com/tomoaki_imai Ryoichi Kato, Software Engineer ⁠https://twitter.com/ryo1kato

Will Larson is Chief Technology Officer at Carta. Prior to joining Carta, he was the CTO at Calm and held engineering leadership roles at Stripe, Uber, and Digg. He is the author of two foundational engineering career books, An Elegant Puzzle and Staff Engineer, and The Engineering Executive's Primer, which will be released in February. In our conversation, we discuss:• Systems thinking: what it is and how to apply it• Advice for product managers on fostering productive relationships with engineering managers• Why companies should treat engineers like adults• How to best measure developer productivity• Writing and its impact on his career• How to balance writing with a demanding job• How to develop your company values—Brought to you by DX—A platform for measuring and improving developer productivity | OneSchema—Import CSV data 10x faster | Vanta—Automate compliance. Simplify security.—Find the transcript for this episode and all past episodes at: https://www.lennyspodcast.com/episodes/. Today's transcript will be live by 8 a.m. PT.—Where to find Will Larson:• X: https://twitter.com/Lethain• LinkedIn: https://www.linkedin.com/in/will-larson-a44b543/• Website: https://lethain.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Will's background(04:12) Changes in the field of engineering(06:27) We need to stop treating engineers like children(08:32) Systems thinking(13:23) Implementing systems thinking in hiring(16:32) Engineering strategy(20:21) Examples of engineering strategies(25:08) How to get good at strategy(26:48) The importance of writing about things that excite you(32:40) The biggest risk to content creation is quitting too soon(35:24) How to make time for writing(37:41) Tips for aspiring writers(41:18) Building productive relationships between product managers and engineers(43:45) Giving the same performance rating to EMs and PMs(48:24) Measuring engineering productivity(55:53) Defining company values(01:02:10) Failure corner: the Digg rewrite(01:11:05) Will's upcoming book, The Engineering Executive's Primer(01:12:04) Lightning round—Referenced:• The end of the “free money” era: https://www.theguardian.com/technology/2023/apr/11/techscape-zirp-tech-boom• Work on what matters: https://lethain.com/work-on-what-matters/• Sheryl Sandberg to Harvard Biz Grads: “Find a Rocket Ship”: https://www.forbes.com/sites/kashmirhill/2012/05/24/sheryl-sandberg-to-harvard-biz-grads-find-a-rocket-ship/?sh=708c9a93b37a• What Is Systems Thinking?: https://www.snhu.edu/about-us/newsroom/business/what-is-systems-thinking• Introduction to systems thinking: https://lethain.com/systems-thinking/• Thinking in Systems: https://www.amazon.com/Thinking-Systems-Donella-H-Meadows/dp/1603580557• Silent Spring: https://www.amazon.com/Silent-Spring-Rachel-Carson/dp/0618249060• Writing an engineering strategy: https://lethain.com/eng-strategies/• Carta: https://carta.com/• Eric Vogl on LinkedIn: https://www.linkedin.com/in/ericvogl/• Good Strategy/Bad Strategy: The difference and why it matters: https://www.amazon.com/Good-Strategy-Bad-difference-matters/dp/1781256179• The Crux: How Leaders Become Strategists: https://www.amazon.com/Crux-How-Leaders-Become-Strategists/dp/1541701240/• How Big Things Get Done: The Surprising Factors That Determine the Fate of Every Project, from Home Renovations to Space Exploration and Everything in Between: https://www.amazon.com/How-Big-Things-Get-Done/dp/0593239512/• Technology Strategy Patterns: Architecture as Strategy: https://www.amazon.com/Technology-Strategy-Patterns-Architecture/dp/1492040878/• The Value Flywheel Effect: Power the Future and Accelerate Your Organization to the Modern Cloud: https://www.amazon.com/Value-Flywheel-Effect-Accelerate-Organization/dp/1950508579• The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win: https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/1942788290• The Engineering Executive's Primer: Impactful Technical Leadership: https://www.amazon.com/Engineering-Executives-Primer-Impactful-Leadership/dp/1098149483• An Elegant Puzzle: Systems of Engineering Management: https://press.stripe.com/an-elegant-puzzle• Staff Engineer: Leadership beyond the management track: https://www.amazon.com/Staff-Engineer-Leadership-beyond-management-ebook/dp/B08RMSHYGG• Gergely Orosz's newsletter: https://blog.pragmaticengineer.com/author/gergely/• Leaving big tech to build the #1 technology newsletter | Gergely Orosz (The Pragmatic Engineer): https://www.lennyspodcast.com/videos/leaving-big-tech-to-build-the-1-technology-newsletter-gergely-orosz-the-pragmatic-engineer/• The art of product management | Shreyas Doshi (Stripe, Twitter, Google, Yahoo): https://www.lennyspodcast.com/videos/the-art-of-product-management-shreyas-doshi-stripe-twitter-google-yahoo/• Henry Ward on LinkedIn: https://www.linkedin.com/in/heward/• Vrushali Paunikar on LinkedIn: https://www.linkedin.com/in/vrushali-paunikar/• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339• How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google): https://www.lennyspodcast.com/how-to-measure-and-improve-developer-productivity-nicole-forsgren-microsoft-research-github-goo/• DORA: https://dora.dev/• Setting engineering org values: https://lethain.com/setting-engineering-org-values/• Digg: https://digg.com/• Kevin Rose on LinkedIn: https://www.linkedin.com/in/kevinrose/• Digg's v4 launch: an optimism born of necessity: https://lethain.com/digg-v4/• Dash Gopinath on LinkedIn: https://www.linkedin.com/in/dashgopinath/• Rich Schumacher on LinkedIn: https://www.linkedin.com/in/richschumacher/• The ALL NEW Don't Think of an Elephant!: Know Your Values and Frame the Debate: https://www.amazon.com/ALL-NEW-Dont-Think-Elephant-ebook/dp/B00NP9LHFA• Top Chef on Peacock: https://www.peacocktv.com/watch-online/tv/top-chef/5172289448907967112• Hard to work with: https://lethain.com/hard-to-work-with/—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

DORA Metriken: Die Performance-Messung deines Software Development Teams bzw. die Ermittlung des Reifegrades von DevOps in deiner OrganisationSoftwareentwicklung ist ein kreativer Beruf. Jedes Projekt ist einzigartig und die geschriebenen Lines of Code sagen wenig über die dafür benötigte Zeit aus. Das Research-Programm DevOps Research and Assessment (DORA) versucht dennoch die Performance eines Software-Entwicklungs-Teams zu messen. Nicht via Lines of Code, sondern auf Basis von Aktivitäten, die Value liefern: Deployment Frequency, Lead Time for Changes, Mean Time to Recovery, Change Failure Rate und Reliability.Die Metriken selbst sind weit bekannt. Wie diese Metriken beeinflusst werden können, wer eigentlich dahinter steckt, und was die Organisation eigentlich für eine Kultur vorleben muss, damit es überhaupt zu einem positiven Ergebnis kommt, wissen viele nicht. Und genau darüber sprechen wir in dieser Episode.Bonus: AOL CDs und Metal-Musik aus Litauen**** Diese Episode wird von trivago gesponsert:trivago aus Düsseldorf sucht Verstärkung für ihr Site Reliability Engineering Team. Arbeite eng mit den Entwicklungsteams an der globalen Hotelsuchmaschine. Profitiere von einem autonomen Arbeitsumfeld und bewirb dich unter https://careers.trivago.com/sre ****Das schnelle Feedback zur Episode:

This episode is brought to you by DX—a platform for measuring and improving developer productivity.—Dr. Nicole Forsgren is a developer productivity and DevOps expert who works with engineering organizations to make work better. Best known as co-author of the Shingo Publication Award-winning book Accelerate and the DevOps Handbook, 2nd edition and author of the State of DevOps Reports, she has helped some of the biggest companies in the world transform their culture, processes, tech, and architecture. Nicole is currently a Partner at Microsoft Research, leading developer productivity research and strategy, and a technical founder/CEO with a successful exit to Google. In a previous life, she was a software engineer, sysadmin, hardware performance engineer, and professor. She has published several peer-reviewed journal papers, has been awarded public and private research grants (funders include NASA and the NSF), and has been featured in the Wall Street Journal, Forbes, Computerworld, and InformationWeek. In today's podcast, we discuss:• Two frameworks for measuring developer productivity: DORA and SPACE• Benchmarks for what good and great look like• Common mistakes to avoid when measuring developer productivity• Resources and tools for improving your metrics• Signs your developer experience needs attention• How to improve your developer experience• Nicole's Four-Box framework for thinking about data and relationships—Find the full transcript at: https://www.lennyspodcast.com/how-to-measure-and-improve-developer-productivity-nicole-forsgren-microsoft-research-github-goo/#transcript—Where to find Nicole Forsgren:• Twitter: https://twitter.com/nicolefv• LinkedIn: https://www.linkedin.com/in/nicolefv/• Website: https://nicolefv.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Nicole's background(07:55) Unpacking the terms “developer productivity,” “developer experience,” and “DevOps”(10:06) How to move faster and improve practices across the board(13:43) The DORA framework(18:54) Benchmarks for success(22:33) Why company size doesn't matter (24:54) How to improve DevOps capabilities by working backward(29:23) The SPACE framework and choosing metrics(32:51) How SPACE and DORA work together(35:39) Measuring satisfaction(37:52) Resources and tools for optimizing metrics(41:29) Nicole's current book project(45:43) Common pitfalls companies run into when rolling out developer productivity/optimizations(47:42) How the DevOps space has progressed(50:07) The impact of AI on the developer experience and productivity(54:04) First steps to take if you're trying to improve the developer experience(55:15) Why Google is an example of a company implementing DevOps solutions well(56:11) The importance of clear communication(57:32) Nicole's Four-Box framework(1:05:15) Advice on making decisions (1:08:56) Lightning round—Referenced:• Chef: https://www.chef.io/• DORA: https://dora.dev/• GitHub: https://github.com/• Microsoft Research: https://www.microsoft.com/en-us/research/• What is DORA?: https://devops.com/what-is-dora-and-why-you-should-care/• Dustin Smith on LinkedIn: https://www.linkedin.com/in/dustin-smith-b0525458/• Nathen Harvey on LinkedIn: https://www.linkedin.com/in/nathen/• What is CI/CD?: https://about.gitlab.com/topics/ci-cd/• Trunk-based development: https://cloud.google.com/architecture/devops/devops-tech-trunk-based-development• DORA DevOps Quick Check: https://dora.dev/quickcheck/• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339• The SPACE of Developer Productivity: https://queue.acm.org/detail.cfm?id=3454124• DevOps Metrics: Nicole Forsgren and Mik Kersten: https://queue.acm.org/detail.cfm?id=3182626• How to Measure Anything: Finding the Value of Intangibles in Business: https://www.amazon.com/How-Measure-Anything-Intangibles-Business/dp/1118539273/• GitHub Copilot: https://github.com/features/copilot• Tabnine: https://www.tabnine.com/the-leading-ai-assistant-for-software-development• Nicole's Decision-Making Spreadsheet: https://docs.google.com/spreadsheets/d/1wItAODkhZ-zKnnFbyDERCd8Hq2NQ03WPvCfigBQ5vpc/edit?usp=sharing• How to do linear regression and correlation analysis: https://www.lennysnewsletter.com/p/linear-regression-and-correlation-analysis• Good Strategy/Bad Strategy: The difference and why it matters: https://www.amazon.com/Good-Strategy-Bad-difference-matters/dp/1781256179/• Designing Your Life: How to Build a Well-Lived, Joyful Life: https://www.amazon.com/Designing-Your-Life-Well-Lived-Joyful/dp/1101875321• Ender's Game: https://www.amazon.com/Enders-Game-Ender-Quintet-1/dp/1250773024/ref=tmm_pap_swatch_0• Suits on Netflix: https://www.netflix.com/title/70195800• Ted Lasso on AppleTV+: https://tv.apple.com/us/show/ted-lasso• Never Have I Ever on Netflix: https://www.netflix.com/title/80179190• Eight Sleep: https://www.eightsleep.com/• COSRX face masks: https://www.amazon.com/COSRX-Advanced-Secretion-Hydrating-Moisturizing/dp/B08JSL9W6K/—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

This week, Dan Neumann is joined by Mike Guiler to discuss the benefits of Agility, including employee satisfaction, predictable delivery, and speed to market among others.   Key Takeaways: Agility leads to employee satisfaction since every Team member is connected to the purpose of the work. Sustainable pace is enabled by Agile Methods Agile done well eliminates the “death march” Deliver slices of value  Deliver the most valuable items first Agile delivery is not “all-or-nothing,” enabling us to decide what we can release without Predictable delivery is mostly assured with Agile, and even when the mark is missed it can be adjusted back in a brief period. Reduction of Waste The Increment is inspected frequently We learn from what we deliver You can stop and pivot when going down a path that is not what the customer needs Make change easier Validate assumptions early Reduce Risk  Don't build the whole thing before we deliver it Reduce risk by gradually exposing your features to users versus an “all-or-nothing” release Incremental deliveries reduce risk by validating assumptions. You get real customer feedback. Speed to Market Deliver the right things, reduce waste, and get a slice delivered! Do not expect that your developers will “code faster” Faster Return on Investment Generate revenue with small slices Decide when to stop investing further in a product When you decide to transform your business outcomes, you need to consider the benefits you are striving for when you make decisions within your organization. Keep the end goal in mind at all times. We want to be efficient instead of effective. Collaboration works wonders; a Team is more resilient and efficient when collaborating. Some people are not ready to work in a Team; they need space and time to gradually start feeling more comfortable with teaming. Scrum is often perceived as having a lot of meetings when in reality, the meetings required are the minimum necessary to keep the Team aligned toward achieving the common purpose.   Mentioned in this Episode: Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren Ph.D., Jez Humble, and Gene Kim   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!  

Is development becoming obsolete? We invited Miku and Pauliina to talk about software engineering — how the roles have been shaping, what the current trends and challenges are, and how we can shape the future of our profession. Tune in and join our semi-practical, semi-philosophical conversation.GuestsPauliina started her career as a communications consultant, but slowly life took her back to her childhood hobby - coding. She moved all the way to Australia to study at a coding bootcamp and has now been working as a software developer for over 5 years. She still thinks it was the best decision of her life. What she loves most about coding is how tangible it feels to build software one piece at a time and how rewarding it is to solve problems with technology. In her free time,, you will find her on a yoga mat or wandering in a forest.With nearly 20 years of experience, Mikael is a passionate, future-oriented technology leader with a cultivated interest in cutting-edge technologies and the methodologies of creating exceptional digital products. While he currently has limited time to actually code at work, he still does it as a hobby. Mikael is a fan of functional programming and loves exploring new tech, surfing, and cooking.Mikael's core expertise and interests are the design of technology organizations, technology strategy, business, and digital strategy, innovation, software and enterprise architectures, modern process methodologies, modern leadership, self-organization, systems thinking, data, and AI.HostAnna Fröblom is a great programmer, problem-solver, hobby photographer, lego enthusiast, and simply a nice person.Guest HostRoss Langley is a human-centered designer from Reaktor Helsinki. He loves helping teams excel in challenging environments. Ross shines when he does concept modeling, validates ideas, or makes celebrity impressions. References:Malan, Pais, Skelton: Team Topologies: Organizing Business and Technology Teams for Fast FlowCagan: Inspired: How to Create Tech Products Customers Love (Silicon Valley Product Group)Forsgren, Humble, Kim: Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology OrganizationsGoogle Cloud 2022: Announcing the 2022 Accelerate State of DevOps Report: A deep dive into securityAbout ReaktorFork Pull Merge Push is a podcast created for developers by developers. It's brought to you by Reaktor,  a creative technology partner for forward-thinking companies and societies, based in Helsinki, New York, Amsterdam, Stockholm, Lisbon, and Tokyo.We at Reaktor are looking for exceptional talent and new friends. Check our open positions and apply now!

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. When Peter joined this project, the teams had been working on it for years and had little to show for it. Thanks to the CTO at the company, the new team which Peter coached, was able to focus on small, valuable increments to deliver the back-office system the company needed. Listen to this segment, to hear how we can help teams go from BIG BANG thinking to incremental delivery, a crucial need for Agile teams.  In this segment, we refer to the Toyota Kata and the PDCA cycle.  Featured Book of the Week: Accelerate by Forsgren et al.  In Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Forsgren et al., Peter found evidence-based support for many of the approaches, and practices used by Agile teams and Agile organizations. In this segment, we talk about the DORA metrics, and how to focus software development on business results.  Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!   About Peter Janssens Peter built a long career in agile coaching and training, and worked in leadership positions leading a PO team, and recently became CTO in a SAAS product company. Peter loves all conversations on effectiveness of team decisions, but he quickly realized that being responsible is different from being a coach. As a leader there is the challenge of sticking to the same foundations when dealing with delivery pressure. You can link with Peter Janssens on LinkedIn.

John Cutler writes the popular and beloved product newsletter The Beautiful Mess. For many years, he was a Product Evangelist at Amplitude, which led him to meeting and working with a large number of product teams around the world. Through this role, he gained unique insight into how the best product teams operate. In today's episode, John reflects on leaving his role at Amplitude, and explains the attributes that the top 1% of product teams share. We also go deep into some of his favorite frameworks and discuss the best way to apply these frameworks to your work. We also unpack skills like product sense and product mindset, and what he's planning in his new role at Toast.—Find the full transcript here: https://www.lennyspodcast.com/what-differentiates-the-highest-performing-product-teams-john-cutler-amplitude-the-beautiful-mess/#transcript—Thank you to our wonderful sponsors for supporting this podcast:• Merge—A single API to add hundreds of integrations into your app: http://merge.dev/lenny• Eppo—Run reliable, impactful experiments: https://www.geteppo.com/• Vanta—Automate compliance. Simplify security: https://vanta.com/lenny—Where to find John Cutler:• Twitter: https://twitter.com/johncutlefish• LinkedIn: https://www.linkedin.com/in/johnpcutler/• Newsletter: https://cutlefish.substack.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—Referenced:• Amplitude: https://amplitude.com/• The North Star Playbook: https://info.amplitude.com/north-star-playbook• Craig Daniel on LinkedIn: https://www.linkedin.com/in/craigmdaniel/• Working Backwards: Insights, Stories, and Secrets from Inside Amazon: https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595• AppFolio: https://www.appfolio.com/• High Leverage Product Evangelism: https://cutlefish.substack.com/p/high-leverage-product-evangelism• Satya Nadella on LinkedIn: https://www.linkedin.com/in/satyanadella/• The Culture Map: Breaking Through the Invisible Boundaries of Global Business: https://www.amazon.com/Culture-Map-Breaking-Invisible-Boundaries/dp/1610392507• Innovation Labs: https://innovationlabs.com/• BEES: https://mybeesapp.com/• Marty Cagan on Lenny's Podcast: https://www.lennysnewsletter.com/p/the-nature-of-product-marty-cagan#details• Sooner Safer Happier: Antipatterns and Patterns for Business Agility: https://www.amazon.com/Sooner-Safer-Happier-Patterns-Antipatterns/dp/1942788916• Teresa Torres on LinkedIn: https://www.linkedin.com/in/teresatorres/• Andrew Huberman on Instagram: https://www.instagram.com/hubermanlab/?hl=en• TBM 49/52: Pyramid of Leadership Self/Other Awareness: https://cutlefish.substack.com/p/tbm-4952-pyramid-of-leadership-selfother• ChatGPT: https://chat.openai.com/chat• How to Measure Anything: Finding the Value of Intangibles in Business: https://www.amazon.com/How-Measure-Anything-Intangibles-Business-ebook/dp/B00INUYS2U• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339• User Story Mapping: Discover the Whole Story, Build the Right Product: https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/B08TZGKKF2• Build with Maggie Crowley podcast: https://podcasts.apple.com/us/podcast/build-with-maggie-crowley/id1445050691• One Knight in Product podcast: https://www.oneknightinproduct.com/index.html#page-top• Sunny Bunnies on Netflix: https://www.netflix.com/title/81286920• Booba on Netflix: https://www.netflix.com/title/81011059• Toast: https://pos.toasttab.com/• Drift: https://www.drift.com/John's list of high-performing people worth following:• Dr. Cat Hicks (@grimalkina) https://www.linkedin.com/in/drcathicks/ • Stephanie Leue https://www.linkedin.com/in/stephanie-leue/• Amy Edmondson (@AmyCEdmondson) https://www.linkedin.com/in/amedmondson/• Dominica DeGrandis (@dominicad) https://www.linkedin.com/in/dominicadeg/• Courtney Kissler https://www.linkedin.com/in/courtney-kissler-0930681/• Christina Wodtke (@cwodtke) https://www.linkedin.com/in/christinawodtke/• Matthew Skelton https://www.linkedin.com/in/matthewskelton/• Heidi Helfand (@heidihelfand): https://www.linkedin.com/in/heidihelfand/—In this episode, we cover:(00:00) What is a product evangelist? John's unique role at Amplitude(05:50) John's reflections and feelings on leaving Amplitude(17:28) What John's doing next(18:52) John's newsletter: The Beautiful Mess(27:49) What do the top 1% of product teams have in common?(40:08) Different ways companies are successful, and why anyone can improve(45:55) Investing in people vs. investing in processes(48:49) The importance of culture and values(49:59) Global company cultures: the individualist vs. the collectivist  (55:55) Why it's hard to make changes in large companies(58:49) How to view frameworks(1:01:02) The spectrum of performance in big and small companies(1:05:27) Examples of high-performing people who work outside of Silicon Valley(1:09:02) The skill of product management(1:11:35) The value of learning a bit about everything(1:13:46) Why do people often underestimate the loops available at their company(1:16:20) Chronic vs. acute issues at companies(1:18:07) Unpacking the skills behind product sense and product mindset(1:20:44) A place for people without the traditional meritocracy mindset(1:22:38) John's writing process and what he plans on writing about next(1:27:52) How to use ChatGPT for learning and levity(1:31:56) Lightning Round—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Quais os caminhos possíveis para profissionais sênior em tecnologia?

Daniel Yanisse is the co-founder and CEO of Checkr, a leading HR technology company, currently valued at $5 billion. During the journey, Daniel has raised over $679M for Checkr from some of the best including Accel, Bond, Coatue, GV, Elad Gil and IVP to name a few. Prior to Checkr, Daniel was a software engineer and helped develop prototypes of the Mars Rover for NASA. Daniel has been recognized in Forbes “30 Under 30” and recently Checkr was recognized by Forbes as one of America's best start-up employers. In Today's Episode with Daniel Yanisse You Will Learn: 1.) The Origins of Checkr: The $5BN Company How did Daniel come to co-found Checkr? What was the a-ha moment? How did Daniel's experience with his prior company impact how he thought about building Checkr? What does Daniel know now that he wishes all first-time founders knew when they started? 2.) Hiring 101: What are the single biggest hiring mistakes Daniel made in the early days of Checkr? How does Daniel structure his interview process for new candidates today? How has it changed? How does Daniel test for ego and humility in the interview process? How does Daniel approach giving feedback today? How has it changed over time? What does Daniel believe is the right way to let someone go? How long does one give a team member who is not performing? 3.) Fundraising 101: How does Daniel advise founders going out to raise today in the challenging market conditions? What terms should founders optimize for? What terms should they not optimize for? What are the single biggest mistakes Daniel sees founders make when raising? What does Daniel wish he had done differently with Checkr's raises? What was the hardest raise for Checkr? Why was it so hard? What was the outcome? 4.) Going into Enterprise: Why does Daniel believe they went into enterprise too soon? What was the result of this? How does Daniel advise founders on when is the right time to go into enterprise? What changes in both your company and your product when moving to enterprise? Items Mentioned in Today's Episode with Daniel Yanisse: Daniel's Favourite Book: Accelerate: The Science of Lean Software and Devops: Building and Scaling High Performing Technology Organizations

In this episode, we'll start by separating out Agile from DevOps, and then bringing in CI/CD pipelines.  We'll also discuss DevSecOps and some of the best practices in engineering that a developer can adopt. We'll also give an overview of what a CI/CD pipeline looks like, what a pipeline stage is, what a pipeline's purpose is, and how it is related to DevOps.  As a bonus, I talk about tools for Static Code Analysis (SCA) and Static Application Security Testing (SAST)!  We'll also touch on Test Driven Development (TDD).  ----- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Storytime with Dad Podcast

If you write software, you are probably collaborating with other developers.  If you are collaborating, then you probably need to isolate your code and then merge it together when you're done.  So what are some of the best-practices for managing this? My favorite is trunk-based development, but that name probably doesn't mean what you think it means!  In this episode, we dive into branching strategies and trunk-based development.  We also touch on test automation, CI/CD pipelines, agility, and DevOps practices.  We'll also talk about anti-patterns or "worst practices" that some companies adopt because they are risk averse.  Ironically, many of today's software delivery practices increase risk rather than decrease it! Hear my take and compare it to your own, then Tweet me (@tweetsofgrant) and tell me where our views differ! ----- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Google's Guidebook on Trunk-Based Development Other Visualizations of Trunk-Based Development

In part two of this two-part episode on The DevOpsHandbook, Second Edition, Gene Kim speaks with coauthors Dr. Nicole Forsgren and Jez Humble about the past and current state of DevOps. Forsgren and Humble share with Kim their DevOps aha moments and what has been the most interesting thing they've learned since the book was released in 2016. Jez discusses the architectural properties of the programming language PHP and what it has in common with ASP.NET. He also talks about the anguish he felt when Mike Nygard's book, Release It!, was published while he was working on his book, Continuous Delivery. Forsgren talks about how it feels to see the findings from the State of DevOps research so widely used and cited within the technology community. She explains the importance of finding the link between technology performance and organizational performance as well as what she's learned about the importance of culture and how it can make or break an organization. Humble, Forsgren, and Kim each share their favorite case studies in The DevOps Handbook.   ABOUT THE GUEST(S) Dr. Nicole Forsgren and Jez Humble are two of five coauthors of The DevOps Handbook along with Gene Kim, Patrick Debois and John Willis. Forsgren, PhD, is a Partner at Microsoft Research. She is coauthor of the Shingo Publication Award-winning book Accelerate: The Science of Lean Software and The DevOps Handbook, 2nd Ed., and is best known as lead investigator on the largest DevOps studies to date. She has been a successful entrepreneur (with an exit to Google), professor, performance engineer, and sysadmin. Her work has been published in several peer-reviewed journals. Humble is co-author of Lean Enterprise, the Jolt Award-winning Continuous Delivery, and The DevOps Handbook. He has spent his career tinkering with code, infrastructure, and product development in companies of varying sizes across three continents, most recently working for the US Federal Government at 18F. As well as serving as DORA's CTO, Jez teaches at UC Berkeley.   YOU'LL LEARN ABOUT Projects Jez and Gene worked on together before The DevOps Handbook came out. What life is like for Jez as a site reliability engineer at Google and what he's learned. The story behind his DevOps aha moment in 2004, working on a large software project involving 70 developers. The architectural properties of his favorite programming language PHP, what it has in common with ASP.NET, and the importance of being able to get fast feedback while building something. The anguish that Jez felt when Mike Nygard's book, Release It!, came out, wondering if there was still a need for the book he was working on, which was Continuous Delivery. “Testing on the Toilet” and other structures for creating distributed learning across an organization and why this is important to create a genuine learning dynamic. What Dr. Forsgren is working on now as Partner of Microsoft Research. Some of Dr. Forsgren's goals as we work together on the State of DevOps research and how it feel to have those findings so widely used and cited within the technology community. The importance of finding the link between technology performance and organizational performance and why it probably was so elusive for at least 40 years in the research community. What Dr. Forsgren has learned about the importance of culture, how it can make or break an organization, and the importance of great leadership.   RESOURCES Personal DevOps Aha Moments, the Rise of Infrastructure, and the DevOps Enterprise Scenius: Interviews with The DevOps Handbook Coauthors (Part 1 of 2: Patrick Debois and John Willis) The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, Second Edition, by Gene Kim, Patrick Debois, John Willis, Jez Humble, and Dr. Nicole Forsgren Nudge: Improving Decisions About Health, Wealth, and Happiness by Richard H. Thaler and Cass R. Sunstein Nudge vs Shove: A Conversation With Richard Thaler The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps by Kevin Behr, Gene Kim and George Spafford FlowCon Elisabeth Hendrickson on the Idealcast: Part 1, Part 2 Cloud Run Beyond Goldilocks Reliability by Narayan Desai, Google Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation by Jez Humble and David Farley Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers) by Michael T. Nygard DevOps Days On the Care and Feeding of Feedback Cycles by Elisabeth Hendrickson at FlowCon San Francisco 2013 Bret Victor Inventing on Principle by Bret Victor Media for Thinking the Unthinkable Douglas Engelbart and The Mother of All Demos 18F Pain Is Over, If You Want It at DevOps Enterprise Summit - San Francisco 2015 Goto Fail, Heartbleed, and Unit Testing Culture by Mike Bland Do Developers Discover New Tools On The Toilet? by Emerson Murphy-Hill, Edward Smith, Caitlin Sadowski, Ciera Jaspan, Collin Winter, Matthew Jorde, Andrea Knight, Andrew Trenk and Steve Gross PDF Study: DevOps Can Create Competitive Advantage DevOps Means Business by Nicole Forsgren Velasquez, Jez Humble, Nigel Kersten and Gene Kim Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren, PhD, Jez Humble, and Gene Kim DevOps Research and Assessment (DORA) on Google Cloud GitLab Inc. takes The DevOps Platform public Paul Strassmann The Idealcast with Dr. Ron Westrum: Part 1, Part 2 Building the Circle of Faith: How Corporate Culture Builds Trust at Trajectory Conference 2021 The Truth About Burnout: How Organizations Cause Personal Stress and What to Do About It by Christina Maslach and Michael P. Leiter Maslach Burnout Inventory Understanding Job Burnout at DevOps Enterprise Summit - Las Vegas 2018 Understanding Job Burnout at DevOps Enterprise Summit - London 2019 Workplace Engagement Panel at DevOps Enterprise Summit - Las Vegas 2019 Expert Panel - Workplace Engagement & Countering Employee Burnout at DevOps Enterprise Summit - London 2019 The Idealcast with Trent Green Kelly Shortridge's tweets about Gitlab S-1   TIMESTAMPS [05:22] Intro [05:34] Meet Jez Humble [10:19] What Jez is working on these days [15:56] What inform his book, “Continuous Delivery” [24:02] Assembling the team for the project [26:30] At what point was PHP an important property [31:56] The most surprising thing since the DevOps Handbook came out [35:07] His favorite pattern that went into the DevOps Handbook [43:40] What DevOps worked on in 2021 [44:46] Meet Dr. Nicole Forsgren [50:32] What Dr. Forsgren is working on these days [52:18] What it's like working at Microsoft Research [55:58] The response to the state of DevOps findings [59:18] The most surprising finding since the findings release [1:05:59] Her favorite pattern that influence performance [1:08:49] How Dr. Forsgren met Dr. Ron Westrum [1:11:06] The most important thing she's learned in this journey [1:14:46] Her favorite case study in the DevOps Handbook [1:19:12] Dr. Christina Maslach and work burnout [1:20:46] More context about the case studies [1:25:32] The Navy case study [1:29:04] Outro

Dragan Stepanović is our guest, and he brings his heuristic: “Continuous code reviews enable higher team's throughput”. We dive into Dragan's research on how async code reviews affect the quality and throughput of teams that create and maintain software. He also shares how his research challenged some of his assumptions, and we finalise discussing his experiences bringing his research to management. Dragan recommends the following resources: The Principles of Product Development Flow from Donald G. Reinertsen The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win from Gene Kim, Kevin Behr and George Spafford The Goal from Eliyahu M. Goldratt Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation from Jez Humble and Dave Farley Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations from Nicole Forsgren, Jez Humble and Gene Kim Dragan (@d_stepanovic) is based in Berlin and currently works as a principal engineer at HelloFresh. Typically on the search for better ways of working, exploring ends of the spectrums, and helping teams and organisations try out counter-intuitive ideas that initially don't make a lot of sense but end up as completely opposite of that. It's been a long time since he fell in love with eXtreme Programming, Domain-Driven Design, and software as a craft (founder of Software Crafting Serbia community). In the last couple of years, he enjoys endless discussions connecting the Theory of Constraints, Systems Thinking, Lean and socio-technical topics.

Avsnitt 25 av UTVECKLA är här! Vi har haft förmånen att bli gästade av Martin Fredriksson som jobbar med Innovation Lead på Consid. Dagens ämne är Assemblerprogrammering och Multicloud. Vad innebär egentligen dessa två? Och vad är fördelarna kontra nackdelarna med dem? Frågor som dessa besvaras i dagens samtal med Martin. Trevlig lyssning! Höjdpunkter från avsnittet: [06:50] - Vem är Martin Fredriksson? [08:30] - Martin har precis fått igång en Commodore 64 som han ska använda för att bygga upp ett spel med hjälp av Assemblerprogrammering. Här berättar han mer om detta projekt. [15:00] - Vilka är fördelarna kontra nackdelarna med assemblerprogrammering? [26:25] - Vad är multicloud för något? Och varför använder man sig av detta? [40:45] - Hur kostnadseffektivt är det egentligen med multicloud? [42:20] - Hur kommer man igång med sin multicloud-lösning? [47:15] - Så här ser framtiden ut inom assemblerprogrammering [49:45] - Hur påverkar forskningen våra molntjänster? [52:40] - Martin ger tips på två böcker inom programmering! Länkar till böcker:  Accelerate - the Science of Lean Software and Devops: Building and Scaling High Performing Technology Organizations  Measure what matters: The Simple Idea that Drives 10x Growth

Although it's a technical strategy, DevOps has implications beyond that. Namely: ➕ more focus on improving business ➖ less idling due to communication and collaboration breakdowns On the latest episode of PALOcast, Senior Developer & DevOps pro Jung Kim chats with host Ivy Chan about the crucial relationship between development and operations teams. He also details his experiences helping organisations move past dated software development processes and waterfall project management, and onto the greener pastures of DevOps practices.

Charles Flatt is joining the podcast today! He has been a software developer since 1994 and has helped over a dozen organizations succeed on over fifty projects, both small and large. Charles has an unusual breadth of business and personal experience from foodservice and retail to music, business management, hardware installation, and of course, software development.   In this episode, Charles talks about his learning as a developer and some of his successes, big lessons, and key takeaways from the course of his career. He shares actionable advice for developers, teams, and organizations on how to improve; his favorite resources and books for further learning;  the metrics that matter the most; and what he sees as being the key components of what makes a DevOps organization successful.   Topics of Discussion: [:38] Be sure to visit AzureDevOps.Show for past episodes and show notes. [1:00] About The Azure DevOps Podcast, Clear Measure, and Jeffrey’s offer to speak at virtual user groups. [1:24] Clear Measure is hiring! Be sure to check out the link in the show notes. [1:34] About today’s guest, Charles Flatt! [1:57] Jeffrey welcomes Charles to the podcast. [2:34] Charles shares his career journey before software development and how he began his career in software. [6:49] Charles speaks about where he has worked and what he has been working on in the last decade. [11:48] Charles shares some of the big lessons and key takeaways from the course of working on over fifty projects in software development. [18:21] Charles and Jeffrey discuss their favorite books on DevOps and give their recommendations on what you should be reading as a developer today. [20:50] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [21:22] What Charles sees as needing to change within an organization in order to become more successful. [23:01] Charles gives some actionable advice on how to begin improving as a developer, as a team, and as an organization. [28:06] Charles and Jeffrey discuss the metrics that matter the most. [29:18] Jeffrey and Charles discuss the importance of continuous integration and what it really means to do continuous integration. [32:32] Charles recommends some go-to resources to check out after today’s podcast! [34:33] Jeffrey thanks Charles for joining the podcast!   Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! The Azure DevOps Podcast’s Twitter: @AzureDevOpsShow Charles Flatt’s LinkedIn Azure DevOps Podcast Ep. 33: “Rockford Lhotka on Software Architecture” Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD The Phoenix Project (A Novel About IT, DevOps, and Helping Your Business Win), by Gene Kim The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Continuous Integration: Improving Software Quality and Reducing Risk, by Paul M. Duvall, Steve Matyas, and Andrew Glover Good Habits, Bad Habits: The Science of Making Positive Changes That Stick, by Wendy Wood Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs, by John Doerr   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Τι επιλογές έχει ένας προγραμματιστής για την εξέλιξη του σε μία σύγχρονη εταιρεία. Από junior μέχρι VP. Δήλωσε συμμετοχή στο Laravel, React ή Docker #workshop: http://bit.ly/sn-workshops-y Ή πες μας τι workshop θες: bit.ly/WhatWorkshopSN Δες το video -> https://youtu.be/EieMyOU4Dfo Accelerate: The Science of Lean Software and Devops: Building and Scaling High Performing -> https://amzn.to/35fzv29

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.   A team Oskar worked with, was complaining about the meetings and wanted to stop some of those. Over time, the team members started not showing up, or showing up and not participating actively in the meeting. As the team was delivering, no one else saw this was a problem, but Oskar knew that this was not a team, it was just a group of individuals. In this episode, we talk about how to motivate a team and the importance of having a Vision that brings the team members together.  In this segment, we refer to the FREE Create A Compelling Product Vision e-course.  Featured Book of the Week: Accelerate by Nicole Forsgren In Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren, Oskar found a book that helped him explain the Agile mindset to technical people. He also understood the role of DevOps in an Agile organization. The biggest takeaway? Listen in to learn what was Oskar’s biggest takeaway. In this segment, we also talk about the #NoEstimates book, and how that influenced Oskar’s career.    About Oskar Collin Oskar is a former software developer who became a passionate agile coach and Scrum master. He did so mainly because he was better at helping teams working together than building software. He loves experiments and questioning the status quo. He is passionate about helping teams build digital products and deliver value continuously.  You can link with Oskar Collin on LinkedIn and connect with Oskar Collin on Twitter.

Sponsored by Linode Panelists Allen "Gunner" Gunn | Justin Dorfman | Pia Mancini | Richard Littauer Guest Tobie Langel Show Notes Welcome to Sustain! On today’s episode, we have special guest, Tobie Langel, the Founder of UnlockOpen, from Geneva, Switzerland. Tobie tells us all about UnlockOpen and what he does there. He tells us how he focuses on convincing companies that they need to contribute back to Open Source. Other topics we will talk about are DevOps culture, prototype JavaScript framework not being updated since 2015, which Tobie extensively explains what happened, as well as speaking about lessons to be learned and things we need to be aware of. There is so much great advice and stories shared on this episode. Download it now! [00:01:19] Tobie tells us about UnlockOpen and what he does. [00:02:30] Richard wants to know how do you get in the door as a consultant to try to talk to people about how they should use Open Source and how do you pitch that to people that don’t know what Open Source is? [00:08:04] Tobie discusses how he focuses on convincing companies that they need to contribute back to Open Source. Pia wonders if Tobie thinks we’re making progress towards cultural changes within the audience? [00:12:10] Allen asks Tobie if he’s advancing the notion of DevOps as a gateway drug for all of this open culture. Tobie mentions a book he’s reading called, Accelerate, that_ _talks about the benefits of DevOps culture to companies from a business perspective. [00:14:13] Justin wants to know where Tobie got his kind of background and he also wonders about project abandonment, and prototype JavaScript framework hasn’t been updated since 2015. So, what happened there and what lessons could be learned? [00:24:06] Tobie speaks about learning from history, about lessons to be learned, and things we have to be aware of. [00:26:06] Tobie mentions how he’s a huge fan of DHH and Basecamp and he gives some great advice that he’s learned on focusing on things that matter long term. Justin and Richard also have some positive advice and stories to share as well. [00:35:25] Richard makes an awesome statement here about being resilient. [00:36:20] Tobie tells us where we can find him to learn more about him. Spotlight [00:38:03] Justin’s spotlight is our first bonus podcast episode (#41) with Dave Gandy, and we discussed Font Awesome 6, the donut diet, commitments, and more. Check it out! ☺ [00:42:23] Allen’s spotlight is Open Tech Fund. [00:38:56] Richard’s spotlight is Aral Balkan, a cyborg rights activist. [00:39:17] Toby’s spotlight is a book by Nadia Eghbal called, Working in Public: The Making and Maintenance of Open Source Software. Quotes “It boils down to bottom line and top line. To some degree it’s more than that, obviously, culture, brand, making people feel happy to work in a company. All of those are critical for a company.” [00:10:45] “And we are at the point where we need to cross the chasm. So maybe move that from being something that is essentially something adopted by a few really performant companies at the helm of this effort and move that across to become more mainstream. [00:16:47] “And so the funny thing is I essentially learned JavaScript by reading the source code because there was no documentation and I started contributing to the library by writing documentation for it.” [00:17:44] “It took a lot of time for Sam to realize that he was burning out and just couldn’t spend the time that was needed to give more authority to other people on the project.” [00:21:58] “There was a lot of energy, and people are ready to do a lot of things for the rocket ship because you also benefit personally quite a bit when you’re investing your time in a rocket ship.” [00:25:19] “This goes right to the heart of what we’re trying to talk about here. And so I think one of the things that I’m really picking up from what you’re saying is that it’s better to dedicate yourself towards an ideology of working well in the open, of working with other people, of trying to consistently not just stay ahead of the curve, but work in a way that what you do will matter later.” [00:34:20] “At the same time you could carry that comparison even further kind of ad absurdum, like everything’s the same, because we all need to eat and we all get tired and we all get sleepy and we all get hungry, we’re all kind of anxious and we have to work with other people and what wears kind of annoying and it’s pretty tough.” Links Tobie Langel Twitter (https://twitter.com/tobie?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) UnlockOpen (https://unlockopen.com/) Sustain Podcast-Episode 41: The Donut Diet, Commitments. and More Awesomeness with Dave Gandy (https://fireside.fm/s/fxw-Bcan+HH3L5owT) Open Technology Fund (https://www.opentech.fund/) Aral Balkan (https://ar.al/) [Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal](https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862/ref=sr12?dchild=1&keywords=working+in+public%3A+the+making&qid=1592942530&sr=8-2) [Accelerate: The Science of Lean Software and DevOps:Building and Scaling High Performing Technology Organizations by Nicole Forsgren, PhD](https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr12?dchild=1&keywords=accelerate&qid=1592942345&sr=8-2) Credits Produced by Justin Dorfman (https://www.justindorfman.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Ad Sales by Eric Berry Special Guest: Tobie Langel.

In this episode of Adventures in DevOps the pane interviews Adam Nowak. Adam is a part of the DevOps team at Netguru. He joins the panel today to share his DevOps transformation story. Adam starts by explaining the title he chose for today’s episode. He also shares his definition of DevOps. Adam explains the age-old story of a misunderstood DevOps team that was overworked and underappreciated. The organization grew but the DevOps team didn’t scale with it, leaving them with piles of tickets and everyone else wondering what was taking so long. The panel commiserates with Adam and shares some of their own similar stories.  Reaching out to others to help solve the problem, Adam found that many DevOps teams had and are experiencing the same problem. He found help from others in the DevOps space and recommended books. His team started by making their work more visible. To do this they streamlined their communication and published documentation.  Next, they made more focused goals. Instead of trying to do everything and never meeting their goals they chose a couple things to work on and focused on that. Another change they made was to diversify their meetings, projects, and initiatives; they brought in people from all the teams to collaborate, making the projects even better.  The panel discusses the importance of empathy in the workplace and in life. Most people are trying their best and probably have a reason for doing the things that they are doing. Instead of treating others as if they are incompetent, talk them and discuss the reasons behind their actions and decisions.  Panelists Nell Shamrell-Harrington Charles Max Wood Guest Adam Nowak Sponsors CacheFly Links How we killed DevOps by creating a dedicated DevOps team | Adam Nowak The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win  Making Work Visible: Exposing Time Theft to Optimize Work & Flow  The Goal: A Process of Ongoing Improvement   The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations  Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs  Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations  Switch: How to Change Things When Change Is Hard  https://www.facebook.com/Adventures-in-DevOps-345350773046268/ Picks Charles Max Wood: Holiday Inn  White Christmas  The MaxCoders Guide To Finding Your Dream Developer Job  Nell Shamrell-Harrington: The Mandalorian Rust in Motion  Adam Nowak: Why We Sleep: Unlocking the Power of Sleep and Dreams Jabra Elite 85h Wireless Noise-Canceling Headphones

In this episode of Adventures in DevOps the pane interviews Adam Nowak. Adam is a part of the DevOps team at Netguru. He joins the panel today to share his DevOps transformation story. Adam starts by explaining the title he chose for today’s episode. He also shares his definition of DevOps. Adam explains the age-old story of a misunderstood DevOps team that was overworked and underappreciated. The organization grew but the DevOps team didn’t scale with it, leaving them with piles of tickets and everyone else wondering what was taking so long. The panel commiserates with Adam and shares some of their own similar stories.  Reaching out to others to help solve the problem, Adam found that many DevOps teams had and are experiencing the same problem. He found help from others in the DevOps space and recommended books. His team started by making their work more visible. To do this they streamlined their communication and published documentation.  Next, they made more focused goals. Instead of trying to do everything and never meeting their goals they chose a couple things to work on and focused on that. Another change they made was to diversify their meetings, projects, and initiatives; they brought in people from all the teams to collaborate, making the projects even better.  The panel discusses the importance of empathy in the workplace and in life. Most people are trying their best and probably have a reason for doing the things that they are doing. Instead of treating others as if they are incompetent, talk them and discuss the reasons behind their actions and decisions.  Panelists Nell Shamrell-Harrington Charles Max Wood Guest Adam Nowak Sponsors CacheFly Links How we killed DevOps by creating a dedicated DevOps team | Adam Nowak The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win  Making Work Visible: Exposing Time Theft to Optimize Work & Flow  The Goal: A Process of Ongoing Improvement   The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations  Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs  Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations  Switch: How to Change Things When Change Is Hard  https://www.facebook.com/Adventures-in-DevOps-345350773046268/ Picks Charles Max Wood: Holiday Inn  White Christmas  The MaxCoders Guide To Finding Your Dream Developer Job  Nell Shamrell-Harrington: The Mandalorian Rust in Motion  Adam Nowak: Why We Sleep: Unlocking the Power of Sleep and Dreams Jabra Elite 85h Wireless Noise-Canceling Headphones

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.  What happens when a team member who joined as a “gift” from management fails to keep the standard expects from each of the team members? If you add to this, the fact that some team members become vocal about the problem, but others don’t even want to touch the subject, you have all the ingredients you need for massive conflict. What can a Scrum Master do? Listen in to learn how Dmytro, the Scrum Master helped the team get out of this negative spiral.  Featured Book for the Week: Accelerate, by Nicole Forsgren et al. Dmytro’s recommendation is the book by Gene Kim, Jez humble and Nicole Forsgren, Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations. In Accelerate, Dmytro found many inspirational stories and anecdotes that helps him improve the organization and the teams he works with. Dmytro also recommends Scrum, the art of doing twice the work in half the time by Sutherland. In this book he highlights the many real-life examples. Additionally, Dmytro refers to The DevOps Handbook by Gene Kim, a book he describes as filled with technical practices that teams can apply.   About Dmytro Balaba Dmytro calls himself one of the most dedicated Scrum Masters/Agile Coach in the world :) On his right-hand he has a tatoo with golden ratio, Fibonacci sequence. After almost 15 years of work in IT management Dmytro found himself balanced and happy. He’s been a full-time Scrum Master for more than 3 years. You can link with Dmytro Balaba on LinkedIn and connect with Dmytro Balaba on Twitter.

In today’s episode, Dan Neumann is joined by Steven Granese, the Vice President of the Transform Practice at AgileThought! As the VP of Transform Practice, Steven leads a team of the top Agile Coaches, DevOps Consultants, and Product Consultants in the United States.   Together, Dan and Steven will be exploring the ‘why’ behind Scrum and examing the question of why organizations and teams should be using Scrum, in the first place. Steven often sees that the clients he’s working with lose focus on the ‘why’ behind Scrum or don’t even know what it is, to begin with! With these clients, there will be a lot of focus on the mechanics of Scrum and the framework itself (i.e. the ‘how’) without a deep understanding of why they’re using Scrum, what problems they’re trying to solve with Scrum, and what their purpose is for working with sprints with iterations. In this episode, Steven addresses how organizations can shift their perspective from a ‘how’ mentality to a ‘why’ mentality as well as many of the misconceptions and incorrect uses of Scrum (so you can be sure to avoid them!)   Key Takeaways Why it is important to focus on the ‘why’ behind Scrum rather than the ‘how’: The ‘why’ helps the team and organization understand what problem they’re trying to solve with Scrum in the first place Focusing on the ‘how’ (such as: “How do we execute Scrum?”) leads to organizations applying Scrum incorrectly Understanding the ‘why’ leads to a deeper understanding of why they’re using Scrum, the problems they’re trying to help solve with it, and what their purpose is in working with sprints and iterations The ‘why’ behind Scrum and where it makes the most sense to use: In conditions of high uncertainty In environments of high uncertainty Incorrect ways Steven sees Scrum being applied: As opposed to building a working increment of their product, getting feedback as they go, and adjusting their sprint-to-sprint plan based on the feedback (which is the heart and soul of the ‘why’ behind Scrum), they’re not allowing feedback into the process — therefore losing the ‘why’ in the process Breaking up work into milestones instead of sprints Treating the sprint demo like a sales pitch and not letting the customer experience the demo for themselves Techniques and tips for achieving the ‘why’ behind Scrum: Recognize that the market moves fast, there’s a lot of uncertainty in the world, and that the customer’s needs are changing very quickly Match the way you think about your work and deliver your work to that uncertainty (which allows you to move faster) Stop overplanning and just start working Put increments of the product into the customers’ hands and start getting their feedback Get back to the basics and simply focusing on two weeks at a time Measuring the right metrics (“You get what you measure”) Don’t just use Scrum to measure the team; use it to measure the flow of the entire system Focus on getting really quality feedback from your customers “Begin with the end in mind.” — Stephen Covey Through receiving high-quality, real feedback from a sprint demo, really listen to the feedback and adjust the plan and fix problems accordingly Understand where the market is headed (and differentiate between what the customer wants and what is actually needed) by building something and putting it in their hands to get feedback Fail fast to learn fast Build in thin slices and get feedback as you go — you will learn a ton about what users actually need and also save time by not building unneeded features Misconceptions about the Scrum framework: That Scrum is really about product delivery (“Scrum is just as much about discovering the solution as it is about delivering the solution” — Steven Granese) Scrum and other Agile frameworks are seen as a delivery mechanism (as opposed to a mechanism to discover what the customer actually needs) That you have to use Scrum (if you already know exactly what you need to build and there’s no uncertainty then there’s no need for the iterative nature of Scrum)   Mentioned in this Episode: Steven Granese Stephen Covey “Wagile” (Waterfall Agile)   Steven Granese’s Book Picks: The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren, Jez Humble, and Gene Kim   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Robby speaks with Matt Weagle, Engineering Manager at Lyft. Matt discusses how his engineering teams have handled technical debt in small iterations vs. a major rewrite, why a whiteboard is the best tool for architectural challenges, and the most common mistakes he sees when engineers approach legacy code bases. Helpful Links: Follow Matt on Twitter Matt on LinkedIn Some Thoughts on Security After 10 Years of Gmail A Taxonomy of Yak Shaving [Book] The Manager's Path by Camille Fournier [Book] Release It!: Design and Deploy Production-Ready Software by Michael T. Nygard [Book] The Phoenix Project, A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim , Kevin Behr [Book] The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity by Alan Cooper [Book] Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren Subscribe to Maintainable on: Apple Podcasts Overcast Or search "Maintainable" wherever you stream your podcasts. Loving Maintainable? Leave a rating and review on Apple Podcasts to help grow our reach. Brought to you by the team at Planet Argon.

Today’s episode is all about recognizing middle-of-the-day deployments; how teams such as Netflix, Facebook, and even the Azure DevOps Product Team are doing them; and taking a look at how other teams can achieve that for themselves!   Jeffrey Palermo’s guest today is Eric Fleming, a Software Architect at Clear Measure. Eric leads an intense team, developing and operating a mission-critical software system in the financial sector. He lives in Alpharetta, Georgia, and is a host of the Function Junction Youtube Channel, which is all about Azure functions. He’s also written articles for MSDN Magazine and CODE Magazine.   In this episode, Eric takes Jeffrey through his journey of inheriting a monolithic software system and the major transformations he had to execute to get it where it is today; deploying in the middle of the day! He explains the key steps he took in breaking up the monolith, the development process, who was involved, what the structure and DevOps environments looked like, and all of the details you need to know if you’re finding yourself in a similar situation!   Topics of Discussion: [:52] How to get your hands on Jeffrey’s book, .NET DevOps for Azure. [2:04] About today’s episode and featured guest. [3:00] Jeffrey welcomes Eric to the podcast! [3:06] Eric begins the story of how he inherited a software system and the journey it took getting it to deploy in the middle of the day. [9:58] Fast forward to today, what does this software system look like now? [11:50] What does Eric attribute to his ability to handle a high-throughput in only four app servers? [15:52] Eric’s process for deploying the 50-sum processes that need to be deployed. [17:32] A word from Azure DevOps sponsor: Clear Measure. [17:59] Eric speaks about their Git Repositories. [19:25] Eric explains what the structure and DevOps environments of one of his applications looks like (that is a Windows service with its own Git Repository). [21:45] Who is involved whenever part of the system is being deployed? [25:37] Has there been development process differences during their monthly deployments/monolith time? [26:22] Now that they are shipping every day/whenever they need to, what has become of their sprints? And how do they get some features done in just a day and ready to deploy within days? What does this look like and how do they implement this pattern? [31:50] Do sprints even exist in this new world? [33:31] The major transformations that Eric had to execute to get to where he is today with the software system, and some of the first steps he took to breaking up the monolith. [36:27] Would Eric have been able to start breaking the monolith apart if he didn’t have automated tests? [38:47] Resources Eric recommends to listeners in a similar situation to where he was!   Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) — Reach out to Jeffrey @JeffreyPalermo on Twitter if you have a user group or conference and would like some free copies of .NET DevOps for Azure! .NET DevOps for Azure, by Jeffrey Palermo bit.ly/dotnetdevopsproject — Visit for an example of .Net DevOps for Azure Function Junction Youtube Channel MSDN Magazine CODE MagazineEric Flemming’s Twitter: @EFleming18 NServiceBus Particular SoftwareTeamCity Octopus Deploy Sumo Logic New Relic Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD, Jez Humble, and Gene Kim The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Your host, Dan Neumann, is excited to bring you two guests for this week’s episode — repeat guest, Eric Landes, and Barry Matheney. Eric and Barry are both Agile thinkers, experts in the DevOps space, and colleagues of Dan at AgileThought.   Eric Landes is a Scrum.org certified professional Scrum trainer and currently serves as a Senior DevOps Consultant, ALM Director, and Solutions Architect. Barry also is a Senior DevOps Consultant. Previously to his role at AgileThought, he served as Director Enterprise Applications at Kforce Inc.   Today, they’re talking about DevOps and the importance of having it on Scrum teams. They cover whether it is good or bad that there are barriers between Agile, Scrum, and DevOps; what well-functioning Scrum teams look like when they have a DevOps skillset embedded into them; how to incorporate DevOps into organizations; what a DevOps skillset could bring to a team; and how DevOps can fit into even the most traditional of companies.   Key Takeaways Is it good or bad that there are barriers between Agile or Scrum and DevOps? It is disadvantageous to separate DevOps from Agile or Scrum because it is important that your team has all the skills they need to deliver software You need the DevOps skillset on your team and it should be a goal to incorporate it What do well-functioning Scrum teams look like when they have DevOps skillsets embedded into them? Self-sufficient Not limited by dependence on other teams or organizations Eliminates walls and allows for continuous delivery How to incorporate DevOps into organizations: Use baby steps Use it to inform the beginning of the development cycle and product decisions down the line What the DevOps skillset brings to a team: Experimentation or hypothesis-driven development Rapid deployment and continuous delivery Tons of not-so-visible benefits (such as auditing, compliance, security, deployability, and testability) How DevOps can fit into traditional companies: Remove constraints (such as specific deployment dates) Automate the value the compliance brings   Mentioned in this Episode: Eric Landes (LinkedIn) Barry Matheney (LinkedIn) The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Podcast Ep. 9: “Exploring Expert Facilitation Tips with Adam Ulery” SRE — Site Reliability Engineering Cowboy coding   Eric Landes and Barry Matheney’s Book Picks The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done, by Stephen Denning Lean Enterprise: How High Performance Organizations Innovate at Scale, by Jez Humble, Joanne Molesky, and Barry O’Reilly Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD, Jez Humble, and Gene Kim Outliers: The Story of Success, by Malcolm Gladwell   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Do 203. dílu jsme pozvali Lukáše Křečana, Martina Damovského a Zdeňka Mertu a bavili se o testování na produkci. Techniky (postupy) - Canary release https://martinfowler.com/bliki/CanaryRelease.html - Blue Green deployment https://martinfowler.com/bliki/BlueGreenDeployment.html - A/B testing https://en.wikipedia.org/wiki/A/B_testing - Tap recording - Shadowing http://blog.christianposta.com/microservices/advanced-traffic-shadowing-patterns-for-microservices-with-istio-service-mesh/ - Feature toggles https://martinfowler.com/articles/feature-toggles.html - Synthetics (Specialni ucty) - Exploration Testing https://en.wikipedia.org/wiki/Exploratory_testing - Chaos testing https://principlesofchaos.org Nástroje - Diffy https://github.com/twitter/diffy - Istio https://istio.io Zdroje Knihy - The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations - Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations - Lean Enterprise: How High Performance Organizations Innovate at Scale - Building Microservices: Designing Fine-Grained Systems Články - https://medium.com/@copyconstruct/testing-in-production-the-safe-way-18ca102d0ef1 - https://blog.turbinelabs.io/deploy-not-equal-release-part-one-4724bc1e726b - https://blog.turbinelabs.io/deploy-not-equal-release-part-two-acbfe402a91c - https://martinfowler.com/articles/microservice-testing/ - http://blog.christianposta.com/microservices/advanced-traffic-shadowing-patterns-for-microservices-with-istio-service-mesh/ - https://githubengineering.com/move-fast/

with Nicole Forsgren (@nicolefv), Jez Humble (@jezhumble) and Sonal Chokshi (@smc90) From the old claim that "IT doesn't matter" and question of whether tech truly drives organizational performance, we've been consumed with figuring out how to measure -- and predict -- the output and outcomes, the performance and productivity of software. It's not useful to talk about what happens in one isolated team or successful company; we need to be able to make it happen at any company -- of any size, industry vertical, or architecture/tech stack. But can we break the false dichotomy of performance vs. speed; is it possible to have it all?  This episode of the a16z Podcast boldly goes where no man has gone before -- trying to answer those elusive questions -- by drawing on one of the largest, large-scale studies of software and organizational performance out there, as presented in the new book, Accelerate: The Science of Lean Software and DevOps -- Building and Scaling High Performing Technology Organizations by Nicole Forsgren, Jez Humble, and Gene Kim. Forsgren (co-founder and CEO at DevOps Research and Assessment - DORA; PhD in Management Information Systems; formerly at IBM) and Humble (co-founder and CTO at DORA; formerly at 18F; and co-author of The DevOps Handbook, Lean Enterprise, and Continuous Delivery) share the latest findings about what drives performance in companies of all kinds. But what is DevOps, really? And beyond the definitions and history, where does DevOps fit into the broader history and landscape of other tech movements (such as lean manufacturing, agile development, lean startups, microservices)? Finally, what kinds of companies are truly receptive to change, beyond so-called organizational "maturity" scores? And for pete's sake, can we figure out how to measure software productivity already?? All this and more in this episode!