Tom Segura jokes about supermodels in his Netflix special, "Sledgehammer".
Player FM - Internet Radio Done Right
Checked 1d ago
اضافه شده در three سال پیش
محتوای ارائه شده توسط Serverless Craic from the Serverless Edge. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Serverless Craic from the Serverless Edge یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Player FM - برنامه پادکست
با برنامه Player FM !
با برنامه Player FM !
))
Daily Deals
Serverless Craic Ep46 Resilience Hub
Manage episode 378899691 series 3304957
محتوای ارائه شده توسط Serverless Craic from the Serverless Edge. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Serverless Craic from the Serverless Edge یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
How important is Resilience Hub, Chaos Testing and Well-Architected?
We attended the AWS Resilience Day at the Titanic Hotel. We were sitting in the same room where the ill-fated Titanic was designed and drawn! We discuss what we learned. Including the tools and strategies that help software engineers build resilience that were not available for the Titanic engineers. And we talk about the fact that it isn't just one thing that leads to disaster for ships or workloads.
Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube
67 قسمت
اشتراک گذاریManage episode 378899691 series 3304957
محتوای ارائه شده توسط Serverless Craic from the Serverless Edge. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Serverless Craic from the Serverless Edge یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
How important is Resilience Hub, Chaos Testing and Well-Architected?
We attended the AWS Resilience Day at the Titanic Hotel. We were sitting in the same room where the ill-fated Titanic was designed and drawn! We discuss what we learned. Including the tools and strategies that help software engineers build resilience that were not available for the Titanic engineers. And we talk about the fact that it isn't just one thing that leads to disaster for ships or workloads.
Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube
67 قسمت
همه قسمت ها
×
Send us a text Mapping Your Org Capability | Chapter 11 Breakdown of The Value Flywheel Effect In this episode, Dave Anderson, Mark McCann, and Michael O’Reilly dive into Chapter 11 of The Value Flywheel Effect — "Map Your Organisational Capability". We unpack how to use mapping techniques, such as Wardley Mapping, to assess and visualise your organisation’s capabilities across areas like security, cloud-native development, and emerging tech like GenAI. The discussion covers: 🔹 Why individual expertise ≠ organisational capability 🔹 Mapping techniques using industry standards and evolutionary stages 🔹 How to use mapping for strategic clarity and identifying capability gaps 🔹 Lessons from applying security and cloud-native capability maps in real organisations 🔹 Using mapping as a lightweight but powerful tool for technology leadership and investment planning This episode is full of practical insights for tech leaders seeking clarity, situational awareness, and better strategic decisions. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text 🎙️ Serverless Craic: Exploring Socio-Technical Systems for Change Welcome back to Serverless Craic! In this episode, the team dives into Chapter 10: Challenge – A Socio-Technical System for Change from the book, The Value Flywheel Effect. This thought-provoking conversation unpacks how organisations can effectively bridge the gap between people and technology to foster meaningful, sustainable change. 🔍 Topics Covered: What makes socio-technical change so difficult The importance of flow, team design, and time to value Lessons from Team Topologies and Drive by Daniel Pink Frameworks like Cynefin and Wardley Mapping Democratising AI and enabling change through feedback loops Why architecture alone won't save you 🤔 Whether you're a tech leader, architect, or engineer, this episode offers valuable insights on how to navigate complexity, decentralise expertise, and embed purpose and autonomy at every level of your organisation. 📚 Referenced: Team Topologies Drive by Daniel Pink: Cynefin Framework (Dave Snowden) Wardley Mapping Fred Emery’s Design Principles Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text 🎙️ Environment for Success & Psychological Safety Welcome back to another episode of Serverless Craic! After a short hiatus (thanks, ServerlessDays Belfast!), Dave Anderson and Mark McCann return to dive deep into one of the most critical – and timely – topics in modern software delivery: creating the right Environment for Success. In this episode, we unpack Chapter 9 from The Value Flywheel Effect and explore the fundamentals that enable high-performing teams, including: 🔹 Psychological safety and why it’s the foundation of great engineering cultures 🔹 The danger of hero anti-patterns and the myth of the “rock star” developer 🔹 Challenging assumptions safely – using artefacts, not egos 🔹 Simon Wardley’s doctrine and Dr. Ron Westrum’s organisational culture model 🔹 How aligned autonomy and clarity of purpose help teams focus on what matters 🔹 Why generative, learning organisations adapt best to AI-driven change Whether you’re a tech leader, architect, or engineer, this conversation is a masterclass in building sustainable, modern digital organisations. 🧭 Referenced resources: The Value Flywheel Effect by us! The Fearless Organisation by Amy Edmondson Accelerate by Nicole Forsgren Simon Wardley’s Doctrine Dr. Ron Westrum’s organisational models Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text In this episode of Serverless Craic, Map the Market and A Cloud Guru Case Study, we dive into Chapters 7 and 8 of the book The Value Flywheel Effect. The discussion focuses on "Mapping the Market" and a fascinating case study on clarity of purpose, featuring the story of A Cloud Guru. Discover how mapping the value chain helps companies identify their place in the market, understand competitors, and predict strategic moves. Learn about the transformative impact of a laser-focused North Star and how serverless-first approaches powered scalability and success. The episode includes insightful anecdotes, practical mapping techniques, and lessons from real-world examples like Tesla and A Cloud Guru. 🎯 Key Topics Covered: - Mapping the market and competition. - Understanding and leveraging the value chain. - Insights from A Cloud Guru’s journey to a $2 billion acquisition. - Practical tips for mapping your strategy effectively. 💬 Join the conversation! Share your thoughts and subscribe for more discussions on engineering, strategy, and innovation. Thanks for tuning in, and see you in the next episode, where we’ll explore "Challenging the Environment" in the Value Flywheel framework! 🚀 Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text Welcome to the latest episode of Serverless Craic! 🎙️ Today, we're diving back into our series on The Value Flywheel Effect, focusing on Chapter 6: "Obsess Over Time to Value." Join us as we explore the significance of delivering value quickly and efficiently in tech organisations. We discuss the concept of "Time to Value" over "Time to Market," reflecting on how innovation labs and agile structures can help companies pivot, react, and respond to both threats and opportunities. In this episode, we touch on key topics like: - The importance of creating a feedback loop to see real user value - The challenges of organisational inertia and how it can inhibit innovation - Real-life examples of experimentation and pivoting, including building "trap doors" to validate product assumptions - The role of situational awareness in overcoming barriers to change We also delve into how high-performing teams can increase an organisation’s "rate of turn," making it more adaptable in a rapidly evolving market. Whether you're dealing with big projects or experimenting with new technologies, empowering teams to focus on value, rather than just speed, can transform your business outcomes. If you enjoyed this discussion, don’t forget to subscribe, like, and share. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text This episode centres on Chapter Five of the book "The Value Flywheel Effect," focusing on the North Star framework. We explain how this framework helps teams align their work with a clear, meaningful metric (North Star) and its related leading and lagging metrics. North Star Framework Overview We explain the North Star framework, emphasising its use in helping teams coalesce behind a mission or purpose with a visual, collaborative tool. And the importance of leading metrics and lagging metrics, explaining how the North Star framework helps teams reverse engineer leading metrics from lagging ones. Application of North Star Framework We look at the usefulness of the North Star framework at both the small startup level and the enterprise level, where it helps link lead measures back to overall business impact. The North Star framework is powerful for team and individual morale by making work meaningful and aligning it with organisational objectives. We reference Dan Pink's "mastery, autonomy, sense of purpose" to emphasise the importance of knowing what you are doing and why. The North Star framework is complementary to mapping for strategy, helping to narrow down on value and focus conversations. Challenges and Benefits of North Star Framework It is valuable to ask teams about their metrics and how their work influences them, leading to valuable conversations about measurement and alignment. We look at the importance of measurement, referencing Grace Hopper's quote about the power of accurate measurement. Having data and clear alignment to organisational strategy helps teams advocate for change more effectively. The North Star framework can sometimes reveal that teams are not aligned or that the overall strategy is flawed, likening it to the emperor's new clothes. Connecting North Star to Business Value A structured North Star often reveals disconnects in the work being done and its impact on business value, serving as a corrective measure. We compare the North Star framework to impact mapping, both helping to create a compelling narrative and understand the story of what the team is working on. It is challenging to craft the North Star for behind-the-scenes teams, but the framework helps align value delivery with business goals. We discuss Amazon's working backwards process and its similarities with the North Star framework, emphasising the importance of understanding the customer's need and working backwards from there. Critical Thinking and Leadership These frameworks are enablers of critical thinking, challenging teams and organizations to question their assumptions and goals. North Star metrics and key input metrics make it easier to write a compelling press release that aligns with the company's strategy. Clarity of purpose is the foundation of everything, requiring leadership and courage to implement. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text In this insightful discussion, we explore mapping techniques from Chapter 3 of our book The Value Flywheel Effect and their applications in organisations. Key topics include: Anatomy of a Worldly Map: Breaking down the components of a map, including visible, aware, and invisible items in the value chain. Mapping Teams and Tech Stacks: How mapping helps in identifying team roles and modernising technology stacks. Starting with Maps and Collaboration: Tips for overcoming the blank canvas fear and leveraging tools like GitHub's "Awesome Worldly Maps" and VS Code extensions for map annotations. Open Space Collaboration: The value of engaging everyone in discussions and validating inputs. Mapping the Stack, Organisation, and Market: Using mapping for situational awareness, aligning teams with core domains, and understanding market dynamics to respond effectively to opportunities and threats. This conversation provides practical insights into using mapping for better organizational awareness and strategic decision-making. - Learn more about The ServerlessEdge - see link below - Explore GitHub's Awesome Worldly Maps for useful mapping tools. Don't miss this deep dive into mapping strategies to enhance your organisation’s situational awareness and tech evolution! Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text Wardley mapping is a strategic tool to visualise the evolution of products or services. The two axes of a Wardley Map are visibility and evolutionary stage. Products and technologies evolve through four stages: Genesis, Custom build, Product or rental, and Commodity or utility. Understanding context and phase of adoption is crucial in the business world, especially with AI and LLMs. Identifying and moving commodities versus custom-built solutions is important, and optimizing organizational structure for autonomy involves concepts like movement, time planning, and sub-maps. We explain the anatomy of a Wardley map, starting with the anchor (customer) and emphasising the importance of understanding the map's axis and how space and position have meaning. Evolution of technology from Genesis to Commodity, with stages of Custom Build and Product. Product evolution from Genesis to Custom, Commodity, and ubiquity, tailored to specific contexts. We explain the evolution of products through usage and competition and product evolution is context-dependent. Leveraging AI and LLMs in business contexts. We highlight the varying perceptions of LLM and Gen AI across different contexts and note that DBT is marketed as a product or consumer depending on the context. We discuss the importance of understanding user needs and dependencies in designing a successful product. Mapping components to move from custom-built to commodity products. We look at the importance of mapping components to move a business forward and identify inertia as a challenge in moving components, and discuss ways to overcome it. The conversation highlights the importance of leveraging commodities and building a database in 2024. We discuss the evolution of AI, from its early stages to its current utility, and the importance of having the right team types, including explorers, settlers, and time planners. We emphasise the need for all three team types, as each one plays a crucial role in the AI development process, and spikes in team performance can be identified and addressed accordingly. Mapping for autonomous organisations, including optimisation, movement, and sub-maps. We look at the importance of optimising for movement in engineering teams, with different strategies for 'pioneers', 'settlers', and 'villagers'. And the need for organisation-wide alignment and the use of mixed methods within Wardley Mapping, with a focus on stacking boxes when necessary. We look at the importance of mapping in software development, highlighting different types of maps and their uses. And we provide tips for creating effective maps, including using sub-maps for detailed areas and avoiding too many components on the map. Wardley Mapping Resources: Ben Mosior and https://learnwardleymapping.com/ Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text We discuss facilitating effective collaborative mapping workshops and creating Wardley maps for strategic planning in businesses. We look at the importance of creating a safe environment, effective facilitation techniques, and involving all stakeholders in the mapping process. We also highlight the benefits of embracing diversity and respecting different opinions. And we share various approaches to creating and utilising Wardley maps, including Miro and Lucid, and learning more about the technique through Ben Mosior LearnWardleyMapping.com resources. Wardley Mapping techniques and anti-patterns. Dave Anderson and Mark McCann discussed anti-patterns in Wardley mapping, including "gaming the system" (Dave Anderson). The speakers shared their experiences and insights on how to avoid common mistakes in Wardley Mapping (Dave Anderson, Michael O'Reilly). Collaboration is key in mapping exercises, as it helps to identify blind spots and improve the overall quality of the map. It's important to strike a balance between mapping by yourself and collaborating with others to ensure a richer feedback loop and improved map quality. Michael O'Reilly suggests mapping a subject matter to identify blind spots and derive questions to ask (0:05:10) Dave Anderson advises against re-creating architecture diagrams and instead focuses on higher-level abstraction (0:06:27) Software development, components, and abstraction. Dave Anderson and Mark McCann discuss the challenges of defining and understanding components in software development. Experience and wisdom are key to summarising complex conversations and determining the appropriate level of abstraction for components. Dave Anderson and Michael O'Reilly discuss the importance of context in understanding a Wardley map, with examples from their own experiences. They emphasize the need to introduce new people to a shared conversation gradually, rather than expecting them to pick it up quickly. Facilitating workshops, mapping, and collaboration. Michael O'Reilly and Dave Anderson discuss the importance of mapping in strategy development, highlighting its ability to shake out key elements and dependencies. Mark McCann emphasises the value of psychological safety in a top-down environment, where managers must create a safe space for team members to share their thoughts and ideas. Dave Anderson and Mark McCann emphasise the importance of creating a safe environment where participants feel comfortable sharing their opinions and asking questions. Facilitators should be open and non-forced in their approach, allowing participants to take the lead and challenge each other's perspectives. Using Wardley mapping to understand user needs and dependencies. Dave Anderson and Mark McCann discuss the importance of identifying the user and their needs in the mapping process. They use specific examples and exercises to help the group understand and clarify their thinking. Dave Anderson and Mark McCann discuss the importance of collaboration in product development, using sticky notes and online tools like Miro and Lucid to facilitate brainstorming sessions. They emphasise the need to keep the collaboration process simple and focused, with clear goals and a structured approach to e Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text Dave, Michael, and Mark discussed the application of Wardley Mapping in understanding movement and making strategic decisions. They share their experiences with the method, emphasising its ability to visualise and track changes in tech stacks and capabilities. They also discussed the importance of context, user needs, and facilitating meaningful conversations through mapping. Additionally, they highlighted the benefits of mapping for challenging each other's thinking and fostering creative dialogue. Later, they discussed the importance of understanding user needs during agile transformations, including the value of having a shared representation of collective experiences and strategies for removing barriers to change in an organization. Outline Using Wardley mapping to improve understanding of complex systems and software development. Dave Anderson and Mark McCann discuss the history of Wardley mapping, including when they first learned about it and how it has evolved over time. The hosts emphasise the importance of mapping movement and tracking progress in the context of technology and capability, citing examples from their own experiences. Mark McCann: Focusing on user needs in Agile transformations helped teams understand why they were delivering code. Michael O'Reilly: Participating in mapping sessions helped him understand technical nuances and communicate with non-technical stakeholders. Mark McCann: Identified value chain visibility as key to success Dave Anderson: Custom skill sets and implementations were hindering progress Challenging inertia points in team decision-making. Dave Anderson and Mark McCann discussed the importance of mapping out problems and inviting team members to contribute their perspectives. The team used a structured approach to thinking deeply about problems and coming up with solutions, which helped to challenge assumptions and identify areas for improvement. Identifying and addressing inertia points is crucial for strategic maneuvering. Leadership principles, including courage, collaboration, empathy, and narrative. Dave Anderson and Michael O'Reilly discussed the importance of courage and collaboration in tackling complex problems. They emphasised the need for shared understanding and mapping with other teams to make better decisions. The importance of context in mapping: Understanding the user's needs and perspective is crucial for effective mapping. Empathy and narrative: Mapping can facilitate empathy and storytelling, but it's important to show the map to the right audience. Principles of Wardley mapping for strategic planning. Michael O'Reilly and Mark McCann discuss the importance of simplifying complex systems through Wardley mapping, focusing on the principles of abstraction and dialogue. Dave Anderson emphasises the importance of not overcomplicating the model, and using it as a facilitation for meaningful conversations. Dave Anderson and Michael O'Reilly discuss the importance of mapping in facilitating creative conversations. They outline the eight principles of Wardley mapping and its benefits in understanding a company's value chain. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text The Value Flywheel Effect is a pattern seen in organisations where business strategy and technology strategy align, leading to more sales and growth. The hosts discuss the concept of the value flywheel effect, its origins, and how it applies to creating software for customers. Dave Anderson and Mark McCann discuss the four phases of the value flywheel process, with three principles for each phase, aimed at building momentum and sustainability in organizations and teams. Clarity of purpose is the first principle, visualised as a data-informed Northstar, helping teams understand their core user needs and improve situational awareness. Software development principles, including focus, clarity, and understanding the market. Michael O'Reilly and Dave Anderson discuss the importance of aligning individual and team goals with the overall organisational Northstar. They emphasise the need for a clear problem statement and direction to focus attention and achieve success. Michael O'Reilly and Dave Anderson discuss the importance of focusing on time to value in product discovery, rather than just time to market. They emphasise the need to map the market and clarify the business's purpose, rather than just focusing on individual silos or software pieces. Dave Anderson looks at the importance of understanding a company's strategy and market position, even for software engineering teams. Mark McCann suggests that junior engineers can gain valuable insights by analysing a company's website, LinkedIn, job postings, and press releases to understand their competitors and industry landscape. Engineering team structure, process, and enablement. Michael O'Reilly: Embrace diverse teams for success, learn from failures. Mark McCann: Socio-technical systems crucial for successful teams. Michael O'Reilly and Dave Anderson discuss the importance of enabling and empowering engineers in High Performance Engineering, including creating a generative environment and mapping the organisation for enablement. Mark McCann adds that removing friction points and impediments is crucial, including developer enablement, handoffs, and carving off certain things to encourage smaller approaches. Prioritising tech stack, offloading non-differentiating tasks, and mapping solutions to customer needs. Focus on delivering value, not just building code. Dave Anderson emphasises the importance of prioritizing tech stack and deciding what to move to the right, while Michael O'Reilly and Mark McCann discuss the benefits of mapping out the tech stack and identifying key differentiators for the business. Modernising software development and delivery using AWS Well-Architected Framework. Dave Anderson looks at the importance of preventing problems before they occur in software development. Mark McCann highlights the need to understand the ecosystem and constraints when implementing continuous delivery. Mark McCann: Celebrate successes in fraud prevention, reward employees for going above and beyond. Dave Anderson: Keep a low carbon footprint, measure efficiency and sustainability in cloud workloads. Mark McCann and Dave Anderson discuss the importance of well-architected frameworks for cloud migration and sustainability. They highlight the 12 p Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text We discuss why we wrote 'The Value Flywheel Effect,' emphasising our desire to give back to the community and help others who have contributed to their success. We share our experiences and insights on navigating the cloud transformation journey, highlighting the importance of luck, collaboration, and upskilling in overcoming challenges. We also discuss modernising engineering practices, prioritising meaningful outcomes, and providing insights on change leadership and decision-making techniques. Modernising software development and delivery in the cloud. Michael O'Reilly and Dave Anderson share their experiences working together in the cloud industry, mentioning luck and serendipity as key factors in their success. They emphasise the importance of being high up the value chain and delivering meaningful outcomes, even in the face of economic ups and downs. Michael O'Reilly and Dave Anderson discuss the shift towards modernisation in engineering, with a focus on agility and speed. They emphasise the importance of thinking differently and acting collectively to drive change in the industry. Modernising software development and embracing new technologies. Organisations must adapt to changing industry expectations and evolving technologies to remain competitive. Dave Anderson and Mark McCann discuss their book on modern software development, with Dave crediting Mark for encouraging them to write it. Mark McCann recounts how they met and shared ideas before writing the book, with Dave describing it as a "big confidence boost." Modernisation strategies for technology and business. Dave Anderson and Michael O'Reilly praise Simon Wardley's mapping technique and strategic thinking, citing his ability to make complex decisions and decompose things down. Simon Wardley's 2015/2016 talk on serverless computing is highlighted as a standout moment, with Dave Anderson calling it "super important" and Michael O'Reilly praising his ability to entertain and carry a message. Dave Anderson and Mark McCann discuss modernisation in organisations, emphasising the importance of leadership and decision-making. They suggest a framework for driving modernisation, including techniques like event storming and Northstars. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text AWS Serverless Developer Advocate Team news is breaking. We discuss this and the importance of community events and fostering a culture of curiosity and collaboration in the tech industry. We emphasise the value of attending events like ServerlessDays Belfast and looking outside one's own silo to drive enterprise transformation. We also discuss the significance of developer advocacy in promoting AWS adoption and we look at the challenges of quantifying the impact of advocacy work and the importance of learning about new technologies and driving change within companies. Outline Serverless development and engineering history in Belfast. ServerlessDays Belfast provided a great opportunity for attendees to engage in meaningful conversations with both beginner and seasoned experts in the field. Serverless technology and its impact on software development. We emphasise the importance of applying new ideas and learning from others in the tech industry. Jeremy Daly's keynote at the event inspires attendees with his innovative approach to serverless computing at AMP. We praise the AWS Developer Relations team for their helpfulness and unbiased opinions. The team has been a valuable resource for learning and validation, with their content and opinions shaping the field. Leveraging serverless technology and its benefits in modernisation and migration efforts. We credit the DAs with breathing life into the serverless movement and discuss how serverless technology can help modernize enterprises by leveraging existing work and tailoring it to specific contexts. Developer advocacy and its impact on the tech industry. We highlight the valuable insights and expertise of various serverless experts, including Julian Wood, Eric Johnson, David Boyne, Marcia Villalba, and Chris Munns. We recommend reading the ServerlessLand site as a go-to resource for understanding serverless technology and strategies. We discuss the impact of their developer advocacy work on AWS, highlighting the need for continued investment in Dev Rel. We emphasise the difficulty in measuring the impact of their work but noted anecdotal evidence of significant change driven by their efforts. Modern cloud solutions and their evolution. We discuss the evolution of developer advocacy at AWS, highlighting the importance of feedback loops and professionalism. And emphasise the value of connecting customers with the product team to address feature requests and shape product direction. We discuss the evolution of cloud services, including the term "next gen" and the importance of situational awareness. And reflect on their favorite team and thank engineers for their work, encouraging listeners to follow TheServerlessEdge.com website and channels. Serverless Craic from The Serverless Edge: https://theserverlessedge.com/ ServerlessDays Belfast: https://serverlessdaysbelfast.com/ AWS Serverless DA Team: https://serverlessland.com/ Check out our book The Value Flywheel Effect: https://theserverlessedge.com/the-value-flywheel-effect/ Follow us on X @ServerlessEdge: https://twitter.com/ServerlessEdge Follow us on LinkedIn - The ServerlessEdge: https://www.linkedin.com/company/71264379/ Subscribe to our Podcast: https://open.spotify.c Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text We use the Cynefin Framework in our cloud modernisation work. Dave Snowden created the Cynefin framework. Cynefin, pronounced "ku-nev-in," is a Welsh word that translates as "place" or "habitat." However, it can also be used to describe the elements of our situation and personal history that influence our thoughts and decisions in ways we don't understand. It's a sense making framework. As architects, we find that the Cynefin framework is a good thinking model. In the Cynefin framework there are four domains and a fifth disorder domain. The first four domains are: 1. Clear, when something is well understood, 2. Complicated, it's understood by few, 3. Complex, where there are a lot of unknowns. 4. Chaos, when you don't know what's happening. The 5th domain in the middle is called Confused. If you understand which domain you're in, you can assess where you're at, and if you're not aware of where you are, you're just confused. When you deal with situations and teams, it's sometimes easy to see the problem or situation. It falls under one of the domains and there are a bunch of practices to apply. When something's well understood and clear, the practices are different than for something that's complex. There are different ways for you to handle situations. And if you're a manager, there are different ways to manage. A chaotic project needs different practices to a project that you know well and when know what to do. We explain each of the domains and we apply them to Software Development. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text ServerlessDays Belfast 2024. ServerlessDays Belfast is back at Titanic Hotel Belfast on Thursday 23rd May 2024 Our theme is 'Building Beyond Boundaries: ServerlessDays Belfast celebrates the spirit of Innovation'. Find out why you should come to the birthplace of Titanic and what you can expect from this year's ServerlessDays Belfast. From the 100-year-old Drawing Offices at Titanic Hotel Belfast, we will celebrate how the Serverless Mindset enables engineers and organisations to break barriers and build like never before. We ask our speakers to speak of the courage, ambition and resiliency needed to build big. We will showcase international and local speakers, attracting interest across Europe and the US. Most importantly, we want to inspire Engineers in Ireland, the UK and the local tech community. Serverless has transcended technology and is now a synonym for Digital Transformation. Engineers working for large and small organisations need a dedicated space to hear and share innovation stories, with Serverless First as the enabler. Senior executives sense that Serverless is at the intersection of technology and business. Everyone needs a network to access the playbook for the Modern Cloud. Everyone is welcome, especially: Engineers who are curious by nature are excited to explore new technologies and ways of working. Leaders seeking the latest solutions and innovations, including product managers, programme directors, and CTOs. This event is a dedicated space for you to network, share, learn and become inspired about Serverless and Modern Cloud. We look forward to seeing you there! What’s on offer Food and Beverages ServerlessDays Speaker Agenda: Listen to renowned experts on Serverless Network with fellow attendees ServerlessDays Belfast 2024 Call for Papers We’re looking for speakers who can share their stories about how serverless technology has helped them achieve amazing things. The theme for this year’s event is “Building Beyond Boundaries”. We want to celebrate the spirit of Innovation and share stories of real change. Tell us about something incredible that happened, how you felt and how the tech helped out. If you’re interested in speaking, submit your talk by March 31st! We will cover travel and accommodation expenses for speakers living outside commuting distance. Take advantage of this opportunity to share your knowledge and experience with the serverless community on the island of Ireland. Learn more and submit your talk on Sessionize . serverlessdaysbelfast.com/ twitter.com/BFSServerless linkedin.com/company/serverlessdays-belfast Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
S
Serverless Craic from The Serverless Edge
Send us a text The Software Development Lifecycle - how does it apply to modern cloud? We are kicking off this episode with the term modern SDLC. The software development lifecycle (SDLC) is changing. When you get into this new way of working, you start differently. It's no longer a straight waterfall/ABCD, or starting with an established system like SCRUM and iterating. So how do you get into a fast flow state? We have discovered a lot of things over the past couple of years. In this episode, we talk you through the phases of the modern software development lifecycle. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text We talk about what we would like to see announced at this years AWS re:Invent 2023 looking at Observability, Generative AI, PartyRock, Developer Experience to name a few. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text Team Engineering with SCORP - there are practices we do like SCORP, which is our agile way of doing well-architected in every sprint with teams. Our practices are connected to engineering excellence, looking at what you're doing and constantly improving. And HP (high performing engineering), as a way of capturing key metrics to define good engineering or architecture, and then talk about it as a team. Even though the practices are out there, it's really just a mindset. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
S
Serverless Craic from The Serverless Edge
Send us a text There were a few stories in the news about working remotely from another country. We talk about the pros and cons of working remotely versus returning to work. We work remotely and are globally distributed, but we've worked for many years in the office to, so we have experience of both to make a fair analysis. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text Developer Productivity and discussions on developers and productivity have never gone away. You heard people talking about this in the 80s and the idea of paying developers by lines of code. And it was even rubbished in the 80s as a foolish thing to do. There's a famous story about developers removing bad code from the code base and having negative numbers by the end of the week and then asking if they have to pay the company back money. It's never been a good idea. It strikes me as strange that in 2023, we are having the same discussion. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text How important is Resilience Hub, Chaos Testing and Well-Architected? We attended the AWS Resilience Day at the Titanic Hotel. We were sitting in the same room where the ill-fated Titanic was designed and drawn! We discuss what we learned. Including the tools and strategies that help software engineers build resilience that were not available for the Titanic engineers. And we talk about the fact that it isn't just one thing that leads to disaster for ships or workloads. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
S
Serverless Craic from The Serverless Edge
Send us a text Bringing mapping to your org. We are doing a wee series on Wardley Mapping, with some practical items. The last two episodes were: 'Wardley Mapping 101' and 'Can Wardley Maps Predict the Future?'. So I thought it would be good to answer a common question: 'That's a cool technique, but how would I do that in my work?'. If you follow Simon Wardley, on Twitter, and you've started experimenting with Wardley Mapping, we tell you how you to bring Wardley Mapping to your place of work. We talk about using the Northstar exercise to facilitate mapping. And about finding like-minded people to sit and practice with. There is a way of talking about mapping. You're better to start with the outcomes. And then see if people are interested to get back into the map, as a way of sensemaking complicated areas. It's great to make sense of something and share that thinking with peers. And once you get into that language, you open up a common way of thinking and the idea of evolution to access things you want to talk about it. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
S
Serverless Craic from The Serverless Edge
Send us a text Can Wardley Maps predict the future, is our topic this week. In our last episode, we talked about Wardley Mapping. We did a 101 last time, explaining the basics. One of the things that we say is that Wardley Mapping is a superpower that helps you predict the future. What do we mean by that? It's like a fortune teller. But it doesn't tell you when exactly something's going to happen. It's the state of mind that it puts you in. We run through a couple of examples, to demonstrate how we've done it in the past. Conversational Programming Generative AI Well-Architected Serverless CDK (Cloud Development Kit) If you have good situational awareness, you can wait until the appropriate time. You don't have to go off and waste energy, cycles and money trying custom build something. Wait three months and you'll get what you're trying to achieve. When you map this stuff out, you can start to think about how your sensing engine can get intel on whether these things are going to happen or not. There are lots of different ways you can do that. Like following Twitter feeds and looking at blogs. And looking at who they're hiring and following the industry experts. They're points of information that can help you see how things will evolve. To predict the way things are going to go. There are multiple levels of maturity in your map and how you think it's going move and where the evolution is going to happen. Wardley Mapping can be used to predict the future but it's not going to give you an exact date. What it can do is give you an example of this is what it will look like if it happens. So you prepare yourself for when it does. And then when the press release comes out, you're like, boom, we're ready. We saw that coming. So it's the no 'surprise approach' to building situational awareness. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text Wardley Mapping is a core part of our book: 'The Value Flywheel Effect'. And it's a topic that people always ask about it. It's a difficult thing to learn. We've spent many years thinking about it, stumbling around, and then practicing. So we figured we would do a quick series on Wardley Mapping. We have spent almost 10 years mapping, give or take. For me, it has been an absolute game-changer. One thing that's come along recently is the Wardley Mapping canvas by Ben Mosior @hiredthought . It's a nice canvas with six steps on how to map. Before I started using the canvas, I used to find that maps could get big and go off in 60 different directions. Purpose and scope are the first two steps. And then the third one is users . The fourth one is user needs. And then the fifth step is the value chain . It can be difficult to keep things abstract. And not go too deep. But it is good to be as abstract and high-level as possible, even just to start to get something down. Once you have the value chain of the user, a need, and a couple of dependencies, that's when you then bring it across to the map. And I would usually put them in the middle of the map. Drop them all into Product, to get you started. So you've got them all in a vertical line on your map and canvas. You start moving different components from left to right. And you might work out that one of the dependencies is Commodity or Custom. And you can see how that interaction goes. That's when you start to add in dependencies because you've got more room in the map. This is where the conversation really starts to kick into gear. And this is where people start to challenge each other's context and think about where that component belongs or what's missing from the map. So it makes for a very collaborative exercise. If you are planning a mapping session, you need to be a good facilitator. If a participant feels something is in the wrong place. Don't say no, you're wrong. It's in the right place. You want the individual to explain why they think so. If it is something that's blatantly just them for raising the challenge. The last thing you want is an unsafe environment where nobody wants to speak. It doesn't need to be too fancy. You might map for an hour. And if you're facilitating, five or 10 minutes off the hour, you take a couple of notes, If someone says we should move that component from x to y that's an observation, You're not committing to do it but just taking a few observations. Always just keep it simple. So here are a couple of really good links. We talked about Ben Mosier @hiredthought . He's got a brilliant site called LearnWardleyMapping.com . Ben created the Wardley Mapping Canvas, which is on Creative Commons Open Source. Simon's also got a couple of links. There's a site on GitHub called Awesome Wardley Maps. It is by John Grant on List.WardleyMaps.com . Simon's original book is on medium.com/wardleymaps . Simon's content is great but deep. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text ServerlessDays Belfast was on the 28th of February. It's a volunteer, community, and not-for-profit event. We had a bunch of sponsors: AWS, Bazaarvoice, EverQuote, G-P, Instil and LibertyIT. Our organizers are me, Gillian Armstrong, Garth Gilmour, Peter Farrell, Julie Sherlock, and Treasa Anderson. We had 12 speakers, and over 260 attendees from over 40 companies. But most excitingly we had it at the Game of Thrones Studios Tour. The theme was 'The Reality and Fantasy of Serverless, Building Serverless Teams and Making it Real'. Phil Le-Brun, who is the Director of the Enterprise Strategy Team for AWS launched the event. And give us a perspective of what he sees when he is speaking to the leaders of the industry. IT Revolution was very generous to sponsor and provide 250 of 'The Value Flyweel Effect' books. Julian Wood gave the Keynote. Even though he works for AWS as a Serverless Developer Advocate, he gave his opinion on where he sees the industry. I thought that paired really nicely with Mattie Wilson from Instil. He gave a brilliant talk on an engineering team going through the journey from a cloud application to a serverless application. Sheen Brisals from The LEGO Group, as ever, gave an absolutely brilliant talk about Lego's journey. Going Serverless to EDA and the team topologies of an event-driven organisation. Sheen is an absolute master. Jonah Andersson did a talk on the .NET stack. And Conall Bennett and Roger Moore did a talk on CME Group's move to a Google tech stack. Craig McCarter talked about large-scale serverless. And I took comfort from hearing about a team that's doing something financially significant at a massive scale. And they're pushing those limits. I really enjoyed the talk by Anna Carlin and Emma Patton from Aflac Northern Ireland. They called their talk: 'A rookie journey of discovery and learning'. So they came in as grads and basically built a serverless system. And Chintan Parmar's Dunelm story was really interesting about Dunelm's e-commerce site because it's quite an unknown story. Most people had no idea that they had a whole big serverless ecommerce site. Ben Ellerby from Aleios closed out with his Serverless Staircase Framework. I've been a fan of Ben's for many years. He's an AWS Hero. He's brilliant and very experienced. And he's worked on a lot of serverless projects. That is what his company does. So he's got lots of war stories from doing this with real customers. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text We've been talking about AWS re:Invent over the last few episodes. But one thing that we haven't talked about is Serverless Espresso. Serverless Espresso is a pop up coffee shop that allows you to order coffee from your phone. In the Expo Hall at the AWS Summit, they have a Barista setup. And you walk up to a QR code with a screen in the background. So you scan the QR code and enter in your email address. And up pops a menu. If you select an americano, espresso or other type of coffee, it kicks off an event driven flow. It uses an event driven service under the hood and pops up in the screen as a number. And then the Barista takes the number makes your coffee and gives it to you. But what's happening in the background is a whole load of orchestration and choreography run events. And as they've been using it as a way to explain serverless event driven architecture. Event driven architecture can be hard for people to conceptually wrap their heads around. So making it real through ordering coffee. And showing how to tie a coffee process and an event driven coffee ordering system makes it real. It stitches together a lot of stuff that we've been advocating for, in a way that makes sense. By using AWS Step Functions, EventBridge, Lambda, API Gateway, S3, DynamoDB and Cognito. There are two myths in this space that AWS are trying to dispel. We first started talking about event driven architecture 13 years ago. We had the idea of doing something but back then it was really difficult, because we didn't have a lot of support. So we had hard problems to solve technically, because the foundations weren't there. That is the first myth of being a hard thing to do. The second myth is that people think of serverless as just writing code and functions. It's actually more like an event driven architecture. It's events firing off activity and not a call stack. So it's a lot easier to build full event of architecture than it would have been years ago. The technical challenge is not as bad as you think it is. What I like about Serverless Espresso is the simple interactions. You order, it goes to the barista who makes the coffee, and he gives it back to you. There's one interaction. Normally when ordering a coffee, you talk to a waiter, the waiter talks to the barista, and the barista talks to someone about milk etc. There can be six or seven people in that flow. It causes confusion. In a company, if a business process is owned by six or seven teams, even across two or three departments, it gets messy. If a single team builds for the customer directly and there's no one else, it's usually pretty clean. Serverless Espresso Lab is good, because the opinions are out there and you add on your bit, which is your business process flow. It goes back to our book The Value Flywheel Effect. And the first phase of the value flywheel which is clarity of purpose. Who is the customer and what is the business flow that we're trying to build? And let's have a good debate on how we are going to do that. When you get to the technical side, that opinion is already there. And you can focus on getting the orchestration correct. Because you know that a lot of that underlying stuff is pretty much solved apart from making it behave. Look at the Serverless Espresso Lab on Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text AWS, What's New? We are post AWS re:Invent. To sum up, it was about the next generation of cloud focused on delivering value quickly by removing barriers to business adoption and enablement. On Day 1 SiliconAngle published an article called " AWS chief Adam Selipsky hints at the next-gen cloud ". He looks at classic cloud versus next-gen cloud. Classic cloud is infrastructure as a service and the platform of the cloud. And next-gen is looking at ISVs and true cloud. It's about using the cloud to power you business journey. Which is exactly what we talk about in The Value Flywheel Effect ! AWS are market leading for low level cloud primitives. If you want compute, get it from AWS. It has been this way for the last 15 years. But next generation cloud is about business capability. When you do Wardley mapping correctly, cloud primitives are pushed to the right to become commodities. You then look for the business capability you need. That's exactly what the value flywheel effect is. AWS are consolidating core primitives and opening up the solution space to help customers do interesting things with them. There has been a lot of criticism of AWS in previous years with regards to their developer experience. Code catalyst is a big move from AWS to try to make that more seamless. It stitches together a number of things that have evolved over the last while. It's an accelerator for teams coming on to the cloud or into serverless. And it is frictionless developer experience. In our book, it's the next best action phase of the value flywheel. Well architected featured heavily at AWS re:Invent. AWS are continuing to develop well architected and build it into things. Security also featured with verified permissions. It's out in pilot at the moment but it has potential to make a big impact on managing fine grained permissions and doing identity authorization properly, especially if you have a custom app. Most companies of a certain scale have their own custom built version of this. But you need to acknowledge that you are ahead of the curve. And have the courage to delete your custom built solution. There's a bunch of step function stuff out. I particularly like SnapStart which gives you the ability to drop large java applications into lambda. And performance time is through the roof. You can draw up an average Spring Boot application into lambda and you will get similar performance but it's way cheaper to run. It's addressing the myths around cold starts and using lambda for high performance workloads. It's also interesting from the perspective of having large framework oriented services and leveraging those for femoral compute. At AWS re:Invent, the message I was hearing loud and clear is that enterprises and large companies have moved to the Cloud but need help doing the next piece. They need help creating their value flywheel. They've done the move and now need to go to the next stage of modernization or next-gen. So that is good news for our book 'the Value Flywheel Effect'. There's definitely a lot of demand for more advice and guidance. The ecosystem has never been better for applying the value fly Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
Send us a text AWS reInvent announcements In this episode we are talking about what we would like to see at AWS re:Invent. What would you like to see? Serverless Services An increase to the enhancement and evolution of service development capabilities and the ecosystem in general. So more serverless services coming online for items that aren't serverless and iterating to be more serverless. There's a bunch of things that people are almost afraid of like observability, deployment patterns and some of the frameworks. API Gateways In service development, Private API gateways are interesting, but they could be more developer friendly, in terms of setting up, naming and managing. We are seeing more enhancements around eventing capability like SNS filtering, SQS and X ray. These are things that make the serverless experience more rich and all encompassing. Developer Enablement You need to think about developer enablement and time to value. Can you get a developer up and running with a productive IDE in the cloud? And can they start delivering value rapidly? We're seeing steps around Cloud IDE starting to emerge. I want to see what AWS does around their Cloud9 offering. Well Architected Over the last year, we've seen good announcements on well architected capabilities, systems and services. I want to see a continued evolution of that. And more well architected thinking and characteristics baked into everything. All the way from developer advocates to patterns and code samples. Some of the basic primitives are moving up a level to something more like a pattern. It's about fast feedback and dare I say the value flywheel. Can the pipeline's tell us how well architected the chains that we made are. And can our IDE tell us how well architected we are? Stitching that together in a compelling way with fast feedback for the developers would raise the bar on what developers deliver into production. That's effectively platform heuristics. I remember back in the IBM mainframe days, it was a mature platform. And you knew it so well, that they started to bake in heuristics. When you start to analyse your code there would be a heuristics to say this might be wrong. Here's what you need to do to fix it. We're starting to see some of these elements emerge already with Security Hub, Reliability Hub and Fault Injection Simulator. It's about stitching those together like factory mode for workloads in your accounts. Tell me we're not well architected, and tell me how to fix it. Sustainability More fine grained analysis of carbon scores would be useful when teams are designing and building their workloads. And getting faster feedback on a particular service and how much it is going to cost you in carbon. What's the wacky stuff you would like to see? I'd love to see work on APA management and API gateways . Factory mode for your accounts. How well architected are you would be really good. Instead of us having to do the reviews and do it manually. The gateways are due an uplift or enhancement. What about documentation ? And how you consume information about services. We are seeing an explosion of services on the console. Is there going to be a cut down console just for Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
S
Serverless Craic from The Serverless Edge
Send us a text It began with the forging of the Great Maps and Simon Wardley We've been talking this week about Wardley mapping. Where did you first hear about Wardley Mapping? I first heard Simon Wardley talking at cloud conferences about early cloud. I remember an open source conference and a 20 minute video. When he presented it came across as common sense. Like, why would you do anything else? The bigger question is why were we looking for this type of stuff? Or why did it resonate with us? I think we were at a certain point in our careers. We had been engineers for a while. And we thought there's got to be a bigger picture here that we're not quite grasping. Simon Wardley started writing his book in 2016. I went to Lean Agile Scotland in October 2016. And he did the talk in person. I had seen his talk a couple of times, but it didn't really click until I sat and watched it in real life. Remember, there was a time when we said we need to stop using PowerPoint! We need to get people into rooms to have conversations and working sessions. I refined and improved my ability to do Wardley Maps through teaching. There were people who hadn't experienced mapping. There's another important step. You move from doing it yourself to doing it in a group environment. When you are looking at a map you are figuring it out. When you do it in a group environment, the group will ask about this and that. And that's when it really starts to click. For me, the two big things are: 1. Start with a customer need. I remember a team were stuck for six months because they didn't know who the customer was. 2. The four phases of evolution or access (Genesis, Custom Built, Product, Commodity). Get your head around that concept. One of the other pitfalls we fell into was mapping too much detail. We went too low level. And then someone came along and zoomed us out, by saying 'you don't need those five components. Here's just one!'. Another important lesson is that senior people just want to hear what you are going to do. They don't want to know how you figured it out. If they say why are you doing that? You can go through the map in your head and say that you've thought about it. If you say this is what we are going to do and here's the outcome, you don't need to show them all your work. When we started mapping there wasn't much about apart from the odd presentation. Now there's lots of material out there. The community is growing. You can google and look up YouTube. And there's online conferences as well like Map Camp. For resources look at Simon Wardley on Twitter @swardley and his pinned tweet. Simon has a book: ' Wardley mapping '. He is on Medium at ' wardleymaps '. There's a whole bunch of stuff including free articles. They're fairly meaty but they're good. John Grant keeps a list of maps on GitHub, which is list.wardleymaps.com . Ben from @hiredthought is also at learnwardleymapping.com . And of course, our book, ' Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
S
Serverless Craic from The Serverless Edge
Send us a text What is Engineering Excellence? Few companies say they don't want good engineering. But they don't define what good looks like. And secondly,engineers are expected to write lots of code. For me, engineering excellence is not writing loads of code. It's about getting into code reliability, feedback loops and how well engineering is functioning. And how your team is performing and meeting bigger goals. I love to say 'slow is smooth and smooth is fast'. So how do we set ourselves up for that? At the beginning, I like to go slowly to look at our process. To define engineering excellence, we use Dan Pink's motivation factors of autonomy, mastery, and purpose. We translate those motivation factors to technical excellence, autonomy, and customer focus. Well architected is better defined than engineering excellence. But I find that a lot of people haven't heard the term well architected and they think you've just made it up! If you want to move fast, you've got to be empowered and know what good architecture looks like. When you have guidance or patterns that are implemented in a well architected fashion, that sets you up for rapid delivery, moving with speed, and in an engineering excellence way. It's fast flow aimed to facilitate you moving fast, getting things out quicker and being more competitive. Teams are rapidly delivering product value multiple times a day. And they have a trail of evidence that they're going the right way because of these practices. They have dashboards, logs, alarms, alerts and the run books and the playbooks. And the key business indicators (KPIs) at their fingertips. So any stakeholder can challenge them on what they are doing, how they are operating or what they are deploying. If you arrive in an area that isn't well architected, you've got to spend three months trying to understand what went on before or trying to understand the decision making. Or you've got 12 months of technical debt that should have been taken on board before you moved there. That very difficult from a personal perspective. There's a whole bunch of advantages. One is a problem prevention culture. But I don't think it exists in a lot of organisations. It hasn't really cut through. They're still on the feature, factory, server mindset. Deliver, deliver deliver. Feature, feature feature. And then they have a tipping point where everything grinds to a halt for months or maybe years. And it may never recover. But if you have a continuous improvement mindset and you are investing in fraud prevention, well architected, engineering excellence and continuous learning. And you are enabling and applying this to your teams, you get ahead of problems before they become problems. From a problem prevention perspective, do you want to spend all your time babysitting a non well architected workload and dealing with all of that? You want your teams moving, adding value and moving on to the next thing. That's not possible if your build lacks quality, is always down or if you're having to constantly upgrade. With well architected and engineering excellence, we can build things that run and increase in value. And there's less work over the long term, while your teams move on to what the business needs. I don't think a lot of orgs think in th Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on X @ServerlessEdge Follow us on LinkedIn Subscribe on YouTube…
به Player FM خوش آمدید!
Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.
Daily Deals
Player FM - برنامه پادکست
با برنامه Player FM !
با برنامه Player FM !
))
