POPULARITY
What are the top books that every legal leader needs to read to succeed in the new year? At the close of each episode, Tyler asks our guests what book they would recommend to our audience, and we're kicking off 2025 with this year's list of must-read books that you need to check out. Listen to hear titles that these CEOs, start-up founders, and GCs can't live without. Read detailed summary: https://www.spotdraft.com/podcast/episode-75 Topics: Introduction: 0:00 Joe Green, Chief Innovation Officer Gunderson Dettmer, recommends Leading Professionals: Power, Politics, and Prima Donnas by Laura Empson: 0:42 Rachel Olchowka, General Counsel & Chief People Officer at Fetch recommends Powerful: Building a Culture of Freedom and Responsibility by Patty McCord: 1:34 Dan Haley, General Counsel at Guild Education recommends Helping Your Business Win by Gene Kim, Kevin Behr, George Spafford: 2:39 Chelsea Grayson, Managing Partner at Pivot, recommends Quench Your Own Thirst: Business Lessons Learned Over a Beer or Two by Jim Koch: 5:51Aaron Gregory, CEO of Upwardly, recommends The Right It: Why So Many Ideas Fail and How to Make Sure Yours Succeed by Alberto Savoia: 7:38Jasmine Singh, General Counsel at Ironclad, recommends The Practice of Groundedness: A Transformative Path to Success That Feeds--Not Crushes--Your Soul by Brad Stulberg: 10:03Sean West, Co-Founder of Hence Technologies, recommends The Coming Wave: Technology, Power, and the Twenty-first Century's Greatest Dilemma by Michael Bhaskar and Mustafa Suleyman: 12:56Jules Polonetsky, CEO of Future of Privacy, recommends: Privacy Is Hard and Seven Other Myths by JH Hoepman: 14:17Heath Tarbert, Chief Legal Officer at Circle, recommends The Enchiridion of Epictetus: 14:57Matt Tanielian, Co-Founder of Franklin Square Group, recommends How to Talk Dirty and Influence People: An Autobiography by Lenny Bruce: 16:21Connect with us: Tyler Finn - https://www.linkedin.com/in/tylerhfinn SpotDraft - https://www.linkedin.com/company/spotdraft SpotDraft is a leading contract lifecycle management platform that solves your end-to-end contract management issues. Visit https://www.spotdraft.com to learn more.
Folge 41 beschäftigt sich mit der Frage, wie die IT-Funktion zum Alleinstellungsmerkmal von Unternehmen beitragen kann. Zu Gast ist Annette Hamann, CIO von Beiersdorf und Geschäftsführerin der BSS IT, der Beiersdorf Shared Services. Annette und ihr Team bei BSS verantworten die IT-Funktion für Beiersdorf. Das Team ist für alle IT-Initiativen zuständig und richtet die IT-Infrastruktur und den IT-Betrieb an der Strategie und dem Geschäftsmodell des Konzerns aus. Uli, Markus und Annette diskutieren über die Notwendigkeit, dass sich die IT vollständig mit den Geschäftsprioritäten identifizieren muss, um einen echten Beitrag zur Gestaltung und Verbesserung des Geschäftsmodells leisten zu können. Annette betont, dass diese Ausrichtung eine adäquate Struktur, gezielte Investitionen und den Aufbau entsprechender Kompetenzen erfordert. Das Gespräch mit den beiden CIOs macht deutlich, dass die IT schneller und offensichtlicher Nutzen und Mehrwert bringt, wenn sie eng mit den verschiedenen Abteilungen zusammenarbeitet. Wer mehr wissen möchte, findet hier weitere Informationen: - Beiersdorf und und Beiersdorf Shared Services Angebot https://www.beiersdorf.de und Beiersdorf Shared Services GmbH (BSS) - Literaturhinweis: „The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win“ von Gene Kim, Kevin Behr, and George Spafford https://amzn.eu/d/ftlmCst - Literaturhinweis. „Digital Transformation: Survive and Thrive in an Era of Mass Extinction“ von Thomas M. Siebel https://amzn.eu/d/aGnWsb3 - Literaturhinweis: „The New IT: How Technology Leaders are Enabling Business Strategy in the Digital Age“ von Jill Dyche https://amzn.eu/d/3GSzH9h - Literaturhinweis: „Leading Digital: Turning Technology into Business Transformation“ von George Westerman, Didier Bonnet, and Andrew McAfee https://amzn.eu/d/dI8iJ9n - Literaturhinweis: „The CIO's Guide to Breakthrough Project Portfolio Performance: Applying the Best of Critical Chain, Agile, and Lean“ https://amzn.eu/d/5X1eNF5 - Literaturhinweis: CIO-Magazin https://www.cio.de Euer Feedback zur Folge und Vorschläge für Themen und Gäst:innen sind sehr willkommen! Vernetzt euch und diskutiert mit: - Annette Hamann: https://www.linkedin.com/in/annette-hamann-0549883/ - Ulrich Irnich: https://www.linkedin.com/in/ulrichirnich/ - Markus Kuckertz: https://www.linkedin.com/in/markuskuckertz/ Mitwirkende - Hosts: Ulrich Irnich & Markus Kuckertz // Produktion: Daniel Sprügel, Maniac Studios (https://maniacstudios.com/) // Redaktion: Marcus Pawlik © Digital Pacemaker Podcast 2023
Today we're talking to George Spafford, Vice President Analyst at Gartner. We discuss the lessons George learned from his worldwide travels as a young man, the real value of AI when pitted against massive amounts of data, and why even the most transformative AI may not destroy the world after all. All of this right here, right now, on the Modern CTO Podcast! For more about Gartner, check out their website here. Have feedback about the show? Let us know here. Produced by ProSeries Media. For booking inquiries, email booking@proseriesmedia.com
On today's show, we have our first book club discussion about The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win by authors Gene Kim, Kevin Behr, and George Spafford. We review chapters 3-6 and talk about how Adam's recent compliance work has given him a fresh perspective on the 190-page spreadsheet of vulnerabilities portrayed in the book. It's interesting how a security team can have a deeply collaborative relationship with a company that feels, at least for some, to be purely adversarial.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.
Тайминг 00:00:00 Вступление 00:00:31 Слишком много Вити 00:01:27 40й выпуск! 00:01:46 Гость в DKT - Вячеслав Мацукевич (https://www.linkedin.com/in/viachaslau-matsukevich/) 00:04:11 Цель выпуска 00:05:07 Как Слава создавал DevOps школу внутри компании 00:05:58 Почему хотели переучать dev-ов в DevOps? 00:07:10 Легко ли научить dev-ов OPS-у? 00:09:50 Cравнение c EPAM school 00:11:32 Что мотивировало учиться? 00:14:26 Немного о Сашином опыте преподавания 00:16:53 Как попадают в школу к Славе? 00:18:03 Как придумали программу школы? 00:20:28 Курсы от вендоров 00:21:22 У каждого свой подход 00:22:35 Social learning подход 00:26:00 Критерии успешного завершения 00:30:55 Что Славу мотивировало делать школу? 00:34:12 Почему Саша пошел преподавать? 00:38:51 Professional growth во время преподавания 00:40:24 Эффективные подходы для обучения DevOps 00:53:47 Как переход в онлайн повлиял на обучение 00:56:36 Курс на Udemi от Славы 01:04:10 Планы на будущее 01:05:48 Новые курсы для известных технологий 01:13:15 Не утонуть в обилии информации 01:17:46 Top-3 книги от гостя 01:21:56 3 youtube канала, 3 курса 01:25:51 Как качать Soft skills 01:31:40 Как попаcть в DKT Топ 3 канала Youtube: ⏩ Кирил Семаев https://www.youtube.com/c/KirillSemaev ⏩ ADV-IT https://www.youtube.com/c/ADVIT4000 ⏩ HighLoad https://www.youtube.com/c/HighLoadChannel Топ 3 курса:
Three members of the CyberWire's Hash Table of experts: Rick Doten Kevin Ford Kevin Magee discuss SOAR tools. Resources: “A Brief History of SIEM,” by Stephen Gailey, CyberSecurity Magazine, 19 January 2020. “Cybersecurity First Principles: DevSecOps.” by Rick Howard, CSO Perspectives, The CyberWire, 8 June 2020. "Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains,” by Eric Hutchins, Michael Cloppert, Rohan Amin, Lockheed Martin Corporation, 2010, last visited 30 April 2020. “Site Reliability Engineering: How Google Runs Production Systems,” by Betsy Beyer, Chris Jones, Jennifer Petoff, and Niall Richard Murphy, Published by O'Reilly Media, 16 April 2016. “The Cybersecurity Canon: The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win,” book review by Rick Howard, Palo Alto Networks, 21 October 2016. “The Evolution of SOAR Platforms,” by Stan Engelbrecht, SecurityWeek, 27 July 2018. “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win,” by Gene Kim, Kevin Behr, George Spafford, Published by IT Revolution Press, 10 January 2013.
Peter and Dave talk about the importance of managing SPOF (Single Point Of Failure) this week. This issue can have a negative effect on an organization if not handled correctly, so stay tuned! This week takeaways: A single point of failure in an organization does not mean that organization has failed. Identify them. Build redundancy or slack into the system Encourage the habit of continuously sharing knowledge References in this episode: The Phoenix Project- by Gene Kim, Kevin Behr, George Spafford - https://www.goodreads.com/book/show/17255186-the-phoenix-project We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com
What is cloud computing? How do you get started in tech with no past experience? Meet Joshua "TechDev" Walker, a senior cloud engineer, diversity advocate, and the author of “Venti Fried Chicken." He is also the co-founder of Black Orlando Tech and an Army veteran. Joshua is passionate about demystifying the tech industry and promoting diversity. In this episode, we talk about cloud computing: what it is, how it works, and what resources you need to start learning. We discuss the similarities and differences between the various cloud computing services and which certification exams you should take. We also dig into do-it-yourself careers and how to start your journey in tech with no prior experience. Joshua shares what inspired him to get into tech and why you should get into the industry too. Mentioned in This Episode: Black Orlando Tech: blackorlandotech.org freeCodeCamp: freecodecamp.org Pluralsight: Pluralsight Datacamp: datacamp.com A Cloud Guru (YouTube channel): bit.ly/3pZ1wlT AWS Cloud Practitioner Exam Pulp Fiction (Movie) Google SRE Book: sre.google/sre-book/table-of-contents/ "The Phoenix Project" by Gene Kim, Kevin Behr, George Spafford: bit.ly/2Pp15Fb Connect with Joshua: Buy Venti Fried Chicken on Amazon: amzn.to/3r2P99O Website: ventifriedchicken.com TikTok: @ventifriedchicken Instagram: @ventifriedchicken LinkedIn: /jwtechdev Follow Blossoming Technologist: Instagram: @blossomingtechnologist Twitter: @blssmngtchnlgst LinkedIn: /blossoming-technologist --- Support this podcast: https://anchor.fm/blossoming-technologist/support
Today, we are going to be talking with Dan Ayala a bit about what it’s like being a vCISO or Virtual CISO. Books mentioned in this episode: The Phoenix Project - Gene Kim, Kevin Behr, George Spafford
The three ways of DevOps comes from the Phoenix Project, a famous book in DevOps circle. This episode covers how to use the three ways to progress in your digital transformation initiatives. Sources: https://www.businessinsider.com/how-changing-one-habit-quintupled-alcoas-income-2014-4?r=US&IR=T https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/0988262592 https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations-ebook/dp/B01M9ASFQ3/ref=sr_1_1?crid=316RJMM06NH59&dchild=1&keywords=the+devops+handbook&qid=1600774333&s=books&sprefix=The+devops+h%2Cstripbooks-intl-ship%2C235&sr=1-1 Transcript: My first introduction to the principles behind DevOps came from reading The Phoenix Project by Gene Kim, Kevin Behr and George Spafford. In this seminal book, that blew my mind we follow Bill as he transforms Parts Unlimited through salvaging The Phoenix Project. An IT project that went so wrong, it could almost have been a project in the public sector. Through Bills journey to DevOps, we discover and experience the Three Ways of DevOps. In this episode, I cover the three ways of DevOps and how they can be applied in a Transformation. This is the DevOps Dojo #6, I am Johan Abildskov, join me in the dojo to learn. In the DevOps world, few books have had the impact of The Phoenix Project. If you have not read it yet, it has my whole-hearted recommendation. It is tragically comic in its recognizability and frustratingly true. In it, we experience the three ways of DevOps. The three ways of DevOps are Principles of Flow, principles of feedback and principles of continuous learning. While each of these areas support each other and has some overlap, we can also use them as a vague roadmap towards DevOps capabilities. The First Way of Flow addresses our ability to execute. The second way of Feedback concerns our ability to build quality in and notice defects early. The Third way of Continuous Learning focuses on pushing our organizations to ever higher peaks through experimentation. The first way of DevOps is called the principles of flow. The first way of DevOps is called the principles of flow. The foundational realization of the first way is that we need to consider the full flow from ideation until we provide value to the customer. This is also a a clash with the chronic conflict of DevOps with siloed Dev and Ops teams. It doesn't matter whether you feel like you did your part or not, as long as we the collective are not providing value to end-users. If you feel you are waiting a lot, try to pick up the adjacent skills so you can help where needed. We also focus on not passing defects on and automating the delivery mechanisms such that we have a quick delivery pipeline. Using Kanban boards or similar to visualize how work flows through our organization can help make the intangible work we do visible. A small action with high leverage is WIP limits. Simply limiting the amount of concurrent tasks that can move through the system at any point in time can have massive impact. Another valuable exercise to do is a Value Stream Map where you look at the flow from aha-moment to ka-ching moment. This can be a learning situation for all involved members as well as the organization around them. Looking at the full end to end flow and having optimized that we can move on to the second way of DevOps. The second way of DevOps is the Principles of Feedback The first way of DevOps enables us to act on information, so the second way focuses on generating that information through feedback loops, and shortening those feedback loops to be able to act on learning while it is cheapest and has the highest impact. Activities in the Second Way can be shifting left on security by adding vulnerability scans in our pipelines. It can be decomposing our test suites such that we get the most valuable feedback as soon as is possible. We can also invite QA, InfoSec and other specialist competences into our cycles early to help architect for requirements, making manual approvals and reviews less like to reject a change. Design systems are a powerful way to shift left as we can provide development teams with template projects, pipelines and deployments that adhere to desired guidelines. This enables autonomous teams to be compliant by default. The second way is also about embedding knowledge where it is needed. This is a special case of shortening feedback loops. This can both be subject matter expert knowledge embedded on full stack teams, but it can also be transparency into downstream processes to better allow teams to predict outcomes of review and compliance activities. A fantastic way of shifting left on code reviews, and improve knowledge sharing in the team is Mob Programming. Solving problems together as a team on a single computer. We can even invite people that are external to the team to our sessions to help knowledge sharing and to draw on architects or other key knowledge banks. Now that we have focused on our ability to create flow and feedback we can move on to the third and final way of DevOps. The principles of continuous learning. The first and second way of DevOps provide most of the technical capabilities for continuous learning and experimentation - so the hard work in the third way of DevOps is primarily cultural. Which makes it that much more difficult to do. A small step could be to start talking about hypotheses that we want to test rather than tasks we want to do. We have a tendency to state things as fact and put them into our backlogs. This creates an unfortunate mental model and Taylorist Command and Control culture. Language shape our thoughts so let's start phrasing our backlog items as hypothesis. Rather than saying "Make Button A Blue", say "We believe making Button A Blue will increase clickthrough rate by 10%." While the previous step can be useful the big theme in the third way is psychological safety. Making it safe to learn and experiment must be a priority if we want to have a healthy culture. We must make diversity a focus area, especially in the tech business we have a notoriously toxic culture. We can measure Westrum Culture as described in a previous episode, and seek to address any shortcoming. Learning, Diversity and Psychological safety must come from a leadership level exemplifying the virtues that the members of the organization must live. Otherwise, there will be no resilience and any benefits will be temporary. The impressive transformation of Alcoa embodies this perfectly. Another simple, but difficult practice is to drive down the size of the work items you are working on. This will make it easier to create small self-contained experiments. This will of course put stress on your software and organizational architecture.If you want to finish with a concrete technical practice look into Chaos Engineering as described in a previous Episode. Chaos Engineer will help build resilience into your organization and is a structured approach to create more learning. As such it can bring some safer sandbox to practice learning and experimentation. This can be beneficial if the organization is quite far from psychologically safe. The three ways of DevOps: Flow, Feedback and Learning are a meaningful definition of DevOps and it even hints at a roadmap for DevOps Transformations. Use the three ways and the activities I have described here as an inspiration to kickstart or accelerate your DevOps transformation! This has been the DevOpsDojo. You can follow me on twitter @randomsort. If you have any questions, feedback or just want to reach out and suggest a topic, do not hesitate. You can find show notes with transcripts, links and more at dojo.fm. Support the show by leaving a review, sharing this episode with a friend or colleague or subscribing to the DevOpsDojo on your favourite podcast platform. Thank you for listening, keep learning.
In this episode, we answer: My boss has been trying to transition our team from everybody working all the time, day or night to setting realistic expectations for support and holding us to those. It's hard for me to take her seriously when she answers emails day and night within minutes of their arrival. I'm not talking about just high importance emails, but all emails. It's rare for an email that is sent between 6am and 11pm to fail to get a response from her within an hour. Sometimes, she even responds to emails at 2 or 3 in the morning! I don't feel right not paying attention to my emails when sometimes they're from her, and if it's important enough for her to be online at all hours, shouldn't I be too? What do you think she really wants us to do? And some special treats from us to you: Olive Garden by Shytown Puppy Monkey Baby Don't forget to join us as we read The Phoenix Project by Gene Kim, Kevin Behr, and George Spafford!
Business Book Movement - Notion360. Revisión Online del Libro: The Phoenix Project - Gene Kim, Kevin Behr y George Spafford. Invitado: Esteban Eid. Únete a nuestra comunidad en Discord a través del siguiente enlace: https://bookmovement.co/discord See acast.com/privacy for privacy and opt-out information.
In 2013 the Phoenix Project by Gene Kim, Kevin Bahr and George Spafford sparked the next phase of DevOps transformations. 6 years later Gene Kim (@RealGeneKim) is back with The Unicorn Project, A Novel about Developers, Digital Disruption, and Thriving in the Age of Data.Developer Productivity is a key focus point of the story in the book and is what Gene has learned from different companies in the last years about. Good engineering companies put their best resources in developer productivity as it benefits every developer and allows them to use their best energy to provide business value instead of solving puzzles. Gene lets us in on his day at Etsy as well as the story from Nokia and the reason they moved away from Symbian – both stories that touch on developer productivity!If you want to learn more and read about the Five Ideals then download the excerpts from The Unicorn Project.https://itrevolution.com/the-unicorn-project/https://twitter.com/RealGeneKim
In 2013 the Phoenix Project by Gene Kim, Kevin Bahr and George Spafford sparked the next phase of DevOps transformations. 6 years later Gene Kim (@RealGeneKim) is back with The Unicorn Project, A Novel about Developers, Digital Disruption, and Thriving in the Age of Data.Developer Productivity is a key focus point of the story in the book and is what Gene has learned from different companies in the last years about. Good engineering companies put their best resources in developer productivity as it benefits every developer and allows them to use their best energy to provide business value instead of solving puzzles. Gene lets us in on his day at Etsy as well as the story from Nokia and the reason they moved away from Symbian – both stories that touch on developer productivity!If you want to learn more and read about the Five Ideals then download the excerpts from The Unicorn Project.https://itrevolution.com/the-unicorn-project/https://twitter.com/RealGeneKim
Adrian Moisey, former VP of Engineering at SweepSouth, and now Salesloft engineer, is a huge advocate for attending tech meetups. As one of the organisers of Cape Town’s DevOpsDays, he’s learned that the way a conference is set up affects the value people get out of it. Using his experience organising DevOpsDays conferences, he shares how he thinks about creating 10x value. He talks about speaker-sponsor-attendee value through mingling, putting together a curated line-up of speakers, and leveraging the ‘open spaces’ model to create engaged conversation amongst attendees.Read the blog post here!-----------If you are keen to learn more about DevOps, two books that Adrian recommends are:“The DevOps Handbook: The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations”, by Gene Kim. A book about DevOps (as the title suggests!), but with examples of specific, technical DevOps practices and stories in action.“The Phoenix Project: The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win 5th Anniversary Edition”, by Gene Kim, Kevin Behr, and George Spafford. This is great for people who are in upper management, and who might see what's happening on the ground but aren’t necessarily that involved with the technical side of DevOps.
We're Back! Sorry for the wait. I hope you enjoyed the podcast, feel free to contact me on timicode54@gmail.com if you have any further queries. The Book mentioned is 'The Phoenix Project' a Novel by Gene Kim, George Spafford, and Kevin Behr. Be sure to give it a read. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/delicatedatabase/message
Om Shownotes ser konstiga ut så finns de på webben här också: https://www.enlitenpoddomit.se/e/en-liten-podd-om-it-avsnitt-220 Avsnitt 220 spelades in den 23:e juni och eftersom en normalstor hummer (ca 700gr) är ca 5-7 år handlar dagens avsnitt om: FEEDBACK OCH BACKLOG * Mats har varit på jakt efter hare tillsammans med hunden. David har haft en bra helg. Björn har grillat. Johan har lekt av barnen. * Om man av misstag kör ett katt-filter på en presskonferens så är det JÄTTEMÅNGA som vill titta. (detta är fantakstiskt kul) * Trots kattfilter så var det ändå Simone Gertz som vann internet den här veckan med sin "truckla". En Tesla model 3 som byggs om till en Truck * NewYork har förbjudit "Not-a-flamethrower" * Mer om New yorks. Den här gången om tunnelbanan som tydligen kör OS/2 * Harry Potter: WizardsUnit har fått 400 000 nedladdningar på första dagen MICROSOFT * Microsoft Edge (den som vi ofta kallar för "chredge" eftersom att det är Chromium-Edge) kommer till Windows 7, 8 och 8,1 * Nya Windows Terminal (preview) finns ni i Microsoft store att ladda ned (Windows 10) * Azure Bastion är nu i publik preview * Världens näst bästa program (=Powerpoint) får mer AI!! :) APPLE * Apple kommer nu supportera NFC (i nästa iOS-version) * BONUSLÄNK: när släpptes Iphone 6 * Microsoft To-Do kommer nu till Mac GOOGLE * Google slutar med Tablets * Google funderar på att lösa "messaging", och vill man läsa ännumer så finns det här också * BONUSLÄNK: marknadsfördelning mellan olika Android versioner * Google hade otur när man byggde Google Nest Cam Indoor home security camera (i alla fall de som ansvarade för säkerheten) DIVERSE NYHETER * Samsung säger att man ska viruskolla sin TV * BONUSLÄNK: The Things network SOMARTIPS: * DAVID - prova-på-Prime (because! "Good Omens" (https://www.amazon.com/dp/B07FMHTRFF) - Hängmatta (https://www.hangmattor.se/hangmattor-singel/hangmatta-pernambuco) - Drickakyl (https://www.coolstuff.se/Cool-Well-Kylbrunn) - Chiliprodukter (https://www.bluebox.se/Chili-Klaus-Preseltlada-Chiliprodukter) - Hamburgerpress (https://www.bluebox.se/Hamburgerpress) - Grill (https://greenmountaingrills.com/products/grills/jim-bowie-prime/) * BJÖRN: - storytel - Blinkist - Böcker - Start With Why,Författare: Simon Sinek, Länk: Ljudbok, Fysisk bok - The Phoenix Project, Författare: Gene Kim, Kevin Behr, George Spafford, Länk: Ljudbok, Fysisk bok - Get in the boat: A journey to relevance, Författare: Pat Bodin och Robert Schaffner, Länk: Fysisk bok (bokus), Fysisk eller kindle (Amazon) - Would you do that to your mother?, Författare: Jeanette Bliss, Länk: Ljudbok, Fysisk bok, e-bok - Djävla skitsystem, Bästa stället att hitta den är här: http://javlaskitsystem.se/ - Sources of Power, Författare: Gary A Klein, Länk: Fysisk bok * MATS: - Köp en Kindle - prova-på-Readly - Prova-på-Audible - Extra batteri till mobilen och plattan - lär dig att beställa drinkar utan att skämmas * JOHAN - Daredevil - Lucifer - Every Tool is a hammer - Lär dig något nytt SHUT UP AND TAKE MY MONEY: * David: Samsung Portabel SSD T5 * Mats: En elektrisk tandborste * BONUSLÄNK: Belysning weber orginal handtag gasolgrill * Johan: Oculus Quest * Björn: en färgläggningsbok från filmen Die Hard * BONUSLÄNK: bok: The beautiful poetry of Donald trump EGNA LÄNKAR * En Liten Podd Om IT på webben * En Liten Podd Om IT på Facebook LÄNKAR TILL VART MAN HITTAR PODDEN FÖR ATT LYSSNA: * Apple Podcaster (iTunes) * Overcast * Acast * Spotify * Stitcher LÄNK TILL DISCORD DÄR MAN HITTAR LIVE STREAM + CHATT https://discord.gg/gfKnEGQ (tack för att du har läst hela vägen hit, du får veckans guldstjärna!)
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.
This weeks podcast discusses the challenges we as IT Heroes often face in working with the executive suite. This episode is fast paced, entertaining and full of nerd references. We reference amazing IT Management and culture books such as Making of a Manager by Julie Zhuo, Powerful by Patty McCord, and The Phoenix Project by Gene Kim, George Spafford, and Kevin Behr. Apparently we really like books. Perhaps we should start a tabGeeks Book Club. What do you think?
Roman is disappointed with Dark Mode. Larry talks about the Phoenix Project. ----- The Big Batch / Small Batch diagram by John Cutler: https://twitter.com/johncutlefish/status/1002193108765831168 ----- The Phoenix Project by Kevin Behr, George Spafford, and Gene Kim: https://itrevolution.com/book/the-phoenix-project/ --- Send in a voice message: https://anchor.fm/uxlikeus/message
In this podcast, Maksim, CDO @ City of San Diago, discussed the nuances of running big data for big cities. He shares his perspectives on effectively building a central data office in a complex and extremely collaborative environment like a big city. He shared his thoughts on some ways to effectively prioritize which project to pursue. He shared how leadership and execution could blend to solve civic issues relating to big and small cities. A great practitioner podcast for folks seeking to build a robust data science practice across a large and collaborative ecosystem. Timeline: 0:28 Maksim's journey. 6:45 Maksim's current role. 11:46 Collaboration process in creating a data inventory. 14:52 Working with the bureaucracy. 18:35 Dealing with unforeseen circumstances at work. 20:22 Prioritization at work. 22:58 Qualities of a good data leader. 26:15 Collaboration with other cities. 27:40 Cool data projects in other cities. 30:55 Shortcomings of other city representatives. 36:54 Use cases in AI 39:00 What would Maksim change about himself? 40:50 Future cities and data 43:55 Opportunities for private investors in the public sector. 45:53 Maksim's success mantra. 50:19 Closing remark. Maksim's Book Recommendation: The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim, Kevin Behr, George Spafford amzn.to/2MAu5Xv Podcast Link: https://futureofdata.org/understanding-bigdata-for-bigcities-with-maksim-mrmaksimize-cityofsandiego-futureofdata-podcast/ Maksim's BIO: Maksim Pecherskiy: As the CDO for the City of San Diego, working in the Performance & Analytics Department, Maksim strives to bring the necessary components together to allow the City's residents to benefit from a more efficient, agile government that is as innovative as the community around it. He has been solving complex problems with technology for nearly a decade. He spent 2014 working as a Code For America fellow in Puerto Rico, focusing on economic development. His team delivered a product called PrimerPeso that provides business owners and residents a tool to search, and apply for, government programs for which they may be eligible. Before moving to California, Maksim was a Solutions Architect at Promet Source in Chicago, where he built large web applications and designed complex integrations. He shaped workflow, configuration management, and continuous integration processes while leading and training international development teams. Before his work at Promet, he was a software engineer at AllPlayers, who was instrumental in the design and architecture of its APIs and the development and documentation of supporting client libraries in various languages. Maksim graduated from DePaul University with a bachelor of science degree in information systems and from Linköping University, Sweden, with a bachelor of science degree in international business. He is also certified as a Lean Six Sigma Green Belt. About #Podcast: #FutureOfData podcast is a conversation starter to bring leaders, influencers and lead practitioners to come on show and discuss their journey in creating the data driven future. Wanna Join? If you or any you know wants to join in, Register your interest by mailing us @ info@analyticsweek.com Want to sponsor? Email us @ info@analyticsweek.com Keywords: FutureOfData, DataAnalytics, Leadership, Futurist, Podcast, BigData, Strategy
Overview: Jason Hand and I discuss the importance of moving away from a blame-oriented culture and towards a learning culture. Jason talks about the importance of understanding how cognitive biases influence decision-making and the need to understand this when conducting post mortems. Jason talks about balancing efficiency and thoroughness, and the importance of using blame-free post mortems as a means for learning. While Jason comes from a tech world, this talk has application to a variety of sectors, including high-risk industrial work. Jason Hand’s Biography: DevOps Evangelist at VictorOps, organizer of DevOpsDays - Rockies, author of the books O’Reilly’s “ChatOps: Managing Operations from Group Chat" as well as "ChatOps for Dummies”. Jason is a co-host of “Community Pulse” (a podcast on building community in tech), and organizer of a number of DevOps related events in the Denver/Boulder area. A frequent speaker at DevOps events around the country, Jason enjoys talking to audiences large and small on a variety of technical and non-technical subjects such as Modern Incident Management, Learning From Failure, Cognitive Bias, ChatOps, and building communities. Show Notes: Information Technology is no longer just a cost center and needs to be seen as a way for companies to innovate and become market leaders. Trying to innovate and experiencing failure can be an important way to learn. Post-Mortems are an important tool for learning and organizations should be transparent about learning and sharing that information about safety with others in the industry. Root cause analysis may uncover something that broke, and that can be fixed, but it may result in a lack of innovation in complex systems unless the organization tries to avoid a check the box mentality for a quick-fix and actually learn and improve the system. After negative events occur, when investigators use the word “why” that can sometimes imply “who” and it is important to avoid blame during post-mortem events, yet organizations often seek blame and accountability from a single individual. Accountability means to “give an account of what took place” or describe what too place. Accountability is not the same as responsibility. DevOps works to create high-functioning teams rather than silo’d teams. When silo’ing goes away organizations can become more innovative and other industries may learn a great deal from how DevOps is working to overcome silo’ing and a lack of cooperation towards system goals. Theory of Constraints may be used to help understand system goals and reduce silos in organizations. Sign up for our Newsletter here, or go to: www.v-speedsafety.com/email-subscription Resources: Books: The Phoenix Project by Gene Kim, George Spafford, and Kevin Behr, Thinking Fast and Slow by Daniel Kahneman, Black Box Thinking by Matthew Syed and The Cynefin Mini-Book-Info-Q by Greg Brougham Contact: Web: www.victorops.com www.jasonhand.com www.techbeacon.com Twitter: @jasonhand Keywords: Disruptive leadership podcast, safety podcast, leadership podcast, safety innovation podcast, high-reliability organizations podcast, human performance, human performance podcast, Crew Resource Management, Crew Resource Management Podcast, HRO podcast, DevOps, blame free post-mortems
Gearóid Crowley is a Lead Consultant at Readify. He's from Ireland, based in Sydney these days, and passionate about helping organisation build quality products with the power of automated release management. Today I gave Gearóid a call to talk to him about his first line of code, his many years in the industry and what he enjoys most about working at Readify. In Discussion: - My first Amstrad. 1992. Ireland. - First line of code. - Building a chess game in assembly. - Solving a problem is often about how it's setup. - First job in tech. - How did Readify appear on your radar? - Life and thinking of the team at Readify. - Changing landscape of cloud computing and the resulting rise of Devops, discipline and quality. - Busy Queues. Idle Queues. - Books. The Phoenix Project by Gene Kim, George Spafford, and Kevin Behr. Personal Kanban by Jim Benson. - Xmas cooking kanban board.
Dwayne Melancon, CTO of Tripwire, has an interesting idea: turn your team into gamers, let them build their internal images and support that vision. This isn't the type of thing you'd expect to hear at a security conference. In this short conversation, I talk with Dwayne about how to implement employee game theory within your project team. About Dwayne Melancon I was a contributor to both the Visible Ops Handbook and Visible Ops Security Handbook, working with authors Gene Kim, Kevin Behr, and George Spafford. As part of this effort, I have worked as a researcher with Carnegie Mellon’s SEI, the University of Florida, and the IT Process Institute in their studies and benchmarking of IT best practices. I work with numerous corporations around the world on IT service management improvement and IT security, and have teamed with the Institute of Internal Auditors in its pursuit of Generally Accepted IT Principles. As a frequent, highly-rated speaker at national and regional itSMF, ISACA, ISSA, IIA and other industry events, I present on how to achieve world-class IT results. Using a framework of essential IT controls, I provide operations, security, and audit audiences with prescriptive steps they can take to improve IT change policies, procedures and systems.