Tiny DevOps

Jonathan Hall
  • 0.0 (0)
  • પ્રૌદ્યોગિક વિજ્ઞાન
  • સાપ્તાહિક અપડેટ કરેલ

Solving big problems with small teams

  1. Jonny Williams — What is Delivery Management?

    20/12/2022

    Jonny Williams — What is Delivery Management?

    Jonny Williams works at Red Hat as an agile Delivery Lead, and he joins Tiny DevOps to cut through the confusion surrounding "Delivery Management". In this episode... What is "Delivery Management"?The discipline vs the roleComparisons to Product Management, Agile, Lean, Scrum, ITIL, and ITSMHistory of Delivery ManagementHow does Delivery Management fit into "Agile"?Where is Delivery Management most popular?How can you start benefiting from the Delivery Management discipline in your organization?How to get started as a Delivery ManagerWho should avoid Delivery ManagementGuestJonny Williams, Agile Delivery Lead at Red HatWeb site: https://delivervalue.uk/LinkedIn: https://www.linkedin.com/in/jonny-williams-83433836/ ResourcesBook: Delivery Management: Enabling Teams to Deliver Value Watch this episode on YouTube.

    57 મિ૰
  2. Gorjan Jovanoski — Saving the planet, one server at a time

    06/12/2022

    Gorjan Jovanoski — Saving the planet, one server at a time

    Gorjan Jovanoski is the co-founder of AirCare, the mobile app that helps you know what you breathe. He joins me to tell the story of founding AirCare, and share some of the surprises, good and bad, along the way. In this episode... What is AirCare, and what does it do for you?What is its business model?AirCare's origin storyAirCare's tech stack: Flutter, PHP, MongoDB, DigitalOcianRequest volume and seasonalityHow to aggregate 35,000 data sources in PHPDetecting and responding to a DoS attackThe software development cycle at AirCareObservability at AirCareScaling challenges along the wayNext steps and objectivesGuestGorjan JovanoskiAirCare web site Watch this episode on YouTube.

    56 મિ૰
  3. Oshri Cohen — What kind of CTO do you need?

    22/11/2022

    Oshri Cohen — What kind of CTO do you need?

    Oshri Cohen is a fractional CTO with a diverse background, currently working with four companies. He joins me on the show to cut through some of the confusion surrounding the Chief Technical Officer role. In this episode: The four phases of the CTO roleHow often can the same person satisfy the needs of all four phases? (Spoiler: Very rarely)How often can a founding CTO succeed in all four phases?A good CTO focuses on his or her strengths, and hires out the restWhat lead Oshri to start as a fCTOWhy many, perhaps most, early-stage startups don't need a full-time CTOWhy a development agency is like a mischievous genieWhy developers love working with a fCTOWhat could you do with the 150k you'd save by hiring a fCTO instead of a full-time CTO?Tips for becoming an fCTO yourselfGuestOshri CohenLinkedIn: https://www.linkedin.com/in/oshricohen/Website: oshricohen.me Watch this episode on YouTube.

    58 મિ૰
  4. Paul Cothenet — Observations on observability

    08/11/2022

    Paul Cothenet — Observations on observability

    Paul Cothenet of Patch.io joins me this time to discuss war stories implementing observabillity at two small startups. In this episode…- How to choose an obervabillity tool/platform- Why AWS doesn't provide the best observability platform- Teaching the team to use observability- How to convince stakeholders that observability is valuable- What would you miss the most if your observability platform was no longer available?- The business value of a good observability solution- Making observability metrics easy for management to use- What does it all cost?- Advice for getting started ResourcesRands Leadership Slack: https://randsinrepose.com/welcome-to-rands-leadership-slack/ GuestPaul CothenetTwitter: @paulcothenetCompany, and jobs: patch.io Watch this episode on YouTube.

    49 મિ૰
  5. James McShane — Is Kubernetes right for your small company?

    25/10/2022

    James McShane — Is Kubernetes right for your small company?

    James McShane is the Engineering Director at SuperOrbital and has been working with Kubernetes for about 6 years, in a large number of environments. He joins the show today to help unpack whether Kubernetes is a good choice for your small company. - What is Kubernetes, and what problems does it solve for you?- Choosing Kubernetes means choosing a set of problems.- Which application architectures match well with Kubernetes?- Which problems Kubernetes doesn't solve well for you.- How to handle your application data layer when starting with Kubernetes- Some of the differences between the big three's Kubernetes offerings- Should you hire experienced Kubernetes engineers before adopting Kubernetes?- Why is Kubernetes controversial, and how can a newcomer cut through the hype?- Common newbie mistakes- How does price figure into the decision to choose Kubernetes or not?- How to learn Kubernetes if your employer isn't using it GuestJames McShaneTwitter: @jmcshaneEngineering Director at SuperOrbital.io Watch this episode on YouTube.

    56 મિ૰
  6. Dave Mangot — Should you deploy on Fridays?

    11/10/2022

    Dave Mangot — Should you deploy on Fridays?

    Dave Mangot is a speaker, author, teacher, and Silicon Valley veteran.  His focus is helping private equity portofolio companies use their technology organization to maximize growth, and he joins me today to discuss the contentious topic of Friday deployments and why you definitely should do them and why you definitely should not do them.  Confused? In this episode Mores are not moratoriumsShaming is inappropriate, on both sides of the issueEvery outage is unexpected, nobody knows what might go wrongFriday deployment should be an informed choiceWhy small batch deployments are importantDeploying features vs other changesYou should be able to deploy at any time, but separate that from choosing to deploy at any timeWhy more QA can be worse than less QAIf deployment hurts, or causes fear, do it moreResponding to failures when they do occurBuilding an accurate mental model of your systemResourcesArticle: Deploy on Fridays, or Don'tBook: Continuous Delivery by Jez Humble and Dave FarleyTalk: How Complex Systems Fail by Richard Cook (Velocity 2012)Book: Project to Product by Mik KerstenBook: Out of the Crisis by W. Edwards Deming GuestDave MangotWeb site: https://www.mangoteque.com/LinkedIn: mangotTwitter: @davemangot Watch this episode on YouTube.

    52 મિ૰
  7. Tod Hansmann — Observability as an engineering enabler

    27/09/2022

    Tod Hansmann — Observability as an engineering enabler

    Problem solver Tod Hansmann of Catalyst joins me to discuss "observability": What it is, why it means different things to different people, and how to get started if it's new for you. In this episode: What is observability (o11y)?What can observability do for you?What metrics should you track?How does observability relate to logging, alerting, monitoring, and other practices?Who should be responsbile for obervability?How heavily should upper management be involved?How does observability relate to culture?CI/CD as a prerequisite for observabilityWhy metrics are better than logsSurprising metrics that can be importantThe relationship between monitoring and automated testingGood observability as an enabler for canary deployments, test in production, and other practicesHow to define service level objectivesHow do you define "uptime"How to address corner casesWhy being on call is desireableGuestTod HansmannTwitter: @todpunkLinkedIn: Tod HansmannCatalyst ResourcesBook: Site Reliability Engineering Watch this episode on YouTube.

    45 મિ૰
  8. Jason Adam — A conversation about trunk-based development

    13/09/2022

    Jason Adam — A conversation about trunk-based development

    Jason Adam is a software with a non-traditional background in biology, business development, and data analytics. Now he's active as a developer, and on the lookout for proven practices he can introduce to his team. On this episode we talk about Trunk-Based Development, and the related topics of continuous integration and deployment, infrastruture as code, and much more. In this episode How Trunk-based development differs from GitFlow and other branching strategiesTwo flavors of trunk-based developmentHow Trunk-based development fits into the larger picture of continuous integration and continuous deliveryTechniques for working in smaller batchesHow test-driven development enhances trunk-based developmentUsing feature flags for smaller batchesHow to keep pull requests smallCherry-picking small changes out of a larger pull requestHow Infrastructure-as-Code works with CI and CD Resources Book: Continuous Delivery by Jez Humble and Dave FarleyBook: Domain-Driven Design by Eric EvansBook: Working Effectively with Legacy Code by Michael FeathersBook: Clean Architecture by Robert Martin GuestJason AdamWeb site & newsletter: functionalbits.io Have a topic to discuss on the show? Let me know!Want a private consultation? Borrow my brain. Watch this episode on YouTube.

    45 મિ૰
તમામ જુઓ (52)

ટ્રેલર

વિષે

Solving big problems with small teams

માહિતી

  • નિર્માતા
    Jonathan Hall
  • વર્ષ સક્રિય
    2021 - 2022
  • ઍપિસોડ
    52
  • રેટિંગ
    સાફસૂથરું
  • કૉપિરાઇટ
    © 2022 Jonathan Hall
  • શોની વેબસાઇટ
    Tiny DevOps