Podcasts about jessica how

  • 15PODCASTS
  • 20EPISODES
  • 37mAVG DURATION
  • 1MONTHLY NEW EPISODE
  • Apr 4, 2025LATEST

POPULARITY

20172018201920202021202220232024


Best podcasts about jessica how

Latest podcast episodes about jessica how

Fit Female Project
Client Q&A 4th April - Targeting your belly, fasted workouts, carb loading, under active thyroid and more

Fit Female Project

Play Episode Listen Later Apr 4, 2025 29:31


Want to apply to be coached by us? Follow us on Instagram nor @fitfemaleproject or head to the website www.fitfemaleproject.com Questions in order: Client Questions - **Sophie** – How can I focus on belly fat after having two kids and a C-section? - **Emily** – Does it matter when I eat breakfast after the gym? - **Francesca** – Should I eat before an early morning workout? If so, what should I eat? - **Michelle** – Is it okay to work out fasted, or should I have a snack to avoid high cortisol? - **Jessica** – How can I balance half marathon training with strength workouts without overtraining? - **Vicki** – How many ab workouts should I do per week? - **Bailey** – What are some simple ways to increase protein intake on busy days? - **Emily** – Could my underactive thyroid be affecting my weight loss, and what foods should I eat or avoid? - **Anna** – How do I do a barbell shoulder press without hitting my chin or pulling my head back? - **Sam** – What alternative handle can I use for cable exercises if the rope attachment isn't available? - **Eadaoin** – What's the correct knee angle and form for the leg press? - **Gemma** – Do I have to do cardio? I love strength training and don't want to risk anything in my first trimester. - **Niamh** – I'm on a mini cut, but my protein intake is higher than usual. Is that okay? - **Amy** – How can I handle sugar cravings? Also, is it normal to wake up thirsty at night? - **Emma** – Can you help me with carb loading? What should I eat and how many carbs do I need? - **Aisling** – I took a break from weighing myself. Should I start tracking my weight again? - **Jess** – What time will the London meet & greet be? - **Ann-Marie** – Should I focus on getting deeper in my squats before adding more weight?

The Patrick Madrid Show
The Patrick Madrid Show: March 27, 2025 - Hour 2

The Patrick Madrid Show

Play Episode Listen Later Mar 27, 2025 48:48


Patrick discusses the following during Hour 2: Elias - How effective are prayers from people of different faiths? Francisco - Is it true that you don't need to be Catholic to go to heaven? AND I was told we are all Saints. Is that true? Jessica - How do you honor the commandment of honoring your parents when they tell you to do something that is against the Catholic Faith? E-Frank - How do you know if a priest is doing something against Cannon Law? AND how can you stop him? Janice - Yesterday, I went to mass and the priest was visibly sick so I decided to not receive communion. Is that a sin? Emmy - Regarding Following Jesus: God has been working in my heart. I left the Church half a year ago because of hypocrisy and scrupulosity. I think I was maybe wrong to leave.

The Candace Cameron Bure Podcast
Priscilla Shirer - Surrender Everything You Are

The Candace Cameron Bure Podcast

Play Episode Listen Later Nov 26, 2024 37:06


In Episode 5 of Moving Beyond Belief, Candace and Priscilla discuss identity - being dead to sin, alive to God, and they answer a listener question from from Jessica: “How do you tell your child they are doing something wrong without constantly criticizing them? I grew up with critical parents and was scared of doing things wrong and now am a perfectionist and neat freak. I want to guide my nephew and niece on how to be orderly, neat and polite but don't want to come across as critical or criticizing them all the time.” LINKS: https://nutrafol.com/ - Promo code CANDACE Get ten dollars off your first month's subscription and free shipping when you go to Nutrafol.com and enter the promo code CANDACE https://worldhelp.net/gift/candace-cameron/?utm_m=WHWEB-CCB https://www.lifeway.com/en/product-family/storyteller-bible-study Learn more about your ad choices. Visit megaphone.fm/adchoices

The Injured Athletes Club
96 | Carrie Answers Your Questions: Re-Finding Your Edge

The Injured Athletes Club

Play Episode Listen Later May 4, 2023 12:26


“I'd love to know how you ever get comfortable with pushing the limits, or pushing hard again, without being so scared of re-injury. I often feel that in my speed workouts, I'm holding back, afraid to see how hard I can push, because I'm scared, but I also don't want to let that fear hinder my athletic development! How to strike a healthy balance of ‘fear' I suppose or learning to listen to your body.” —Jessica   “How do I trust my body again, and how do I untangle what is purely mental (fear!) and what is physical (still rebuilding muscle)? How do I separate what I'm afraid to do from what's actually unsafe to do?” —Stevie   This week, co-host and mental skills coach Carrie Jackson answers two questions from listeners Jessica and Stevie, who are both working to regain their footing as they emerge from recovery.   In her response, Carrie explains why the brain works so hard to protect us after an injury, raising all these fears of getting hurt all over again. And, she shares genius tips for learning to trust your body all over again, including the 1% rule.   Listen to the show for more—and to submit a question for a future episode, email us a note or a voice memo to hello@injuredathletesclub.com.    Resources/links: Athlete affirmations from The Injured Athletes Club   Thank you so much to our sponsors for season 6:  Fluid Running, which has revolutionized fitness by bringing running to the deep water IceeNOW.com, which provides innovative injury prevention and recovery solutions for athletes ADAM Rehabilitation, creators of the ADAM Brace System, the most stable exercise system built to save the health of your shoulders Learn more and access exclusive discount codes for their products at buymeacoffee.com/rebound or by joining The Injured Athletes Club Facebook group.   To access more resources for injured athletes: Buy Rebound: Train Your Mind to Bounce Back Stronger from Sports Injuries —now available as an audiobook! Join The Injured Athletes Club mailing list, for news and updates Join The Injured Athletes Club Facebook group, for support and camaraderie Like The Injured Athletes Club Podcast Facebook page, for the latest episodes Email us at hello@injuredathletesclub.com with questions, guest suggestions, or other feedback   DISCLAIMER: This content is for educational & informational use only and & does not constitute medical advice. Do not disregard, avoid or delay obtaining medical or health related advice from your health-care professional because of something you may have heard in an episode of this podcast. You should not rely on this information as a substitute for professional medical advice, diagnosis or treatment. Please consult with a qualified medical professional for proper evaluation & treatment. Guests who speak on this podcast express their own opinions, experiences, and conclusions, and The Injured Athletes Club podcast hosts nor any company providing financial support endorses or opposes any particular treatment option discussed in the episodes of this podcast and are not responsible for any actions or inactions of listeners based on the information presented. The use of any information provided is solely at your own risk.

sports injuries jessica how injured athletes club
The Patrick Madrid Show
The Patrick Madrid Show: March 21, 2023 - Hour 3

The Patrick Madrid Show

Play Episode Listen Later Mar 21, 2023 49:09


Patrick answers listener questions about cellphones in the confessional, is fornication a mortal sin, what does it mean to “offer it up,” can Guardian Angels read our minds, and are the Harry Potter books okay for kids to read Charlene - A priest said that he was hearing a confession and even though the cellphone was on mute it still picked up the confession of a felon and the police arrest him afterwards. Jessica - How can I encourage my sister to come back to confession? Is fornication a mortal sin? Casey - If the Son has no beginning or end, then why did God say 'today I have begotten you' in the bible? What does it mean to “Offer it up?” Janine - What is the word of faith movement and prosperity gospel? Jennifer - Is the book called “The Great Controversy” good for me to read? Patrick says no and explains why. Rosalia - Can Guardian Angels read our minds when we pray? Burt - If two people who are not married in the church have relations outside of their marriage would that be fornication or adultery? Lisa - Are people who don't know God going to be judged harshly? Irene – Are the Harry Potter books bad for small children?

The Undomestic Mom Podcast
091 |Meaningful Mom Chat with Jessica Smith: Thriving In Millennial Motherhood

The Undomestic Mom Podcast

Play Episode Listen Later Oct 18, 2022 47:40


In my first ever "Meaningful Mom Chat," I have the pleasure of chatting with Jessica Smith from the Fit Life with Jessica Podcast. It's no secret that motherhood is one of the most rewarding yet challenging jobs a woman can have. In my newest series, Jessica Smith shared her insights on inner healing, combatting mom guilt, and how to little moments to yourself can restore you in motherhood. This is a candid conversation between moms that you won't want to miss! Jessica Smith is an accountability coach who helps you NOT break promises to yourself.  She will push you when you need to be pushed and be there to listen when you need a friend.  Tough love mixed with compassion and motivation.  She loves taco night and would never expect you to skip the chips and salsa:) Her logical and realistic approach to helping women who want to work on their health goals is not just some fad diet.  Jessica and I connected on Instagram in April 2021 when I wanted some help staying accountable for my health goals. Jessica helped me fall back in love with riding my bike and having fun with daily movement. In today's episode, I'm asking Jessica my top 5 burning questions for all moms. We have a really meaningful conversation that touches on inner healing, mom friends, being proud of yourself in motherhood, carving out time for yourself, asking for what you need, and getting the support you need when times are tough.  We discuss the struggles with feeding our kids dinner, how the little moments impact our kids and how therapy can be the turning point on your road to happiness.  Going through tough times when you have little kids, and a mountain of responsibilities that don't stop can be extremely tough. Jessica and I get honest and vulnerable about how we both struggle to ask for help or support, and Jessica shares how she likes to receive support from friends that's meaningful and comforting. She gives some real-life anecdotes on how to get through the tough times and come out of the other side stronger. If you're a mom looking for uplifting and authentic conversation, this episode is for you! I hope you enjoy it as much as I did. So, pour yourself a cup of coffee or tea, put your feet up and let's chat about how to have the happiest life possible. You are not alone in this journey called motherhood. We hope you enjoy this episode! Connect with Jessica How to Meal Plan Like a Boss Workshop Instagram Podcast FREE 5-Day Healthy Meal Plan  

Get Sh!t Done
#53 How to Build Your Founder Brand (Jessica Zweig, Founder of SimplyBe) (2019)

Get Sh!t Done

Play Episode Listen Later Jun 7, 2022 33:38


We're taking it back to one of our FAVE episodes on how to build your founder brand with Queen, Jessica Zweig. She is a MASTER at personal branding and will walk you through how to build your founder brand to grow your company. Here's what you're going to learn from Jessica: -How to avoid “faux authenticity” -How to identify your content buckets -Tactics for how you can build out your personal brand Join the tribe: https://www.shegetsshitdone.com/join

The Mental Health and Wealth Show
Recovering from Burnout and Starting a New Life: An Interview with Jessica from The Fioneers

The Mental Health and Wealth Show

Play Episode Listen Later Jun 3, 2022 55:24


In today's episode, I chat with Jessica from The Fioneers, an award-winning blog that focuses on building financial freedom and designing a life you truly love. Jessica is a full-time human being and a part-time writer and lifestyle design coach. We talk about how she recovered from burnout and how she had a transformative time with her relationship with money. Learn how she manages her mental health today and uses money to design a new life. "You deserve to actually feel better." - Jessica "You don't need to stay in the difficult place that you're in just because others might have it worse. We all deserve to thrive and a rising tide lifts all the boats." - Jessica What You Will Learn From This Episode Experiencing burnout from work and the steps that you can take to get sick leave, get paid, and deal with your mental health How dialectical behavioral therapy helps Jessica How self-care by subtraction, burnout recovery activities, and self-discovery work Getting back up again and starting entrepreneurship that supplements her mental health Ways to build financial freedom now to help you enjoy life and improve mental health before reaching FI (what is coast FI) What Jessica is doing now to help with her money and mental health Tips if you're at a crisis point with your work and mental health About Jessica: Jessica is a full-time human being and a part-time writer and lifestyle design coach. She is a co-founder of the blog, The Fioneers, a globally recognized and award-winning resource focused on building financial freedom and designing a life you truly love. In her free time, you can find her spending time outdoors with her husband and dog, road tripping in her camper van, and playing complex board games. Resources: Paying Off Debt, Reaching FI, and Dealing with Online Hate: An Interview with Jillian Johnsrud Burnout Recovery: 6 Strategies I Found Super Helpful by Jessica You are Not Your Job: How to Reclaim your Identity by Jessica How to Set Boundaries at Work by Jessica Connect with Jessica thefioneers.com Instagram Twitter Connect with Melanie mentalhealthandwealth.com melanielockert.com Instagram Support the podcast through Ko-Fi Buy Melanie's book “Dear Debt” Contact: mentalhealthandwealthshow@gmail.com   Want more content and support? Sign up for the Mental Hump Newsletter and get our free Mental Health and Money inventory worksheet. You can sign up at MentalHealthandWealth.com. Also, we host a Mental Health and Wealth Hangout every other Thursday over Zoom at 5 pm PT to chat about all things money and mental health. Join here! Follow us on Apple Podcast or Libsyn! Love the podcast? Leave a review on iTunes!

The Propcast
How Are Building Management Platforms Changing The Way We Live? With Jessica Beck & Marcela Sapone

The Propcast

Play Episode Listen Later May 25, 2022 41:42


Summary: Louisa is joined by Jessica Beck, Co-Founder and COO of Alfred and Marcela Sapone, CEO and Co-Founder of Alfred for the 5th episode of season 9. During this episode, they discuss how building management platforms are changing the way we live. Taking a deeper dive into how Alfred came about and in which city it all began, they also touch on what the product is, what trends they are seeing, and why Alfred acquired a property management company. They wrap up this riveting chat by talking about their journey as female founders and what is next for Alfred. The value bomb from this episode is, “Once you build an asset, you need someone to manage that asset.” Resources: LMRE Global Recruitment and Search Consultancy LMRE YouTube Interviews Companies Mentioned: The Peloton Brookfield Properties Hines Related  RXR  Jamestown Greystar  Shout Outs:   John Fagan, Co-founder & CEO at doorkee   Key Insights From This Episode:  The people who were able to make it all work had one thing in common: they got really comfortable with asking for help as well as comfortable with the idea of a team backing them up. - Marcela  ​Once you build an asset, you need someone to manage that asset. - Marcela   Real estate has been very resistant towards tech enablement. - Marcela My advice to founders would be; it does take time but if you build a relationship and you go building by building, one building to ten buildings, you not only build a great relationship, but you actually get to build a great product and you get to learn and work with your customers to bring something to market. - Jessica We learned that in this space, there's so much fragmentation; there's fragmentation on the technology side, on the services side and on the operator side. - Jessica About Our Guests: Jessica Beck, Co-Founder and COO at Alfred  Jessica Beck is the Co-Founder and Chief Operating Officer of Alfred. Beck leads Alfred's day-to-day operations and under her direction, Alfred has grown to be a leader in hospitality, successfully rolling out a national resident experience and building management platform with hundreds of thousands of units managed.  In an effort to expand Alfred's footprint, Beck has negotiated and developed partnerships with some of the country's largest real estate developers, expanding Alfred to 44 major cities across the country.  Along with Alfred's Co-Founder, Marcela Sapone, Beck supports founders who want to live more consciously through WHITESPACE Ventures, a seed investment firm focused on design-led tech for better business.  From SXSW to the Sante Fe Institute's Annual Business Network & Board of Trustees Symposium, Jess speaks regularly on entrepreneurship and building scalable solutions in the sharing economy. Beck holds an MBA from Harvard Business School and a BA in economics from Williams College, where she was captain of the women's rugby team and graduated cum laude. Marcela Sapone, Co-Founder and CEO of Alfred  Marcela Sapone is the CEO and Co-Founder of Alfred. Sapone launched Alfred with a mission to make help a universal utility in every home. Since 2014, under Sapone's leadership, Alfred has expanded to serve more than 135,000 residents in 44 cities across the United States and Canada, and has been named as Fast Company's Top 50 Most Innovative Companies in 2018, 2019, and 2020.  As one of the first leaders in the sharing economy to advocate for fair compensation of service workers, Sapone adopted the company-wide policy of hiring all Alfred staff as W2 employees. Sapone has worked with the U.S. Department of Labor and the White House under the administration of President Barack Obama, as well as The Brookings Institute and The Aspen Institute's Economic Opportunities and Financial Security Program, to advance these efforts of economic security for the future of employment. Along with Alfred's Co-Founder, Jess Beck, Sapone supports founders who want to live more consciously through WHITESPACE Ventures, a seed investment firm focused on design-led tech for better business.  Named one of Goldman Sachs's “most intriguing entrepreneurs,” Sapone writes and speaks frequently on principled leadership, human-centered technology, and her commitment to being a steward of good jobs and meaningful change. Her writing has appeared in Forbes, Quartz, and Recode, among other highly reputable publications. She has been included in Fast Company's Most Creative People list, featured as the face of Consumer Tech in Forbes 30 Under 30, and was also a winner of Connect Media's Women in Real Estate Award in 2021. Sapone serves on the Norwalk Zoning Commission, where she supports initiatives and creates opportunities for urban development and growth. Sapone earned her BA from Boston University and holds an MBA with distinction from Harvard Business School.  Alfred  Operating at the intersection of real estate and technology, Alfred is the leading resident experience building management platform that is changing the way we live. Founded in 2014 by Marcela Sapone and Jessica Beck, Alfred's mission is clear: to create an industry shift in real estate, transforming renters into residents and apartment properties into neighbourhoods. Named by Fast Company as one of the Top 50 Most Innovative Companies in the World, Alfred has been recognized as a leader in the on-demand and in-home economy, investing in the local ecosystems and neighbourhood businesses that give meaning to our communities. Alfred to date operates in over 135,000 residential units in 44 markets across the U.S. and Canada through strategic partnerships with international real-estate operators, such as Brookfield, Hines, Related, RXR, Greystar and Jamestown. To learn more, visit www.helloalfred.com. About Our Host Louisa Dickins Louisa is the co-founder of LMRE, which has rapidly become the market leading global PropTech recruitment platform and search consultancy with operations across North America, United Kingdom, Europe and Asia-Pacific. To promote the industry she is so passionate about, Louisa set up the Global podcast ‘The Propcast' where she hosts and invites guests from the built environment space to join her in conversation about innovation. About LMRE LMRE is globally recognised for leading the way in Real Estate Tech & Innovation talent management. From the outset our vision was to become a global provider of the very best strategic talent to the most innovative organisations in PropTech, ConTech, Smart Buildings, ESG, Sustainability and Strategic Consulting. At LMRE we are fully committed at all times to exceed the expectations of our candidates and clients by providing the very best advice and by unlocking exclusive opportunities across our global network in the UK, Europe, North America and Asia-Pacific. Timestamps: [02:10] Marcela: How did Alfred come about and how did you meet?  I went to Harvard Business School and ended up sitting next to Jessica, we were both working 90-100 hour weeks.  Our objective, both as individuals and personally, was to figure out if it would be possible to start our own adventure, build our own business and to find a co-founder.  Our question was, “How can we enable women to stay in the workforce longer?”  Our solution was, “Could we create a business that would put groceries in your fridge, dry-cleaning your closet, packages on your counter and have everything you ever needed at the tap of the button. And could that be included in our rent?”  [05:40] Jessica: In which city did this all begin?  We were one of the few consumer companies that originated in Boston as we were still students.  We opened our next market in New York. We have scaled to Canada and now we are in 52 cities.  [07:25] Marcela: Can you tell us more about the product?  We focus on the largest category and asset class in the world, which is housing and we are making it digital.  We take technology and we take a resident first, very consumer perspective and we are disrupting the way that traditional property management happens in multifamily and single family build-to-rent communities. At your fingertips is an application that allows you to buy services, to pay your rent, to book amenities, to book the Peloton, to book the workspace, to complain about something going wrong in your apartment and to request your packages to be delivered to your front door. [10:05] Jessica: How did you go about bringing on your first massive client? Our approach in working with the industry and gaining our first customers was really one of partnering. Our first big customer was Related Rentals.  My advice to founders would be; it does take time but if you build a relationship and you go building by building one building to ten buildings, you not only build a great relationship, but you actually get to build a great product and you get to learn and work with your customers to bring something to market. We always took a partnership oriented, consultative approach.  [12:05] Marcela: What are the major trends you have seen between Boston or New York in terms of what a resident is looking for. In Boston and New York, one of our biggest categories in the service marketplace in terms of time-saving service, was dry cleaning. But in San Francisco, you have absolutely no dry cleaning, and in Texas pet care was our largest category. In the last three to five years while we've been building the business, there's been a tremendous amount of change in the industry. [15:10] Jessica: What was the reasoning behind acquiring a property management company?  One of the things that we learned along the journey is if you really want to change how people live and you want to do it past the front door of their home, you need to be much more connected than you would guess. We realised in order to really deliver the product, we had to become much more integrated into building operations to create an end to end user experience and to deliver on top of that platform, you need to have a consolidation. We learned that in this space, there's so much fragmentation.  [21:15] Jessica: How long on average does a resident stay in an apartment? The average in the US, for annual churn in a property is about 45 - 50% a year and as a consumer business that means there is a lot of opportunity. What we've found is when you put a community in a building and residents start to participate and their lifestyle starts to get automated they end up staying longer.  In properties where we've been operating for some time, we've increased the  renewal rates for our partners by 5-10%.  [24:25] Marcela: Any advice you can give to other female founders? We try to ignore the fact that we're female founders, we would never do female only panels or raise and go out and say, “Female led companies raising X amount.” Focus on the business and the fundamentals of the business.  Have an extreme level of patience and a level of acceptance. Jessica: Being a founder is hard so find a good support system.  [27:55] Marcela/Jessica: How do you support your growing team as well as retain employees?  All of us on the planet are at a point where we're taking a big step back to evaluate our choices. There's been a reshuffling of where people are putting their energy and the careers they want to be in. One thing that is extremely clear is that connecting back to your mission and having an incredibly clear set of values as well as being as radically transparent.  Being empathetic and personal with each member of your team and understanding their goals.  [31:40] Marcela: What is next for Alfred?  Slowly and steadily continually leading the category forward to become the leading brand in residential real estate as well as work with our stakeholders to move the industry forward.  Continuing to add value to all of our customers [34:15] The ‘LMRE' part, Louisa asks the guests to talk about;  L – Touch on the main lessons you have learnt throughout your career. Marcela: First things first and one line to do lists.  Jessica:  When you're a founder, you're kind of the captain of a ship and you see calm seas and stormy seas but you are always in both.  M - Please give a mention to anyone / product / service. Marcela: John Fagan, Co-founder & CEO at doorkee. Jessica: Our whole team. R – What has been the most rewarding aspect of working in PropTech? Marcela:  We're taking things from a piece of paper and turning them into something that you can engage with and interact with.  Jessica: Echo what Marcela said.  E - What are you excited about in the future of PropTech? Marcela:  Getting through 2022 and 2023 and being able to reflect back and be proud of making it through a pretty challenging market with lots of ups and downs and twists. Jessica: Keep pushing the envelope in the industry.  [36:05] Jessica: Are there any plans to come to Europe?  100% Yes Sponsors Launch Your Own Podcast Kopus.com is the leading podcast production and strategic content company for brands, organisations, institutions, individuals, and entrepreneurs. Our team sets you up with the right strategy, equipment, training, and guidance and content to ensure you sound amazing while speaking to your niche audience and networking with your perfect clients. Get in touch jason@kopus.com

Greater Than Code
271: EventStorming with Paul Rayner

Greater Than Code

Play Episode Listen Later Feb 16, 2022 58:24


00:58 - Paul's Superpower: Participating in Scary Things 02:19 - EventStorming (https://www.eventstorming.com/) * Optimized For Collaboration * Visualizing Processes * Working Together * Sticky (Post-it) Notes (https://www.post-it.com/3M/en_US/post-it/products/~/Post-it-Products/Notes/?N=4327+5927575+3294529207+3294857497&rt=r3) 08:35 - Regulation: Avoiding Overspecifics * “The Happy Path” * Timeboxing * Parking Lot (https://project-management.fandom.com/wiki/Parking_lot) * Inside Pixar (https://www.imdb.com/title/tt13302848/#:~:text=This%20documentary%20series%20of%20personal,culture%20of%20Pixar%20Animation%20Studios.) * Democratization * Known Unknowns 15:32 - Facilitation and Knowledge Sharing * Iteration and Refinement * Knowledge Distillation / Knowledge Crunching * Clarifying Terminology: Semantics is Meaning * Embracing & Exposing Fuzziness (Complexities) 24:20 - Key Events * Narrative Shift * Domain-Driven Design (https://en.wikipedia.org/wiki/Domain-driven_design) * Shift in Metaphor 34:22 - Collaboration & Teamwork * Perspective * Mitigating Ambiguity 39:29 - Remote EventStorming and Facilitation * Miro (https://miro.com/) * MURAL (https://www.mural.co/) 47:38 - EventStorming vs Event Sourcing (https://martinfowler.com/eaaDev/EventSourcing.html) * Sacrificing Rigor For Collaboration 51:14 - Resources * The EventStorming Handbook (https://leanpub.com/eventstorming_handbook) * Paul's Upcoming Workshops (https://www.virtualgenius.com/events) * @thepaulrayner (https://twitter.com/thepaulrayner) Reflections: Mandy: Eventstorming and its adjacence to Technical Writing. Damien: You can do this on a small and iterative scale. Jess: Shared understanding. Paul: Being aware of the limitations of ideas you can hold in your head. With visualization, you can hold it in more easily and meaningfully. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Transcript: MANDY: Welcome to Episode 271 of Greater Than Code. My name is Mandy Moore and I'm here today with a guest, but returning panelist. I'm happy to see Jessica Kerr. JESSICA: Thanks, Mandy. It's great to see you. I'm also excited to be here today with Damien Burke! DAMIEN: And I am excited to be here with both of you and our guest today, Paul Rayner. Paul Rayner is one of the leading practitioners of EventStorming and domain-driven design. He's the author of The EventStorming Handbook, co-author of Behavior-Driven Development with Cucumber, and the founder and chair of the Explore DDD conference. Welcome to the show, Paul. PAUL: Thanks, Damien. Great to be here. DAMIEN: Great to have you. And so you know, you are prepared, you are ready for our first and most famous question here on Greater Than Code? PAUL: I don't know if I'm ready, or prepared, but I can answer it, I think. [laughter] DAMIEN: I know you have prepared, so I don't know if you are prepared. PAUL: Right. DAMIEN: Either way, here it comes. [chuckles] What is your superpower and how did you acquire it? PAUL: Okay. So a couple of weeks ago, there's a lake near my house, and the neighbors organized a polar plunge. They cut a big hole in the ice and everyone lines up and you basically take turns jumping into the water and then swimming to the other side and climbing out the ladder. So my superpower is participating in a polar plunge and I acquired that by participating with my neighbors. There was barbecue, there was a hot tub, and stuff like that there, too. So it was very, very cool. It's maybe not a superpower, though because there were little kids doing this also. So it's not like it was only me doing it. JESSICA: I'll argue that your superpower is participating in scary things because you're also on this podcast today! PAUL: [chuckles] Yeah, there we go. DAMIEN: Yeah, that is very scary. Nobody had to be fished out of the water? No hospital, hypothermia, any of that? PAUL: No, there was none of that. It was actually a really good time. I mean, being in Denver, blue skies, it was actually quite a nice day to jump into frozen. MANDY: So Paul, you're here today to talk about EventStorming. I want to know what your definition of that is, what it is, and why it's a cool topic to be talking about on Greater Than Code. PAUL: Okay. Well, there's a few things there. So firstly, what is EventStorming? I've been consulting, working with teams for a long time, coaching them and a big part of what I try and do is to try and bridge the gap between what the engineers, the developers, the technical people are trying to build in terms of the software, and what the actual problem is they're trying to solve. EventStorming is a technique for just mapping out a process using sticky notes where you're trying to describe the story of what it is that you're building, how that fits into the business process, and use the sticky notes to layer in variety of information and do it in a collaborative kind of way. So it's really about trying to bridge that communication gap and uncover assumptions that people might have, expose complexity and risk through the process, and with the goal of the software that you write actually being something that solves the real problem that you're trying to solve. I think it's a good topic for Greater Than Code based on what I understand about the podcast, because it certainly impacts the code that you write, touches on that, and connects with the design. But it's really optimized for collaboration, it's optimized for people with different perspectives being able to work together and approach it as visualizing processes that people create, and then working together to be able to do that. So there's a lot of techniques out there that are very much optimized from a developer perspective—UML diagrams, flow charts, and things like that. But EventStorming really, it sacrifices some of that rigor to try and draw people in and provide a structured conversation. I think with the podcast where you're trying to move beyond just the code and dig into the people aspects of this a lot more, I think it really touches on that in a meaningful way. JESSICA: You mentioned that with a bunch of stickies, a bunch of different people, and their perspectives, EventStorming layers in different kinds of information. PAUL: Mm hm. JESSICA: Like what? PAUL: Yeah. So the way that usually approach it is, let's say, we're modeling, visualizing some kind of process like somebody registering for a certain thing, or even somebody, maybe a more common example, purchasing something online and let's say, that we have the development team that's responsible for implementing how somebody might return a product to a merchant, something like that. The way it would work is you describe that process as events where each sticky note represents something that happened in the story of returning a product and then you can layer on questions. So if people have questions, use a different colored sticky note for highlighting things that people might be unsure of, what assumptions they might be making, differences in terminology, exposing those types of unknowns and then once you've sort of laid out that timeline, you can then layer in things like key events, what you might call emergent structures. So as you look at that timeline, what might be some events that are more important than others? JESSICA: Can you make that concrete for me? Give me an example of some events in the return process and then…? PAUL: Yeah. So let's say, the customer receives a product that they want to return. You could have an event like customer receive product and then an event that is customer reported need for return. And then you would have a shift in actor, like a shift in the person doing the work where maybe the merchant has to then merchant sent return package to customer. So we're mapping out each one of these as an event in the process and then the customer receives, or maybe it's a shipping label. The customer receives the shipping label and then they put the items in the package with the shipping label and they return it. And then there would be a bunch of events that the merchant would have to take care of. So the merchant would have to receive that package and then probably have to update the system to record that it's been returned. And then, I imagine there would be processing another order, or something like that. A key event in there might be something like sending out the shipping label and the customer receiving the shipping label because that's a point where the responsibility transfers from the merchant, who is preparing the shipping label and dispatching that, to the customer that's actually receiving it and then having to do something. That's just one, I guess, small example of you can use that to divide that story up into what you might think of as chapters where there's different responsibilities and changes in the narrative. Part of that maybe layering in sticky notes that represent who's doing the work. Like who's the actor, whether it's the merchant, or the customer, and then layering in other information, like the systems that are involved in that such as maybe there's email as a system, maybe there's the actual e-commerce platform, a payment gateway, these kinds of things could be reflected and so on, like there's – [overtalk] JESSICA: Probably integration with the shipper. PAUL: Integration with the shipper, right. So potentially, if you're designing this, you would have some kind of event to go out to the shipper to then know to actually pick up the package and that type of thing. And then once the package is actually delivered back to the merchant, then there would be some kind of event letting the merchant know. It's very hard to describe because I'm trying to picture this in my mind, which is an inherently visual thing. It's probably not that interesting to hear me describing something that's usually done on some kind of either mirror board, like some kind of electronic space, or on a piece of butcher's paper, or – [overtalk] DAMIEN: Something with a lot of sticky notes. PAUL: Something with a lot of sticky notes, right. DAMIEN: Which, I believe for our American listeners, sticky notes are the little square pieces of brightly colored paper with self-adhesive strip on the back. PAUL: Yeah. The stickies. DAMIEN: Stickies. [chuckles] I have a question about this process. I've been involved in very similar processes and it sounds incredibly useful. But as you describe it, one of the concerns I have is how do you avoid getting over specific, or over described? Like you can describe systems until you're talking about the particles in the sun, how do you know when to stop? PAUL: So I think there's a couple of things. Number one is at the start of whatever kind of this activity, this EventStorming is laying out what's the goal? What are we trying to accomplish in terms of the process? With returns, for example, it would be maybe from this event to this event, we're trying to map out what that process looks like and you start with what you might call the happy path. What does it look like when everything goes well? And then you can use pink stickies to represent alternate paths, or things going wrong and capture those. If they're not tied back to this goal, then you can say, “Okay, I think we've got enough level of detail here.” The other thing is time boxing is saying, “Okay, well, we've only got half an hour, or we've only got an hour so let's see how much we can do in that time period,” and then at the end of that, if you still have a lot of questions, then you can – or you feel like, “Oh, we need to dig into some of these areas more.” Then you could schedule a follow up session to dig into that a little bit more. So it's a combination of the people that are participating in this deciding how much level of detail they want to go down to. What I find is it typically is something that as you're going through the activity, you start to see. “Oh, maybe this is too far down in the weeds versus this is the right level.” As a facilitator, I don't typically prescribe that ahead of time, because it's much easier to add sticky notes and then talk about them than it is to have a conversation when there's nothing visualized. I like to visualize it first and lay it out and then it's very easy to say, “Oh, well, this looks like too much detail. So we'll just put a placeholder for that and not worry about out it right now.” It's a little bit of the facilitation technique of having a parking lot where you can say, “Okay, this is a good topic, but maybe we don't need to get down in that right now. Maybe let's refocus back on what it is that we're trying to accomplish.” JESSICA: So there's some regulation that happens naturally during the meeting, during interactions and you can have that regulation in the context of the visual representation, which is the EventStorming, the long row of stickies from one event to the other. PAUL: Right, the timeline that you're building up. So it's a little bit in my mind, I watched last year, I think it was on Netflix. There was a documentary about Pixar and how they do their storyboarding process for their movies and it is exactly that. They storyboard out the movie and iterate over that again and again and again telling that story. What's powerful about that is it's a visual medium so you have someone that is sketching out the main beats of the story and then they're talking it through. Not to say that EventStorming is at that level of rigor, but it has that kind of feel to it of we're laying out these events to tell the story and then we're talking through the story and seeing what we've missed and where we need to add more detail, maybe where we've added too much detail. And then like you said, Jess, there's a certain amount of self-regulation in there in terms of, do we have enough time to go down into this? Is this important right now? JESSICA: And I imagine that when I have questions that go further into detail than we were able to go in the meeting, if I've been in that EventStorming session, I know who to ask. PAUL: That's the idea, yeah. So the pink stickies that we said represent questions, what I like about those is, well, several things. Number one, it democratizes the idea that it's okay to ask questions, which I think is a really powerful technique. I think there's a tendency in meetings for some people to hold back and other people to do all the talking. We've all experienced that. What this tries to do is to democratize that and actually make it not only okay and not only accepted, but encourage that you're expected to ask questions and you're expected to put these sticky notes on here when there's things that you don't understand. JESSICA: Putting the questions on a sticky note, along with the events, the actors, and the things that we do know go on sticky notes, the questions also go on sticky notes. All of these are contributions. PAUL: Exactly. They value contributions and what I love about that is that even people that are new to this process, it's a way for them to ask questions in a way that is kind of friendly to them. I've seen this work really well, for example, with onboarding new team members and also, it encourages the idea that we have different areas of expertise. So in any given process, or any business story, whatever you want to characterize it as, some people are going to know more about some parts of it than others. What typically happens is nobody knows the whole story, but when we work together, we can actually build up an approximation of that whole story and help each other fill in the gaps. So you may have the person that's more on the business, or the product side explaining some terminology. You can capture those explanations on sticky notes as a glossary that you're building up as you go. You can have engineers asking questions about the sequence of events in terms of well, does this one come before that one? And then the other thing that's nice about the questions is it actually as you're going, it's mapping out your ignorance and I see that as a positive thing. JESSICA: The known unknowns. PAUL: Known unknowns. It takes unknown unknowns, which the kind of elephant in the room, and at least gets them up as known unknowns that you can then have a conversation around. Because there's often this situation of a question that somebody's afraid to ask and maybe they're new to the team, or maybe they're just not comfortable asking that type of question. But it gives you actually a map of that ignorance so you can kind of see oh, there's this whole area here that just has a bunch of pink stickies. So that's probably not an area we're ready to work on and we should prioritize. Actually, if this is an area that we need to be working on soon, we should prioritize getting answers to these questions by maybe we need to do a proof of concept, or some UX work, or maybe some kind of prototyping around this area, or like you said, Jess, maybe the person that knows the answers to these questions is just not in this session right now and so, we need to follow up with them, get whatever answers we need, and then come back and revisit things. JESSICA: So you identify areas of risk. PAUL: Yes. Areas of risk, both from a product perspective and also from a technical perspective as well. DAMIEN: So what does it take to have one of these events, or to facilitate one of these events? How do you know when you're ready and you can do it? PAUL: So I've done EventStorming [chuckles] as a conference activity in a hallway with sticky notes and we say, “Okay, let's as a little bit of an icebreaker here –” I usually you do the story of Cinderella. “Let's pick the Disney story of Cinderella and we'll just EventStorm this out. Just everyone, here are some orange sticky notes and a Sharpie, just write down some things that you remember happening in that story,” and then everyone writes a few. We post it up on the hallway wall and then we sequence them as a timeline and then we can basically build up that story in about 5, or 10 minutes from scratch. With a business process, it's not that different. It's like, okay, we're going to do returns, or something like that and if people are already familiar with the technique, then just give them a minute, or so to think of some things that they know that would happen in that process. And then they do that individually and then we just post them up on the timeline and then sequence them as a group and it can happen really quickly. And then everything from there is refinement. Iteration and refinement over what you've put up as that initial skeleton. DAMIEN: Do you ever find that a team comes back a week, or a day, or a month later and goes, “Oh, there is this big gap in our narrative because nobody in this room understood the warehouse needed to be reordered in order to send this thing down”? PAUL: Oh, for sure. Sometimes it's big gaps. Sometimes it's a huge cluster of pink sticky notes that represents an area where there's just a lot of risk and unknowns that the team maybe hasn't thought about all that much. Like you said, it could be there's this third-party thing that it wasn't until everyone got in a room and kind of started to map it out, that they realized that there was this gap in their knowledge. JESSICA: Yeah. Although, you could completely miss it if there's nobody from the warehouse in the room and nobody has any idea that you need to tell the warehouse to expect this return. PAUL: Right and so, part of that is putting a little bit of thought into who would need to be part of this and in a certain way, playing devil's advocate in terms of what don't we know, what haven't we thought of. So it encourages that sense of curiosity with this and it's a little bit different from – Some of the listeners maybe have experienced user story mapping and other techniques like that. Those tend to be focused on understanding a process, but they're very much geared towards okay, how do we then figure out how we're going to code up this feature and how do we slice it up into stories and prioritize that. So it's similar in terms of sticky notes, but the emphasis in EventStorming is more on understanding together, the problem that we're trying to address from a business perspective. JESSICA: Knowledge pulling. PAUL: Yeah. Knowledge pulling, knowledge distillation, those types of idea years, and that kind of mindset. So not just jumping straight to code, but trying to get a little bit of a shared understanding of what all is the thing that we're trying to actually work on here. JESSICA: Eric Evans calls it knowledge crunching. PAUL: Yes, Eric called it knowledge crunching. DAMIEN: I love that phrase, that shared understanding. That's what we, as product teams, are generating is a shared understanding both, captured in our documentation, in our code, and before that, I guess on large sheets of butcher paper. [laughs] PAUL: Well, and it could be a quick exercise of okay, we're going to be working on some new feature and let's just spend 15 minutes just mapping it out to get a sense of, are we on the same page with this? JESSICA: Right, because sometimes it's not even about we think we need to know something, it's do we know enough? Let's find out. PAUL: Right. JESSICA: And is that knowledge shared among us? PAUL: Right, and maybe exposing, like it could be as simple as slightly different terminology, or slightly different understanding of terminology between people that can have a big impact in terms of that. I was teaching a workshop last night where we were talking about this, where somebody had written the event. So there was a repair process that a third-party repair company would handle and then the event that closed that process off, they called case closed. So then the question becomes well, what does case closed mean? Because the word case – [overtalk] JESSICA: [laughs] It's like what's the definition of done? PAUL: Right, exactly. [laughter] Because that word case didn't show up anywhere earlier in the process. So is this like a new concept? Because the thing that kicks off the process is repair purchase order created and at the end of the process, it's said case closed. So then the question becomes well, is case closed really, is that a new concept that we actually need to implement here? Or is this another way of saying that we are getting a copy of that repair purchase order back that and it's been updated with details about what the repair involved? Or maybe it's something like repair purchase order closed. So it's kind of forcing us to clarify terminology, which may seem a little bit pedantic, but that's what's going to end up in the code. If you can get some of those things exposed a little earlier before you actually jump to code and get people on the same page and surface any sort of differences in terminology and misunderstandings, I think that can be super helpful for everyone. JESSICA: Yeah. Some people say it's just semantics. Semantics' meaning, its only meaning, this is only about out what this step actually means because when you put it in the code, the code is crystal clear. It is going to do exactly what it does and whether that clarity matches the shared understanding that we think we have oh, that's the difference between a bug and a working system. DAMIEN: [laughs] That's beautiful. It's only meaning. [laughs] JESSICA: Right? Yeah. But this is what makes programming hard is that pedanticness. The computer is the ultimate pedant. DAMIEN: Pedant. You're going to be pedantic about it. [laughter] PAUL: I see what you did there. [laughter] DAMIEN: And that is the occupation, right? That is what we do is look at and create systems and then make them precise. JESSICA: Yeah. DAMIEN: In a way that actually well, is precise. [laughs] JESSICA: Right, and the power of our human language is that it's not precise, that it allows for ambiguity, and therefore, a much broader range of meaning. But as developers, it's our job to be precise. We have to be precise to the computers. It helps tremendously to be precise with each other. DAMIEN: Yeah, and I think that's actually the power of human cognition is that it's not precise. We are very, very fuzzy machines and anyone who tries to pretend otherwise will be greatly disappointed. Ask me how I know. [laughter] PAUL: Well, and I think what I'm trying to do with something like EventStorming is to embrace the fuzziness, is to say that that's actually an asset and we want to embrace that and expose that fuzziness, that messiness. Because the processes we have and work with are often inherently complex. We are trying to provide some visual representation of that so we can actually get our head around, or our minds around the language complexities, the meanings, and drive in a little bit to that meaning. JESSICA: So when the sticky notes pile on top of each other, that's a feature. PAUL: It is. Going back to that example I was just talking about, let's say, there's a bunch of, like we do the initial part of this for a minute, or so where people are creating sticky notes and let's say, we end up with four, or five sticky notes written by different people on top of each other that end up on the timeline that all say pretty much the same thing with slight variations. JESSICA: Let's say, case closed, request closed. PAUL: Case closed, repair purchase order closed, repair purchase order updated, repair purchase order sent. So from a meaning perspective, I look at that and I say, “That's gold in terms of information,” because that's showing us that there's a richness here. Firstly, that's a very memorable thing that's happening in the timeline – [overtalk] JESSICA: Oh and it has multiple things. PAUL: That maybe means it's a key event. Right, and then what is the meaning? Are these the same things? Are they different things? Maybe we don't have enough time in that session to dig into that, but if we're going to implement something around that, or work with something around that, then we're going to at some point need some clarity around the language, the terminology, and what these concepts mean. Also, the sequence as well, because it might be that there's actually multiple events being expressed there that need to be teased apart. DAMIEN: You used this phrase a couple times, “key event,” and since you've used it a couple times, I think it might be key. [laughter] Can you tell us a little bit about what a key event is? What makes something a key event? PAUL: Yeah, the example I like to use is from the Cinderella story. So if you think about the story of Cinderella, one of the things, when people are doing that as an icebreaker, they always end up being multiple copies of the event that usually is something like shoe lost, or slipper lost, or glass slipper lost. There's something about that event that makes it memorable, firstly and then there's something about that event that makes it pivotal in the story. For those that are not familiar with the story [chuckles]—I am because I've EventStormed this thing maybe a hundred times—but there's this part. Another key event is the fairy godmother showing up and doing the magic at the start and she actually describes a business policy. She says, “The magic is going to run out at midnight,” and like all business policies, it's vague [laughter] and it's unclear as to what it means because – [overtalk] JESSICA: The carriage disappears, the dress disappears, but not the slipper that fell off. PAUL: Exactly. There's this exception that for some bizarre reason, to move the plot forward, the slipper stays. But then the definition of midnight is very hazy because what she's actually describing, in software terms, is a long running process of the clock banging 12 times, which is what midnight means is the time between the first and the twelfth and during that time, the magic is slowly unraveling. JESSICA: So midnight is a duration, not an instant. PAUL: Exactly. Yes, it's a process, not an event. So coming back to the question that Damien asked about key events. That slipper being lost is a key event in that story, I think because it actually is a shift in narrative. Up until that point in the story, it's the story of Cinderella and then after that, once the slipper is lost, it becomes the story of the prince looking for Cinderella. And then at the end, you get the day tomorrow, the stuff that happens with that slipper at the end of the story. Another key event would be like the fairy godmother showing up and doing the magic. DAMIEN: [chuckles] It seems like these are necessary events, right? If the slipper is not lost, if the fairy godmother doesn't do magic, you don't have the story of Cinderella. PAUL: Right. These are narrative turns, right? DAMIEN: Yeah. PAUL: These are points of the story shifts and so, key events can sometimes be a narrative shift where it's driving the story forward in a business process. Something like, let's say, you're working on an e-commerce system, like order submitted is a key event because you are adding items to a shopping cart and then at some point, you make a decision to submit the order and then at that point, it transitions from order being a draft thing that is in a state of flux to it actually becomes essentially immutable and gets passed over to fulfilment. So there's a shift in responsibility and actor between these two as well just like between Cinderella and the prince. JESSICA: A shift in who is driving the story forward. PAUL: Right. Yeah. So it's who is driving the story forward. So these key events often function as a shift in actor, a shift in who's driving the story forward, or who has responsibility. They also often indicate a handoff because of that from one group to another in an organization. Something like a sales process that terminates in contract signed. That key event is also the goal of the sales process. The goal is to get to contract signed and then once that happens, there's usually a transition to say, an onboarding group that actually onboards the new customer in the case of a sales process for a new customer, or in e-commerce, it would be the fulfillment part, the warehousing part that Jess was talking about earlier. That's actually responsible for the fulfillment piece, which is they take that order, they create a package, they put all the items in the package, create the shipping label, and ship it out to the customer. JESSICA: And in domain-driven design, you talked about the shift from order being a fluid thing that's changing as people add stuff to their cart to order being immutable. The word order has different meanings for the web site where you're buying stuff and the fulfillment system, there's a shift in that term. PAUL: Right, and that often happens around a key event, or a pivotal event is that there's a shift from one, you might think of it as context, or language over to another. So preorder submission, it's functioning as a draft order, but what it's actually typically called is a shopping cart and a shopping cart is not the same as an order. It's a great metaphor because there is no physical cart, but we all know what that means as a metaphor. A shopping cart is a completely different metaphor from an order, but we're able to understand that thread of continuity between I have this interactive process of taking items, or products, putting them in the shopping cart, or out again. And then at some point that shopping cart, which is functioning as a draft order, actually it becomes an order that has been submitted and then it gets – [overtalk] DAMIEN: Yeah, the metaphor doesn't really work until that transition. You have a shopping cart and then you click purchase and now what? [laughs] You're not going to the register and ringing it up, that doesn't make any sense. [chuckles] The metaphor kind of has to end there. JESSICA: You're not leaving the cart in the corral in the parking lot. [laughter] PAUL: Well, I think what they're trying to do is when you think about going through the purchase process at a store, you take your items up in the shopping cart and then at that point, you transition into a financial transaction that has to occur that then if you were at a big box electronic store, or something, eventually, you would make the payment. You would submit payment. That would be the key events and that payment is accepted and then you receive a receipt, which is kind of the in-person version of a record of your order that you've made because you have to bring the receipt back. DAMIEN: It sort of works if the thing you're putting in the shopping cart are those little cards. When they don't want to put things on the shelf, they have a card, you pick it up, and you take it to register. They ring it up, they give you a receipt, and hopefully, the thing shows up in the mail someday, or someone goes to the warehouse and goes gets it. PAUL: We've all done that. [chuckles] Sometimes it shows up. Sometimes it doesn't. JESSICA: That's an interesting point that at key events, there can be a shift in metaphor. PAUL: Yes. Often, there is. So for example, I mentioned earlier, a sales process ending in a contract and then once the contract is signed, the team – let's say, you're signing on a new customer, for a SaaS service, or something like that. Once they've signed the contract, the conversation isn't really about the contract anymore. It's about what do we need to do to onboard this customer. Up until that point, the emphasis is maybe on payment, legal disclosures, and things like that. But then the focus shifts after the contract is signed to more of an operational focus of how do we get the data in, how do we set up their accounts correctly, that type of thing. JESSICA: The contract is an input to that process. PAUL: Yes. JESSICA: Whereas, it was the output, the big goal of the sales process. PAUL: Yes, exactly. So these key events also function from a systems perspective, when you think about moving this to code that event then becomes almost like a message potentially. Could be implemented as say, a message that's being passed from the sales system through to the onboarding system, or something like that. So it functions as the integration point between those two, where the language has to be translated from one context to another. JESSICA: And it's an integration point we can define carefully so that makes it a strong boundary and a good place to divide the system. DAMIEN: Nice. PAUL: Right. So that's where it starts to connect to some of the things that people really care about these days in terms of system decomposition and things like that. Because you can start thinking about based on a process view of this, based on a behavior view of this, if we treat these key events as potential emergent boundaries in a process, like we've been describing, that we discover through mapping out the process, then that can give us some clues as to hmm maybe these boundaries don't exist in the system right now, but they could. These could be places where we start to tease things apart. JESSICA: Right. Where you start breaking out separate services and then when you get down to the user story level, the user stories expect a consistent language within themselves. You're not going to go from cart to return purchase in a case. PAUL: [laughs] Right. JESSICA: In a single user story. User stories are smaller scope and work within a single language. PAUL: Right and so, I think the connection there in my mind is user stories have to be written in some kind of language, within some language context and mapping out the process can help you understand where you are in that context and then also understand, like if you think about a process that maybe has a sales part of the process and then an onboarding part, it'll often be the case that there's different development teams that are focusing on different parts of that process. So it provides a way of them seeing what their integration point is and what might need to happen across that integration point. If they were to either integrate to different systems, or if they're trying to tease apart an existing system. To use Michael Feathers' term, what might be a “scene” that we could put in here that would allow us to start teasing these things apart. And doing it with the knowledge of the product people that are part of the visualization, too is that this isn't something typically that engineers do exclusively from a technical perspective. The idea with EventStorming is you are also bringing in other perspectives like product, business, stakeholders, and anyone that might have more of that business perspective in terms of what the goals of the process are and what the steps are in the process. MID-ROLL: And now a quick word from our sponsor. I hear people say the VPNs have a reputation for slowing down your internet speed, but not with NordVPN, because it's the fastest VPN in the world. I don't have to sacrifice internet speed for better security. With NordVPN, my internet traffic is routed through a secure encrypted tunnel, which protects my data and privacy. I can also have it on up to six devices like my laptop, phone, TV, iPad—all my devices are protected. Grab your exclusive NordVPN deal by going to nordvpn.com/gtc, or use the code GTC to get a huge discount on your NordVPN plan plus one additional month for free. Plus, a bonus gift! It's completely risk-free with Nord's 30-day money back guarantee. JESSICA: As a developer, it's so important to understand what those goals are, because that lets us make good decisions when we're down in the weeds and getting super precise. PAUL: Right, I think so. I think often, I see teams that are implementing stories, but not really understanding the why behind that in terms of maybe they get here's the functionality on delivering and how that fits into the system. But like I talked about before, when you're driving a process towards a key event, that becomes the goal of that subprocess. So the question then becomes how does the functionality that I'm going to implement that's described in this user story actually move people towards that goal and maybe there's a better way of implementing it to actually get them there. DAMIEN: Yeah, it's always important to keep that in mind, because there's always going to be ambiguity until you have a running system, or ran system, honestly. JESSICA: Yeah! DAMIEN: There's always going to be ambiguity, which it is our job as people writing code to manage and we need to know. Nobody's going to tell us exactly what's going to happen because that's our job. PAUL: Right. JESSICA: It's like if the developer had a user story that Cinderella's slipper fell off, but they do didn't realize that the goal of that was that the prince picked it up, then they might be like, “Oh, slipper broke. That's fine.” PAUL: Yeah. JESSICA: It's off the foot. Check the box. PAUL: Let's create a glass slipper factory implementer object [laughter] so that we can just create more of those. JESSICA: Oh, yeah. What, you wanted a method slip off in one piece? You didn't say that. I've created crush! PAUL: Right. [laughter] Yeah. So I think sometimes there's this potential to get lost in the weeds of the everyday development work that is happening and I like to tie it back to what is the actual story that we're supporting. And then sometimes what people think of as exception cases, like an example might be going back to that merchant return example is what if they issue the shipper label, but the buyer never receives it. We may say, “Well, that's never going to happen,” or “That's unlikely.” But visualizing that case, you may say, “That's actually a strong possibility. How do we handle that case and bake that into the design so that it actually reflects what we're trying to do?” JESSICA: And then you make an event that just triggers two weeks later that says, “Check whether customer received label.” PAUL: Yes, exactly. One thing you can do as well is like – so that's one possibility of solving it. The idea what EventStorming can let you do is say, “Well, that's one way of doing it. Are there any other options in terms of how we could handle this, let's visualize.” With any exception case, or something, you could say, “Well, let's try solving this a few different ways. Just quickly come up with some different ideas and then we can pull the best of those ideas into that.” So the idea when you're modeling is to say, “Okay, well, there's probably more than one way to address this. So maybe let's get a few ideas on the table and then pick the best out of these.” JESSICA: Or address it at multiple levels. PAUL: Yes. JESSICA: A fallback for the entire process is customer contact support again. PAUL: Right, and that may be the simple answer in that kind of case. What we're trying to do, though is to visualize that case as an option and then talk about it, have a structured conversation around it, say, “Well, how would we handle that?” Which I think from a product management perspective is a key thing to do is to engage the engineers in saying, “Well, what are some different ways that we could handle this and solve this?” If you have people that are doing responsibility primarily for testing in that, then having them weigh in on, well, how would we test this? What kind of test cases might we need to handle for this? So it's getting – [overtalk] JESSICA: How will we know it worked? PAUL: Different perspectives and opinions on the table earlier rather than later. JESSICA: And it's cheap. It's cheap, people. It's a couple hours and a lot of post-its. You can even buy the generic post-its. We went to Office Depot yesterday, it's $10 for 5 little Post-it pads, [laughter] or 25 Office Depot brand post-it pads. They don't have to stay on the wall very long; the cheap ones will work. PAUL: [laughs] So those all work and then it depends if you have shares in 3M, I guess, with you. [laughter] Or Office Depot, depending which road you want to go down. [laughter] JESSICA: Or if you really care about that shade of pale purple, which I do. PAUL: Right. I mean, what's been fascinating to me is in the last 2 years with switching to remote work and that is so much of, 95% of the EventStorming I do these days is on a collaborative whiteboard tool like Miro, or MURAL, which I don't know why those two product names are almost exactly the same. But then it's even cheaper because you can sign up for a free account, invite a few people, and then just start adding sticky notes to some virtual whiteboard and do it from home. There's a bunch of things that you can do on tool like that with copy pasting, moving groups of sticky notes around, rearranging things, and ordering things much – [overtalk] JESSICA: And you never run out of wall. PAUL: Yeah. The idea with the butcher's paper in a physical workshop, in-person workshop is you're trying to create a sense of unending modeling space that you can use. That you get for free when you use online collaborative whiteboarding tool. It's just there out of – [overtalk] JESSICA: And you can zoom in. PAUL: And you zoom in and out. Yeah. There's a – [overtalk] JESSICA: Stickies on your stickies on your stickies. [laughter] I'm not necessarily recommending that, but you can do it. PAUL: Right. The group I was working with last night, they'd actually gone to town using Miro emojis. They had something bad happen in the project and they've got the horror emoji [laughter] and then they've got all kinds of and then copy pasting images off the internet for things. JESSICA: Nice. PAUL: So yeah, can make it even more fun. JESSICA: Okay. So it's less physical, but in a lot of ways it can be more expressive, PAUL: I think so. More expressive and just as engaging and it can break down the geographical barriers. I've done sessions where we've had people simultaneously spread in multiple occasions across the US and Europe in the same session, all participating in real-time. If you're doing it remote, I like to keep it short. So maybe we do like a 2-hour session with a 10- or 15-minute break in the middle, because you're trying to manage people's energy and keep them focused and it's hard to do that when you just keep going. MANDY: I kind of want to talk a little bit about facilitation and how you facilitate these kind of workshops and what you do, engage people and keep them interested. PAUL: Yeah. So I think that it depends a little bit on the level of detail we're working at. If it's at the level of a few team members trying to figure out a feature, then it can be very informal. Not a lot of facilitation required. Let's just write down what the goal is and then go through the process of brainstorming a few stickies, laying it out, and then sequencing it as a timeline, adding questions. It doesn't require a lot of facilitation hand. I think the key thing is just making sure that people are writing down their questions and that it's time boxed. So quitting while people are still interested and then [laughter] at the end, before you finish, having a little bit of a conversation around what might the next steps be. Like what did we learn? You could do a couple of minutes retrospective, add a sticky note for something you learned in this session, and then what do you see as our next steps and then move on from there with whatever action items come out of that. So that one doesn't require, I think a lot of facilitation and people can get up and running with that pretty quickly. I also facilitate workshops that are a lot more involved where it's at the other end of the spectrum, where it's a big picture workshop where we're mapping out maybe an entire value stream for an organization. We may have a dozen, 20 people involved in a session like that representing different departments, different organizational silos and in that case, it requires a lot more planning, a lot more thinking through what the goal of the workshop is, who would you need to invite? Because there's a lot more detail involved and a lot more people involved, that could be four, or five multi-hour sessions spread over multiple days to be able to map out an entire value stream from soup to nuts. And then usually the goal of something like that is some kind of system modernization effort, or maybe spinning up a new project, or decomposing a legacy system, or even understanding what a legacy system does, or process improvement that will result inevitably in some software development in certain places. I did a workshop like that, I think last August and out of that, we identified a major bottleneck in the process that everyone in the workshop, I think it was just a bunch of pink stickies in one area that it got called the hot mess. [laughter] It was one area and what was happening was there were several major business concerns that were all coupled together in this system. They actually ended up spinning up a development team to focus on teasing apart the hot mess to figure out how do we decompose that down? JESSICA: Yes. PAUL: As far as I know, that effort was still ongoing as of December. I'm assuming that's still running because it was prioritized as we need to be able to decompose this part of this system to be able to grow and scale to where we want to get to. JESSICA: Yeah. That's a major business risk that they've got. They at least got clarity about where it is. PAUL: Right. Yeah, and what we did from there is I coached the developers through that process over several months. So we actually EventStormed it out at a much lower level. Once we figured out what the hot mess was, let's map it out and then they combined that with some flow charting and a bunch of other more engineering, kind of oriented visualization techniques, state machines, things like that to try and get a handle on what was going on. DAMIEN: We'll get UML in there eventually, right? PAUL: Eventually. [laughter] You can't do software development without some kind of state machine, sequence diagram. JESSICA: And it's approximating UML. You can't do it. You can't do it. [laughter] You will either use it, or you will derive a pigeon form of it. PAUL: Right. Well, I still use it for state diagrams and sequence diagrams when I'm down at that technical level. What I find is that there's a certain level of rigor that UML requires for a sequence diagram, or something like that that seems to get in the way of collaboration. So EventStorming sacrifices some of that rigor to be able to draw in everyone and have a low bar of entry to having people participate. DAMIEN: That's a huge insight. Why do you think that is? Is it the inability to hold that much information at a high level of rigor, or just people not used to working at that sort of precision and rigor? PAUL: I think that when I'm working with people that are not hands-on coders, they are in the everyday, like say, product managers, or stakeholders, to use those terms. They're in the everyday details of how the business process works and they tend to think of that process more as a series of steps that they're going through in a very specific kind of way. Like, I'm shipping a certain product, or supporting the shipping. or returning of certain types of products, those kinds of things. Whereas, as developers, we tend to think of it more in terms of the abstractions of the system and what we're trying to implement in the code. So the idea of being able to tell the story of a process in terms of the events that happen is a very natural thing, I find for people from a business perspective to do because that's how they tend to think about it. Whereas, I think as programmers, we're often taught not so much to think about behavior as a sequence of things happening, but more as the structure we've been taught to design in terms of structures and relationships rather than flow. JESSICA: Yet that's changing with event sourcing. PAUL: I think so. EventStorming and event sourcing become a very natural complement for each other and even event-driven architecture, or any event-driven messaging, whatever it happens to be. The gap between modeling using EventStorming and then designing some kind of event-driven distributed system, or even not distributed, but still event-driven is much more natural than trying to do something like an entity relationship diagram and they'd get from that to some kind of meaningful understanding of what's the story of how these functions and features are going to work. JESSICA: On the topic of sacrificing rigor for collaboration, I think you have to sacrifice rigor to work across content texts because you will find contradictions between them. The language does have different meaning before and after the order is submitted and you have to allow for that in the collaboration. It's not that you're not going to have the rigor. It's more that you're postponing it, you're scoping it as separately. This meeting is about the higher level and you need completeness over consistency. DAMIEN: Yeah. I feel like almost you have to sacrifice rigor to be effective in most roles and in that way, sacrifice is even the wrong word. Most of the things that we do as human beings do not allow for the sort of rigor of the things that we do as software engineers and things that computers do. JESSICA: Yeah. DAMIEN: And it's just, the world doesn't work that way. PAUL: Right. Well, and it's the focus in EventStorming on exploration, discovery, and urgent ideas versus rigor is more about not so much exploring and discovery, but about converging on certain things. So when someone says pedant and the other person says pedant, or vice versa, that tends to shut down the conversation because now you are trying to converge on some agreed upon term versus saying, “Well, let's explore a bunch of different ways this could be expressed and temporarily defer trying converge on.” JESSICA: Later in Slack, we'll vote. PAUL: Yes. JESSICA: Okay. So standardize later. PAUL: Yes. Standardize, converge later, and for now, let's kind of hold that at arm's length so that we can uncover and discover different perspectives on this in terms of how the story works and then add regulator when we go to code and then you may discover things in code where there are implicit concepts that you then need to take back to the modeling to try and figure out well, how do we express this? Coming up with some kind of term in the code and being able to go from there. JESSICA: Right. Some sort of potential return because it hasn't happened yet. PAUL: Exactly. So maybe it's a potential, maybe it's some other kind of potential return, like pending return, maybe we don't call it a return at all. JESSICA: Or disliked item because we could – or unsatisfactory item because we could intercept that and try to like, “Hey, how about we send you the screws that we're missing?” PAUL: Right. Yeah, maybe the answer is not a return at all. JESSICA: Yeah. PAUL: But maybe the case is that the customer says they want to return it, but you actually find a way to get them to buy more stuff by sending them something else that they would be happy with. So the idea is we're trying to promote discovery thinking when we are talking about how to understand certain problems and how to solve them rather than closing off options too soon. MANDY: So, Paul, I know you do give these workshops. Is there anything? Where can people find you? How can people learn more? How can people hire you to facilitate a workshop and get in touch with you? PAUL: Okay. Well, in terms of resources, Damien had mentioned at the beginning, I have an eBook up on Leanpub, The EventStorming Handbook, so if people are interested in learning more, they can get that. And then I do workshop facilitation and training through my company, Virtual Genius. They can go to virtualgenius.com and look at what training is available. It's all online these days, so they can participate from anywhere. We have some public workshops coming up in the coming months. And then they can find me, I'm @ThePaulRayner on Twitter, just to differentiate me from all the indefinite articles that are out there. [laughter] MANDY: Sounds good. Well, let's head into reflections. I can start. I just was thinking while we were talking about this episode, about how closely this ties into my background in professional writing, technical writing to be exact, and just how you have this process to lay out exactly what steps need to be taken and to differentiate when people say the same things and thinking about, “Well, they're saying the same things, but the words matter,” and to get pedantic, that can be a good thing, especially when you are writing technical documents and how-tos. I remember still, my first job being a technical writer and looking at people in a machine shop who it was like, first, you do this, then you do this, then you do this and to me, I was like, “This is so boring.” But it makes sense and it matters. So this has been a really good way for me to think about it as a newbie just likening it to technical writing. JESSICA: Yeah. Technical writing has to tell that story. DAMIEN: I'm going to be reflecting on this has been such a great conversation and I feel like I have a lot of familiarity with at least a very similar process. I brought up all my fears that come from them, which is like, what if we don't have the right person in the room? What if there's something we didn't discover? And you said something about how you can do this in 5 minutes and how you can do this in 15 minutes and I realized, “Oh, this process doesn't have to be the 6-hour things that I've participated in and facilitated in. It can also be done more smaller and more iteratively and I can bring this sort of same process and thought process into more of the daily work.” So that's super helpful for me. JESSICA: I want to reflect on a phrase that Paul said and then Damien emphasized, which is shared understanding. It's what we're trying to get to in EventStorming across teams and across functions. I think it's also like what we're constantly trying to get to as humans. We value shared understanding so much because we're trapped in our heads and my experience in my head is never going to be the same as your experience in your head. But at some point, we share the same physical world. So if we can get that visual representation, if we can be talking together about something in that visual world, we can pass ideas back and forth more meaningfully. We can achieve this shared understanding. We can build something together. And that feels so good. I think that that constant building of shared understanding is a lot of what it means to be human and I get really excited when I get to do that at work. PAUL: I think I would just add to that as well is being human, I'm very much aware of limitations in terms of how many ideas I can hold in my head at any one time. I know the times where I've been in the experience that many describe where someone's giving me a list of steps to follow and things like that, inevitably I'm like, “Well, I remember like the first two, maybe three,” and then everything after that is kind of Charlie Brown. What, what, why? [laughter] I don't remember anything they said from that point on. But when I can visualize something, then I can take it in one go. I can see it and we're building it together. So for me, it's a little bit of a mind hack in terms of getting over the limitations of how many things I can keep in my mind at one time. Also, like you said, Jess, getting those things out of my mind and out of other people's minds into a shared space where we can actually collaborate on them together, I think that's really important to be able to do that in a meaningful way. MANDY: Well, thank you so much for coming on the show today, Paul. We really enjoyed this discussion. And if you, as listeners, would like to continue this conversation, please head over to Patreon.com/greaterthancode. We have a Slack channel. You can pledge and donate to sponsor us as little as a dollar and you can come in, hang out, talk with us about these episodes. If not, give me a DM on Twitter and let me know, and I'll let you in anyway because [laughter] that's what we do here at Greater Than Code. PAUL: Because Mandy's awesome. MANDY: [laughs] Thank you, Paul. With that, thank you everyone for listening and we'll see you again next week. Special Guest: Paul Rayner.

Tough Girl Podcast
Jessica Hepburn - Adventure Activist - Her journey to climbing Mt. Everest and completing her “Pond to Peak” Challenge.

Tough Girl Podcast

Play Episode Listen Later Feb 8, 2022 50:45


Jessica's ‘adventure activism' is, by her own admission, a bit of an accident as she hates exercise and considers herself to be the most unlikely athlete.    However, over the last decade she has been taking on some of the world's most iconic physical and mental endurance challenges to turn the sadness she's been through into something positive and at the same time raise awareness of what it means to struggle to conceive and to encourage new ways of thinking about family.    She has run the London Marathon; swum the English Channel; and is still on her journey to climb Mount Everest and complete the iconic ‘Pond to Peak' Challenge.    She is a member of the British Mountaineering Council; The Ramblers; The Long Distance Walkers Association; and the Serpentine, Hampstead Ponds and Dover Open Water Swimming Clubs; and has used her sporting challenges to raise thousands of pounds for charity including Fertility Network UK.   We first spoke to Jessica in Oct 2018 - you can listen to that episode here:    https://www.toughgirlchallenges.com/single-post/jessica-hepburn    New episodes of the Tough Girl Podcast go live every Tuesday and Thursday at 7am UK time - Hit the subscribe button so you don't miss out.    The Tough Girl Podcast is sponsorship and ad free thanks to the monthly financial support of patrons.    Support the mission to increase the amount of female role models in the media. Visit www.patreon.com/toughgirlpodcast and subscribe - super quick and easy to do and it makes a massive difference. Thank you.   Show notes Who is Jessica How she would describe herself and what she does Dealing with a decade long struggle on trying to conceive  Wanting to do something different with her life Completing her childhood dream of swimming the English Channel  Being an adventure activist  Wanting to be the first women to complete the “Pond to Peak” Challenge What Jessica was up to in 2019 Making a change in her career and setting up her own arts' festival  Her dream of heading to Everest in 2020 Climbing Mt. Elbrus and having a tough time Swimming to get fit for climbing mountains Climbing Mt. Kilimanjaro in 2015/2016 Why the Everest journey has been so hard  Being an unlikely mountaineer and athlete  When things don't go according to plan  Having to learn from failure Does swim training translate to walking in the mountains? The benefits of cold water and why she does it regularly  Not being fast enough on the mountains Needing to get into strength training and build muscle Heading to the peak district and the Lake District Training with the Elite Ramblers in the UK  Dealing with the first lockdown in 2020 Being able to stop, slow down and relax Finding the blessings  How lockdown impacted on motivation for training and keeping fit The different types of adventures  Why adventure has become such an important part of her life Getting the confirmation that Everest was going to go ahead in 2021 Getting to base camp and feeling prepared How everyone has an opinion on Everest Why her expedition was a non summit Dealing with cyclones at camp 2 Cyclones, Chest Infections and Covid Making a rookie mistake Why you need a buff!!! Making the decision to turn back… Acceptance and coming to peace  Why climbing mountains have become so meaningful Making it a battle - a battle with nature Wanting to go back in the future Turning 50 at the end of 2020 How to follow along with Jessica and her future adventures  Final words of advice to motivate and inspire more women to take their next steps into the world of adventure   Social Media   Website: www.jessicahepburn.com    Instagram: @jessica_hepburn_    Facebook: @jessicahepburnauthor    Twitter: @JessicaPursuit     

Greater Than Code
237: Empathy is Critical with Andrea Goulet

Greater Than Code

Play Episode Listen Later Jun 2, 2021 55:10


01:13 - Andrea's Superpower: Distilling Complexity * Approaching Copywriting in a Programmatic Way * Word-land vs Abstract-land 09:00 - “Technical” vs “Non-Technical” * This or That Thinking 16:20 - Empathy is Critical * Communication Artifacts * Audience/User Impact * Programmer Aptitude Test (PAT) 33:00 - Reforming Hiring Practices and Systems * Core Values * Exercism.io (https://exercism.io/) * Retrospectives 39:28 - Performance Reviews * Continuous Feedback * Brave New Work by Aaron Dignan (https://www.bravenewwork.com/) * Team of Teams: New Rules of Engagement for a Complex World (https://www.amazon.com/Team-Teams-Rules-Engagement-Complex/dp/1591847486) * Continuous Improvement & Marginal Gains “Start where you are. Use what you have. Do what you can.” ~ Arthur Ashe Empathy In Tech (https://www.empathyintech.com/) Corgibytes (https://corgibytes.com/) Reflections: Mando: Empathy is being able to view and identify other perspectives. Jess: Help happens when you have empathy for individuals who aren't the great majority of people using the software. Casey: The best way to develop empathy for someone else is to get their feedback. Do it during an interview! Andrea: Diving deeper than code is valuable! This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Transcript: JESSICA: Good morning and welcome to Greater Than Code, Episode 237. I'm Jessica Kerr and I'm happy to be here today with my friend, Mando Escamilla! MANDO: Hey, Jess. Thanks. I am happy to be here with my friend, Casey Watts. CASEY: Hi, I'm Casey and we're all here with Andrea Goulet. Andrea is a sought-after keynote speaker for conferences around the world, empowering audiences to deepen their technical skills for understanding and communicating with others. She is best known for her work defining Empathy-Driven Development, a framework that helps software engineers anchor their decisions and deliverables on the perspectives of the people who will be impacted by what they create. Andrea is a co-founder of Corgibytes, a software consultancy that helps organizations pay down technical debt and modernize legacy systems. You can recognize her by the JavaScript tattoo on her wrist. Welcome, Andrea. ANDREA: Hi, welcome! Nice to be here. CASEY: We always like to start with a question, which I think you're prepared for, that is what is your superpower, Andrea, and how did you acquire it? ANDREA: Yeah! First of all, I just love that y'all ask this. I think it's just such a nice way to get to know different people. I was thinking about this because you sent it a little bit ago and I was thinking maybe empathy, given the work I do. But I don't actually think that's it. I feel like I'm constantly trying to learn more about empathy, but I do think that what my superpower is, is distilling complexity. So I went back and looked at what the thread is of all the recommendations I've got on LinkedIn and things like that. It's not something that I would necessarily say that I noticed, but it's something that other people have noticed about me. The idea of taking a really abstract and big, gnarly, complex topic, and being able to distill it down to its essence and then communicate either what the importance is, or what the impact is to other people. I think that's why I've gravitated towards big, gnarly things like legacy code. [chuckles] Because what motivates me is impact and how do we have the work that we do make as big of an impact as possible? So the way I got into software was really a twisty and windy road. I started out as a copywriter and I think that's where the distilling complexity comes down because I would sit with clients and learn all about their businesses. And then I would write typically, a website, or some kind of marketing material and they would say, “You said what was in my head and I couldn't say it.” JESSICA: Wow. ANDREA: And when I got into software, I had a friend of mine from high school, Scott, who's my co-founder at Corgibytes, he came up to me because I had been writing about my writing and he said, “You're not a writer, you're actually a programmer because the way that your brain works, you're thinking in terms of inputs and manipulating data and outputs, and that's exactly what a programmer does.” So then, he wanted to fix legacy code for a living. I didn't even know what that was at that point, thought it was a good thing and I found that my ability to both walk in and understand not just the syntax of what's going on, but the business challenges and how everything links together. With that, you can create a sense of cohesion on a team and getting different people to work together and different people to see each other's points of view, because when you're able to distill a perspective over here and say, “Okay, well, this is what this person's trying to say,” and still, this over here. “Okay, I think this is what this person's trying to say.” I feel like a lot of times I am kind of like a translator, but it's taken me a long time. I've been in software 12 years now and I still have massive imposter syndrome like, I don't belong because I'm not the fastest person on the keyboard. I really struggle with working memory. My visualization is really a struggle, but I do really great in an ensemble. When I started ensemble programming—sometimes it's referred to as mob programming—I was like, “I can do this. Oh my gosh, this makes sense and I belong.” I think just over the years, little things like hearing the joke – I was at a conference, Jess, I think this may have been ETE when you and I connected, but I heard a joke and it was, I think Phil Carlton had first said it and it was like, “There's only two hard problems in computer science, cache invalidation and naming things,” and then somebody else said, “Off-by-1 errors.” I remember I was like, “Y'all think naming things is hard?” Like, help me understand how that's hard because that's – JESSICA: [inaudible]? Oh my gosh, that's hard. ANDREA: Yeah, and to me, it just comes so naturally. I think that's kind of the thing is figuring out where is your trait, where's your skillset. I remember when I first started doing open source contributions, I haven't done those in a long time, but just going in and modifying the language on help messages and turning them from passive to active voice. They got accepted, it was on some high-profile projects, and it was like, I didn't really feel like I was even doing much and I still feel like, “Is that even a big deal?” But I think that's kind of the definition of a superpower a little bit is that – JESSICA: Yeah, it's easy for you. [laughs] ANDREA: You don't recognize that it's hard for other people. Yeah, and so it's neat now that it's like I'm starting to come into my own and leaning into that, and then helping other people see that the way that I approach naming things, the way I approach copywriting is actually in a very programmatic way. It's leaning on frameworks. It's leaning on patterns that I use over time. I know, Casey, you and I have talked last week about like when I first go to a conference like using open-ended questions versus closed-ended questions and these little kind of communication hacks that I've developed over the years. So now putting those together in a framework to help other people remember that when we're coding, we're not coding for a computer, we're coding through a computer for other people. The computer is just like a code is just a tool. It's a powerful tool. But a lot of times – CASEY: I have a question for you, Andrea. ANDREA: Yeah. CASEY: About that, I find myself switching gears between word land and abstract land. So if I'm coding and I'm not thinking of words, the naming is hard, but sometimes I can switch gears in a different head space. It's like a different me and then I'm naming things really well. Especially if I'm looking at someone else's code, I don't have to be an abstract land; they did that part already. Do you find yourself switching between the two? ANDREA: Oh, all the time. Yeah, and especially, too, when you're writing prose. There's two different kind of aspects of your brain. There's the creative conceptual side and then there's the analytical rational side and everybody has both. So it does require you to come out of the abstract side in that and then move into more of the analytical space, which is why I love pairing. I love coding as a group because then that way, it's like the mental model is shared and so, I can stay in my world of naming things really well, or I don't know that we need to be that precise if we try to – like, when I was in one group and they were trying to have a timing thing and it was like down to the millisecond and I was like, “Y'all, we don't need to be that precise. We just need to have this check once every 10 minutes,” and that saved like 6 hours of work. Just being able to say that thing and be the checkpoint. JESSICA: Yeah. Someone has to be super down in the details of what to type next and it helps to have someone else thinking about it at the broader perspective of why are we doing this? ANDREA: Yeah, and that's me, typically and I love that role, but it's very different than I think what goes through people's minds when they envision a software developer. JESSICA: Yeah, maybe they envisioned the things that software developers do that other people don't. Typing curly braces. ANDREA: Yeah. MANDO: I still think of that when I'm doing it. When I think of myself as a software developer, I think of myself as the person who hasn't gotten up from their desk in 5 hours and just hunched over, just blazing fast hacking on something that probably is kind of dumb. [laughter] But when I don't spend my day like that, I don't really feel exactly like I've been doing my job and it's something that I struggle with because I know that's not the job in its totality by any means and it doesn't mean that I'm not getting good work done. JESSICA: Not even close to most of the job. MANDO: Not even close to most of the job, you're exactly right. JESSICA: Like you said, if you're sitting there for 5 hours by yourself, hunched over your computer, you're probably hacking on something dumb. MANDO: Right. [laughter] JESSICA: We had gotten off on a tangent somewhere without someone to be like, “Why are we doing this again?” MANDO: Exactly, exactly. Yeah. ANDREA: Well, and I think that that has been a personal challenge of mine as well. I know there was a really flashbulb moment for me. Scott and I have been running our business together for a couple of years. We had gotten on our first podcast and he was telling our origin story and he used the phrase, “Andrea, she's the non-technical founder.” When I heard it, I was like, “How dare you? I have for 2 years been sitting right next to you,” and then he said, “Well, that's the term you use to describe yourself all the time. We had been in a sales meeting right before I recorded that podcast and that's literally the words you use to introduce yourself. So once you start calling yourself technical, I'll follow suit.” JESSICA: Wow. ANDREA: It really made me think and I think some of it is because whenever I go to conferences, I don't look like other people who code especially 12 years ago. I don't talk like the people who are typically stereotypical developers and the first question I would get asked, probably 25 to 40% of the time from people I met were, “Hi! Are you technical, or non-technical?” JESSICA: Really? ANDREA: Yeah. MANDO: Ugh. JESSICA: Huh. ANDREA: And that would be the first thing out of the gate. At the time, I didn't have the kind of mental awareness to go, “I'm at a technical conference. I think you can assume I'm technical.” The fact is I was scared to call myself technical and over the years, I'm just like, “What does that mean to be technical and why do we define people by you are either technical, or you have nothing?” Non-technical, you have zero technical skills, you don't belong. JESSICA: So after you had that conversation with Scott, did you switch to calling yourself technical? Did you change your language? ANDREA: It has been a journey. I became very conscious of not using non-technical. I'll sometimes then say like, “I struggle with syntax and I'm really, really good at these things.” When I phrase things that way, or “I have engineers who are so much better and have much deeper expertise in Docker and Kubernetes than I do. I'm really good at explaining the big picture and why this happens.” So it becomes, I think what we do in software is that because we're so used to thinking in binaries, because that's the way we need to make our code work—true/false, if/else, yes/no—and that pattern naturally extends itself into human relationships, too. Because I know that every single person who asked me that question in no way was trying to be rude, or shut me out. I know that the intention behind it was kind and trying to be inclusive. But from my perspective, when half the people walk up to you and go, “Do you belong here?” Then it's like, “I don't know. Do I belong here?” JESSICA: Yeah. ANDREA: So that's an example of how, if you're at a conference saying, “What brings you here?” That's very open-ended and then it gives everybody the chance to say what brings them here and there's no predefined, “Do you fit in this bucket, or that bucket? Are you part of us, or are you part of them?” JESSICA: It's open to surprise. ANDREA: Mm hm and I think that's something that I am really good at. That's my superpower is let's see the complexity and then let's see the patterns and let's figure out how we can all get good work done together. But you can't see the complexity unless you take a step back. JESSICA: Yeah, and yet Scott noticed that when you are thinking that way, you are thinking like a programmer. Because while software starts by getting us used to thinking in binaries—I should say programming. ANDREA: Yeah. JESSICA: It's just thinking of binaries, as soon as you get up to software and software systems, you have to think in complexity. ANDREA: Yeah. MANDO: And like you were saying, Andrea, I find myself nowadays better recognizing when I'm falling into that trap when I'm not talking about work stuff. When I find myself saying, “Well, it's this, or it's this.” It's like, “Is it really this, or this?” JESSICA: Are these the only options? ANDREA: Yeah. MANDO: Yeah. Do I have to eat Thai food, or pizza tonight, or could I just eat ice cream, or a salad, or…? [laughs] ANDREA: Yeah. MANDO: You know what I mean? It's a silly example, but I don't know, there's something about doing this for a while that I find that kind of this, or that thinking wiring itself into my brain. JESSICA: Yeah. ANDREA: Yeah. Well, and I think that that's normal and that's human. We operate on heuristics. There's the whole neurons that fire together wire together and if you're spending the majority of your time in this thought pattern, adopting something else can be a challenge. So to me, it's like trying to describe how the way I navigate the world in being able to name things well and being able to talk to new people, connect dots, see patterns that I rely on frameworks just as much as I do when I code and trying to figure out what are those things. What are those things? JESSICA: Yeah, because you don't have to import that top level file from the framework in order to use it. So it's not explicit that you're using it. ANDREA: Exactly. Yeah, exactly. So that's been my challenge is that as Scott is like, “Well, help me understand.” I'm like, “I, uh. I don't know. I do this.” That was where I nailed on empathy as really critical and it's been fascinating because when I first started about 5 years writing and talking about empathy in software, the first thing I noticed were all the patterns. I was like, “A really well-written commit message, that's empathy.” That is taking the time to document your rationale so that it's easier for somebody behind you. Refactoring a method so that it's easy to read, deleting the dead code so that it's less burdensome, even logging. Looking at logging in C versus Ruby, it's night and day. JESSICA: Help messages. ANDREA: Yeah. There's a little moment. MANDO: Non-happy path decisions in code. Guardrails. All that stuff. ANDREA: Yeah. So I started thinking in terms of communication artifacts. All of these little things that we're producing are just artifacts of our thinking and you can't produce a communication artifact unless you are considering a perspective. What I noticed, of the perspective, is that a lot of software developers had been trained to take was that of the compiler. I want to make the compiler happy. I want to make the code work. That's a very specific practice of perspective taking that is useful if you're imagining okay, we don't have to get rid of that and we need to add the recognition that the perspectives taking needs to go the compiler into who will be interacting with what you're creating and that is on both the other side of the UI, if there is one, or working on the code that you've written maybe six months from now and that can be your future self. And then also, who will be impacted by the work that you create, because not everybody who is impacted by the decisions that you make will be directly interacting with and when I'm writing content, or that is the framework is getting to know the audiences really well, doing good qualitative research. So that's kind of the difference between the open-ended versus closed-ended questions. Then being able to perspective change and then along the way, there are little communication hacks, but just thinking about every single thing that you produce—and no, I have not come across a communication artifact, or a thing that is produced while coding that is not somehow rooted in empathy. JESSICA: Because it's communication and you can't communicate – [overtalk] ANDREA: It's all communication. JESSICA: At all without knowing what is going to be received and how that will be interpreted. ANDREA: Yeah. Similar to test-driven development, where we're framing things in terms of unit tests and just thinking about the test before we write the code. In the same way, we're thinking about the perspective of other people—we can still think of the compiler—and anchoring our decisions on how it will impact other people. JESSICA: It's making the compiler happy. That's just table stakes. That's absolute minimum. ANDREA: Yeah. Well, it's been fascinating because this part of this project. So I'm writing a book now, which is super exciting and by far, the hardest thing I've ever done. But one of the things that, because I'm curious, I'm like, “Why? How did we get here? How did we get here where, by all objective measures, I should have been able to go into computer science without a problem and feel like –?” JESSICA: Think of yourself as technical without a problem. ANDREA: Yeah. Why do I still struggle and why did we extract empathy out of this? So looking at the history of it has been fascinating because as the computer science industry grew, there was a moment in the mid-60s. There was a test, like a survey, that went out to just under 1,400 people called the Canon Perry vocational test for computer programmers. It was vocational satisfaction, I think. But it was measuring the satisfaction of programmers and they were trying assess what does a satisfied programmer look like. There were many, many problems with the methodology of this, including the people who they didn't define who a programmer was, the people self-defined. So it's like, if you felt like you were programmer, then you were a programmer, but there was no objective. Like, this is what a programmer is prior to selecting the audience, the survey respondents and then when they evaluated the results, they only used professional men. They didn't include any professional women in their comparison study. So the women in the study, there are illustrations and the women are not presented as professionals, they are presented as sex objects in a research paper. The scientific programmers, they're the ones who get the girl and she's all swooning. The business programmers are very clearly stated as less than and they're shy. The girl is like, “I don't want you.” JESSICA: That have like comics, or something? ANDREA: It was comics, yeah. They had like comic illustrations in there. Okay, it's a survey, what's the big deal? Well, from 1955 through the mid-90s, there was an aptitude test from IBM called the Programmer Aptitude Test, the PAT. In there, Walter McNamara from IBM, who created it, went out, had empathy, and was like, “Okay, let's talk to our customers, what does a good programmer look like,” and determined that logical reasoning was the number one attribute. Okay, sounds good. But then he said, “Well, if logical reasoning is the most important attitude, then we need to create a timed 1-hour math test.” What's interesting to me is that in that, there is a logical fallacy in and of itself, called a non-sequitur, [chuckles] where it's like all humans are mammals, bingo a mammal. Therefore, bingo is a human. That's an example of a non-sequitur. That's what happened where it was determined logical reasoning is important to computer science and programming. All mathematics is logical reasoning. Therefore, mathematics is the only way to measure the capability that somebody has for logical reasoning. That, saying, “Okay, we don't care about communication skills. We don't care about empathy. We don't care about any of that. Just are you good at math?” And then the PAT's study—I've been diving into the bowels of the ACM and looking at primary resource documents for the past several months—and there was an internal memo where Charles McNamara referred to the Canon Perry study in 1967 and said, “The PAT was given to 700,000 people last year and next year, we should incorporate these findings into the PAT,” and the PAT became the de facto way to get into computer science. So these are decisions that were made long before me and so, what you end up getting then – and then also in 1968, there was what's called, there was a NATO conference on software engineering and they said, “We really need to bring rigor into computer science. We need to make this very rigorous.” Again, there were no men at this conference. It was about standards and Grace Hopper wasn't even invited, even though she was like – [overtalk] JESSICA: There were no women in the conference. ANDREA: There were no women. JESSICA: No non-men. ANDREA: No non-men, yes. So you start to see stereotypes getting built and one of the stereotypes became, if you look like this and you are good at math, then you are good at programming. I'm very good at logical reasoning, but I struggle to do a time capsule. I have ADHD and that is something that's very, very, very challenging for me. So that coupled with and then you get advertising where it's marketed, too. MANDO: Yeah. ANDREA: So we need to undo all of this. We can recognize, okay, we can refactor all of this, but it takes recognizing the complexity and how did it all come to be and then changing it one thing at a time. CASEY: A lot of what you've just been talking about makes me think about Dungeons and Dragons and Skyrim for a little nerdy segue. ANDREA: Yeah. CASEY: You have skill trees. You could be a really, really good warrior, very good at math, very good at wielding your sword, and then if you measure how good you are at combat by how big your fireball spell can be, how many you can shoot, how accurate you are, you're missing that whole skill tree of ability, of power that you have. ANDREA: Yeah. MANDO: What I find so fascinating is when I was going through the computer science program that I never finished and this was like a million years ago. When I was in college, there was a very specific logical reasoning class that you had to take as part of the CS program at UT. But it wasn't a math class, it was a philosophy class and I think that's pretty common that logistics studies fall under schools of philosophy, not the schools of mathematics. So it was really interesting to me that these dudes just completely missed the mark, right? [laughs] ANDREA: It is the definition of irony and not Alanis Morrissette kind of way, right? [chuckles] I think that's the thing it's like – and this isn't to say the Walter McNamara was a bad person like, we all make mistakes. But to me, again, this is about impact and if one, or two people can have the ability to create a test that impacts millions of people across generations to help them feel whether, or not they belong in even contributing to building software. Because I always felt like I was a user of software—I was always a superuser—but for some reason, I felt like the other side of the interface, the command line, it was like Oz. It was like that's where the wizards live and I'm not allowed there. It's like, how do we just tear down that curtain and say, “Y'all, there is no – no, this was all built on like false assumptions”? How do we have a retrospective and say, “When we can look at a variety of different perspectives, then we get such stronger products.” We get such stronger code. We minimize technical debt in addition to hopefully, staving off biases that get built into the software. I think it's very similar of human systems, very similar to software systems. It's like, how can we roll back? If we make a mistake and it impacts human systems, how can we fix that as fast as possible, rather than just letting things persist? JESSICA: When you're talking about who can be a good software developer, when you're talking about who is technical, who is valuable, you don't want rigor in that! ANDREA: Right!
 JESSICA: That's not appropriate. ANDREA: Yeah. JESSICA: You want open questions. ANDREA: Yeah, and that is exactly what happened, was people conflate rigor and data with accuracy. There's a bias towards if it's got numbers behind it, it must be real, but you can manipulate data just as much as you can manipulate other things. So the PAT then said, “Okay, well, if you can't pass the PAT, then we'll create all of these other types of tests, so you could be a console operator, or you could be a data analyst.” What's fascinating is when you go back, the thing that was at the very bottom of the Cannon Perry survey, in terms of valuable development activities, was software maintenance. JESSICA: And that's everything now. ANDREA: Yeah!
 JESSICA: Back then, they didn't have a lot of software. MANDO: Yeah. JESSICA: They didn't have open source libraries. If they needed something, they wrote it. ANDREA: But the stereotypes persist. JESSICA: Yeah. MANDO: 100%. ANDREA: The first evidence I found, again, was in 1967. There was a study of 12 people, all of whom were trainees at a company, which that would be a wild – they hadn't even – [overtalk] JESSICA: So this is like even less than interviewing your grad students. ANDREA: Well, yeah. JESSICA: Or your undergrads for your graduate research paper, yes. ANDREA: They measured how quickly someone could solve a problem and they ranked them, and then they made the claim that you can save 25 times—this is the first myth of the 25x developer. Well, it got published in the ACM and then IBM picked it up and then McKinsey picked it up, and then it's just, you get the myth of the full-stack unicorn who's going to come in and save everything! What's interesting is all of these things go back and I think they were formed out of good intention in terms of understanding our world and we understand now, exactly like you said, Jess. That's not the right way to go about it because then people who are really needed on software teams don't feel like they belong and it's like, “Well, do you belong?” JESSICA: That's an outsized impact for such a tiny study. ANDREA: Yeah. So that gets me thinking, what kinds of things am I doing that might have an outside impact? JESSICA: And can we make that impact positive? ANDREA: Yeah, and when we find out that it wasn't, can we learn from our mistakes? I think one of the things, too, is taking the idea of as people are coding. It's like, “Well, who's actually going to read this?” That's something I hear a lot. I used to feel that way about all tags. I'm like, “Who actually reads all tags?” But then my friend, Taylor, was in a car accident and lost his vision. and he was like, “I absolutely need all tags,” and I'll tell you, that changed everything for me. Because it went from this abstract, “I have to check this box. I have to type something in, and describe this photo” to “I care about my friend Taylor and how can I make this experience as best for him as possible?” That is empathy because in order to have empathy, you have to connect with a single individual. Empathy is – and actually, when you do form empathy for a group, you get polarization. So empathy cuts both ways. It can be both very positive, but also very – [overtalk] CASEY: [inaudible] on the individual goes a long way. So for our discussion here, I can share an individual I've been talking to about this kind of problem. I have a friend who's a woman trying to get her first software developer role and she has to study how to hack the coding interview for a lot of the places where she wants to work, which is literally studying algorithms that you probably won't use in the job. I had an interview a few years ago that was the Google style algorithms interview for a frontend role. Frontend developers don't write algorithms, generally. Not unless you're working on the core of the framework maybe. It was completely irrelevant. I rejected them. I think they rejected me back, too probably. [laughter] But I wouldn't work there because of the hiring process. But my friend, who is a woman in tech trying to get in, doesn't have that kind of leeway to project. She wants to get her first job whoever it is – [overtalk] MANDO: She wants a job, yeah. CASEY: That is willing to use the bias system like that and to hack that system to study it specifically how to get around it, which isn't really helping anyone. ANDREA: Yeah. CASEY: So how can we help reform the system so she doesn't have to do that kind of thing and so, people like her don't have to, to get into tech? I don't know, my boycotting that one company is a very small impact; how do we get a company's hiring practices to change is a hard problem. ANDREA: It is a very hard problem. I can share what we are doing in Corgibytes to try to make a difference. I think the first thing is that in our hiring process, we have core values mapped to them and these are offshoots of our main core values, one of which is communication is just as important as code. So we have that every single applicant will get a response and that seems so like, duh, but the number of people who are here who are just ghosted, submit an application and it goes out into the ether. That is, in my opinion, disrespectful. We have an asynchronous screening interview, so it's an application and it's take your time, fill it out, and it's questions like, “What's an article you found interesting and why?” and “What do you love about modernizing legacy code?” Some people need that time to think and just to formulate an answer and so, taking some of that pressure off, and then at the end of our – we have all of our questions mapped to our core values. I'm still trying to figure out how we can get away from more the dreaded technical interviews, but we don't use the whiteboard, but we also have a core value of anything that someone does for us, in terms of whether they show up for an interview, they will walk away with just as much benefit. They will have an artifact of learning something, or spec work is I think, immoral to some of these core things. So we use Exercism for us, so Katrina Owens, as a way of like, “Okay, show us a language that you're like really familiar with.” And then because with what we do, you just get tossed into if it's like, “Okay, let's pick Scala.” It's like you've never tried functional programming before, but then just, it's more of seeing the mindset. Because I think it's challenging because we tried getting rid of them all together and we did have some challenges when it came to then client upper-level goals and doing the job. So it's a balance, I think and then at the end of our interviews doing retrospectives telling the candidate, “Here's what you did really well in this interview, here's where it didn't quite land for me,” because I think interviewing is hard and like you said, Casey, especially now post-COVID, I think more and more people have the power to leave jobs. So I think the power, especially in software development, for people who have had at least their first position, they have a lot more power to walk out the door than they did before. So as an employer and as somebody who's creating these, that's what I'm doing and then if we get feedback and the whole idea with empathy is you're never going to be able to be perfect. Because you don't have the data for the perspective of every single person, but being open and listening and when you do make mistakes, owning up to them, and fixing them as fast as possible. If we all did that, we can make a lot of progress on a lot of fronts really fast. CASEY: I'm so glad your company has those good hiring practices. You're really thinking about it, how to do it in a supportive, ethical, and equitable way. I wonder, we probably don't have the answer here today, but how can we get more companies to do that? I think you sharing here might help several companies, if their leadership are listening. and that's awesome. Spreading the message, talking about it more—that's one thing. Glad we're doing that. MANDO: Yeah. The place that I work at, we're about to start interviewing some folks and I really like the idea of having a retrospective with the candidate after maybe a couple of days, or whenever after the interview and taking the time, taking the 30 minutes or whatever, to sit down and say, “If I'm going to take time to reach out to them anyway and say, ‘You're moving on to the next round,' or ‘We have an offer for you, or not,' then I should be willing to sit down with them and explain why.'” ANDREA: Well, I think the benefit goes both ways, actually. We do it right in our interviews. So we actually say the last 15 minutes, we're going to set aside on perspectives. MANDO: Oh wow, okay. ANDREA: So we do and that's something that we prep for ahead of time. We get feedback of what went well [chuckles] and what we can do better and what we can change. MANDO: Yeah. ANDREA: Because otherwise, as an employer, it's like, I have no idea. I'm just kind of going off into the ether, but then I can hear from other people's perspectives and it's like, okay and then we can change things. But that's an example of, we think of employer versus employee and it's like that's another dichotomy. It's like no, we're all trying to get good work done. JESSICA: Andrea, how do you do performance reviews? ANDREA: We're still trying to crack that, but there's definitely a lot of positive psychology involved and what we are trying to foster is the idea of continuous performance, or continuous feedback is what we call it. So we definitely don't do any kind of forced ranking and that's a branch of things that have contributed to challenges. We have one-on-ones, we check in with people, but a lot of it, I think is asking people what they want to be doing, genuinely. As a small company, we're like 25 people. I think it's easier in a small company, but part of it is – and we were constantly doing this with ourselves, too. My business partner was like, “I really want to try to be the CEO. I've always wanted to be the CEO.” So I stepped back actually during COVID. We focus on being a really responsive team and so, then that way, it's less about the roles. It's less about rigidity. There's a really great book in terms of operations called Brave New Work by Aaron Dignan. It has a lot of operational principles around this. Team of Teams is another really good one. But just thinking through like, what's the work that needs to be done, how can we organize around it, and then thinking of it in terms of more of responsibilities instead of roles. JESSICA: I want to think of it as a relationship. It's like, I'm not judging you as a developer, instead we're evaluating the relationship of you in this position, in this role at this company. ANDREA: Yeah. JESSICA: How is that serving the company? How is that serving you? ANDREA: Yes, and I think that's a big piece of it is – and also, recognizing the context is really important and trying to be as flexible as possible, but then also recognizing constraints. So there have been times where it's like, “This isn't working,” but trying to use radical candor as much as you can, that's something we've been working on. But trying to give feedback as early and as often as possible and making that a cultural norm as to the, “Oh, I get the 360 feedback at the end, twice a year,” like that. JESSICA: Yeah, I'm sorry, if you can't tell me anything within two weeks, don't bother. ANDREA: Yeah. But one example is like we've fostered this and as a leader, I want people who are going to tell me where I'm stepping in it and where I'm messing up. So I kind of use – [overtalk] JESSICA: Yeah, at least that retrospective at the end of the interview says that. ANDREA: Mm hm, but even with my staff, it's like – [overtalk] JESSICA: [inaudible] be able to say, “Hey, you didn't send me a Google Calendar invite,” and they'd be like, “Oh my gosh, we should totally be doing that.” Did anybody tell them that? No! ANDREA: Yeah, totally. So I don't claim to have the answers, but these are just little experiments that we're trying and I think we really lean on the idea of continuous improvement and marginal gains. Arthur Ash had a really great quote, “Start where you are. Use what you have. Do what you can.” I think that's the thing, the whole point of the empathy during development framework is that if you're a developer working on the backend writing a nice commit message, or giving quality feedback on a pull request, instead of just a “Thumbs up, looks good to me.” That's a small act of empathy that you can start doing right away. You don't need to run it by anybody, really, hopefully. If you do, that's a problem [chuckles] your manager and we've seen that. But there are small ways that you can be empowered and leaning into those small moments, doing it again and again, and then creating opportunities to listen. Because empathy, I think the other thing is that people tend to think that it's a psychic ability. You're either data, or your Deanna Troi. CASEY: Jamil Zaki, right? ANDREA: Yeah, the Roddenberry effect. Jamil Zaki, out in Stanford, coined that. I think that's the thing; I've always been told I'm an empath, but I don't think it's telepathy. I think it's just I've gotten really good at spotting patterns and facial recognitions as opposed to Sky. He can just glance and go, “Oh, you're missing a semicolon here.” That is the same skill, it's just in a different context. CASEY: I love that parallel. JESSICA: Yeah. CASEY: Recognizing small things in facial expressions is like noticing missing semicolons. M: Mm hm. [laughs] CASEY: That's so powerful. That's so vivid for me. MANDO: Yeah. Going back, that made what something that you said earlier, Andrea really click for me, which is that so many people who are professional software developers have this very well-developed sense of empathy for the compiler. [laughs] ANDREA: Yeah. MANDO: Right, so it's not that they're not empathetic. ANDREA: Yes! MANDO: They have learned over their career to be extremely empathetic, it's just for their computer. In the same way, you can learn to be empathetic towards your other teams, towards your DevOps group, towards the salespeople, towards anybody. ANDREA: The flip side of your non-technical is you're not good with people because Scott got this all the time. He's like, “You're good with machines, but you're not good with people.” When he told me that, I was like, “I've known you since we were 11, you're incredibly kind. I don't understand.” So in some ways, my early journey here, I didn't come with all the baggage and so, there is this, like, this industry is weird. [laughs] How can we unpack some of this stuff? Because I don't know, this feels a little odd. That's an example and I think it's exactly that it's cultural conditioning and it's from this, “You're good with math, but we don't want you to be good with people.” If you're good with people, that's actually a liability. That was one of the things that came out of the testing of the 60s, 70s, 80s, and early 90s. MANDO: I can't wait till this book of yours comes out because I'm so curious to read the basis of all these myths that we have unconsciously been perpetuating for years and I don't know why, but there is this myth, there are these myths. Like, if you're technical, you're not good with people and you're not – you know what I mean? It's like, I can't wait to read it. ANDREA: You can go to empathyintech.com. You can sign up for the newsletter and we don't email very often. But Casey actually helps me run a Discord channel, too, or Discord server. So there's folks where we're having these conversations and it doesn't matter what your role is at all. MANDO: Yeah. ANDREA: Just let's start talking to each other. JESSICA: Andrea, that's beautiful. Thank you. That makes this a great time to move to reflections. At the end of each episode, we each get to do a reflection of something that stood out to us and you get to go last. ANDREA: Awesome. MANDO: I can go first. I've got one. The idea that empathy is being able to view and identify other perspectives is one that is something that I'm going to take away from this episode. I spent a lot of my career as a software developer and spent another good chunk of my career as someone who worked in operations and DevOps and admin kind of stuff. There's this historic and perpetual tug of war between the two and a lot of my career as a systems administrator was spent sitting down and trying to explain to software engineers why they couldn't do this, or why this GraphQL query was causing the database to explode for 4 hours every night and we couldn't live like that anymore. Stuff like that. To my shame, often, I would default to [laughs] this idea that these software engineers are just idiots and that wasn't the case at all. Well, probably [laughs] not the case at all. Almost always it wasn't the case at all. Anyway, but the truth of the situation is probably much closer to the idea that their perspective was tied specifically to the compiler and to the feature that they're trying to implement for their product manager, for customer X, or whatever. And they didn't have either the resources, or the experience, or the expertise, or whatever that was required to add on the perspective of the backend systems that they were interacting with. So maybe in the future, a better way to address these kinds of situations would be to talk about things in terms of perspective and not idiocy, I guess, is the… ANDREA: Yeah, a really powerful question there is what's your biggest pain point and how can I help you alleviate it? It's a really great way to learn what somebody's perspective is to get on the same page. MANDO: Yeah, like a lot. JESSICA: Nice. I noticed the part about how a lot of the help happens when you have empathy for the individuals who aren't on a happy path, who aren't the great majority of the people using the software, or the requests that come through your software. It's like that parable, there's a hundred sheep and one of them goes astray and the shepherd is going to leave the ninety-nine—who are fine, they're on the happy path, they're good—and go help the one. Because some other day, it's going to be another sheep that's off the happy path and that one's going to need help and that's about it. MANDO: Yeah. Today you, tomorrow me, right? That's how all this works. CASEY: The thing I'd been picking up is about feedback. Like, the best way to develop empathy for someone else is to get feedback, to get their perspective somehow. I've done retros at the ends of meetings, all the meetings at work I ever do. I even do them at the end of a Pomodoro session. A 25-minute timer in the middle of a pairing day, I'll do them every Pomodoro. “Anything to check in on? No? Good. Okay.” As long as we do. But I've never thought to do it during the interview process. That is surprising to me. MANDO: Yeah. CASEY: I don't know if I can get away with it everywhere. The government might not like it if I did that to their formal process. [laughter] Maybe I can get away with, but it's something I'll think about trying. I would like feedback and they would like feedback—win-win. MANDO: Yeah, I've never done it either and it makes perfect sense. I have a portion, unfortunately, in my interviews where I say right at the beginning, “This is what's going to happen in the interview,” and I spend 5 minutes going through and explaining, we're going to talk about this, we're going to talk about that, or just normal signposting for the interview. It never once has occurred to me to at the end, say, “Okay, this is what we did. Why don't you give me some feedback on that and I give you some feedback about you?” That makes sense. ANDREA: Awesome. For me, I have been wanting to come on your show for a really long time. I was telling Casey. [chuckles] JESSICA: Ah! ANDREA: I was like, “I love the mission of expanding the idea of what coding is.” So I just feel very honored because for the longest time, I was like, “I wonder if I'm going to be cool enough one day to –” [laughs] JESSICA: Ah! We should have invited you a long time ago. ANDREA: Yeah. So there's a little bit of fangirling going on and I really appreciate the opportunity to just dive a little bit deep, reflect, and think. As somebody who doesn't mold, it's nice to get validation sometimes that the way I'm thinking is valuable to some people. So it gives me motivation to keep going. JESSICA: Yeah. It's nice when you spend a lot of energy, trying to care about what other people care about, to know that other people also care about this thing that you care about. ANDREA: Yeah. JESSICA: Thank you so much for joining us. ANDREA: Thank you for having me! MANDO: Thank you. ANDREA: The fastest way to reach out to me and make sure that I see it is actually to go to corgibytes.com. Corgi like the dog, bytes, B-Y-T-E-S, .com and send an email on the webform because then that way, it'll get pushed up to me. But I struggle with email a lot right now and I'm on Twitter sporadically and I'm also on – MANDO: That's good. The best way to do that. ANDREA: I am a longform writer. I'm actually really excited that I have a 100,000 words to explain myself. I do not operate well in the 140-character kind of world, but I'm on there and also, on LinkedIn. And then the book website is empathyintech.com and there's a link to the Discord channel and some deeper articles that I've written about exactly what empathy in tech is and what empathy driven development is. I'm writing it with my friend, Carmen Shirkey Collins, who is another copywriter who is now in tech over at Cisco, and it's been a joy to be on a journey with her because she's super smart and has great background in perspective, too. JESSICA: And if you want to work on meaningful, impactful legacy code in ensembles, check out Corgibytes. ANDREA: Yeah. JESSICA: And if you want to talk to all of us, you can join our Greater Than Code Slack by donating anything at all to our Greater Than Code Patreon at patreon.com/greaterthancode. Thank you, everyone and see you next time! Special Guest: Andrea Goulet.

英语每日一听 | 每天少于5分钟
第1185期:The Love Story

英语每日一听 | 每天少于5分钟

Play Episode Listen Later Apr 14, 2021 2:01


JJ: Look at them all lean in as I tell this story. It starts out sickeningly sweet. I was in a musical, Cinderella. I was Cinderella and the guy who played the prince and I started to date.We got pretty serious. He was trying to get rid of an ex who kept bothering him and so he decided to come to Japan to teach English. All during the summer we had plans you know, I would come and visit and that kind of stuff.We were really excited about it and he was a model at the agency. At the same agency where I was an actor and... so we had the same agent. He went to Japan and was teaching and we were writingback and forth, "looking forward to seeing you" all that kind of stuff.I was having lunch with my agent one day and telling her that I had started taking Japanese and I had been planning out my trip. I was very excited about this whole thing and she says, "JJ, I don't know how to tell you this."I'm thinking,"Oh, my God! What?"And she says, "Yeah, Richard's ex-girlfriend flew out to Japan and they got married."Jessica: Oh, my God!JJ: Married!Jessica: Oh, no!JJ: Yeah! Yeah!Jessica: How did you feel?JJ: Like I needed a ladder to get on a piece of paper. Really, I mean it was a devastating. You know that first broken-love kind of thing, but..Jessica: Did you hear from him afterwards?JJ: Yeah, we were always just friends apparently. Yeah, so not only adding the "insult to the indus..". What I meant to say "insult to injury" was him just saying that we were always just friends.

英语每日一听 | 每天少于5分钟
第1185期:The Love Story

英语每日一听 | 每天少于5分钟

Play Episode Listen Later Apr 14, 2021 2:01


JJ: Look at them all lean in as I tell this story. It starts out sickeningly sweet. I was in a musical, Cinderella. I was Cinderella and the guy who played the prince and I started to date.We got pretty serious. He was trying to get rid of an ex who kept bothering him and so he decided to come to Japan to teach English. All during the summer we had plans you know, I would come and visit and that kind of stuff.We were really excited about it and he was a model at the agency. At the same agency where I was an actor and... so we had the same agent. He went to Japan and was teaching and we were writingback and forth, "looking forward to seeing you" all that kind of stuff.I was having lunch with my agent one day and telling her that I had started taking Japanese and I had been planning out my trip. I was very excited about this whole thing and she says, "JJ, I don't know how to tell you this."I'm thinking,"Oh, my God! What?"And she says, "Yeah, Richard's ex-girlfriend flew out to Japan and they got married."Jessica: Oh, my God!JJ: Married!Jessica: Oh, no!JJ: Yeah! Yeah!Jessica: How did you feel?JJ: Like I needed a ladder to get on a piece of paper. Really, I mean it was a devastating. You know that first broken-love kind of thing, but..Jessica: Did you hear from him afterwards?JJ: Yeah, we were always just friends apparently. Yeah, so not only adding the "insult to the indus..". What I meant to say "insult to injury" was him just saying that we were always just friends.

英语每日一听 | 每天少于5分钟
第1185期:The Love Story

英语每日一听 | 每天少于5分钟

Play Episode Listen Later Apr 14, 2021 2:01


JJ: Look at them all lean in as I tell this story. It starts out sickeningly sweet. I was in a musical, Cinderella. I was Cinderella and the guy who played the prince and I started to date.We got pretty serious. He was trying to get rid of an ex who kept bothering him and so he decided to come to Japan to teach English. All during the summer we had plans you know, I would come and visit and that kind of stuff.We were really excited about it and he was a model at the agency. At the same agency where I was an actor and... so we had the same agent. He went to Japan and was teaching and we were writingback and forth, "looking forward to seeing you" all that kind of stuff.I was having lunch with my agent one day and telling her that I had started taking Japanese and I had been planning out my trip. I was very excited about this whole thing and she says, "JJ, I don't know how to tell you this."I'm thinking,"Oh, my God! What?"And she says, "Yeah, Richard's ex-girlfriend flew out to Japan and they got married."Jessica: Oh, my God!JJ: Married!Jessica: Oh, no!JJ: Yeah! Yeah!Jessica: How did you feel?JJ: Like I needed a ladder to get on a piece of paper. Really, I mean it was a devastating. You know that first broken-love kind of thing, but..Jessica: Did you hear from him afterwards?JJ: Yeah, we were always just friends apparently. Yeah, so not only adding the "insult to the indus..". What I meant to say "insult to injury" was him just saying that we were always just friends.

Tough Girl Podcast
Jessica “Dixie” Mills - Thru-Hiker & Vlogger walking 500 miles on the Camino de Santiago (the French Way)!

Tough Girl Podcast

Play Episode Listen Later Jul 2, 2020 46:53


We have been following Jessica (Trail name - Dixie) since 2016 when we first spoke with her about her thru hike of the Appalachian Trial, we then caught up with Jessica in Feb 2019, when she shared more about hiking the Pacific Crest Trail and the Continental Divide Trail.    During this episode, Jessica shares more about her most recent challenge - walking 500 miles on the Camino de Santiago, which is also known as the French Way. The journey begins at Saint Jean Pied de Port, in France, and goes through four of Spain's 15 regions, ending at the Cathedral of Santiago de Compostela.   Jessica shares more about her experiences of this walk, what she wanted to learn and what made it such a special journey. She also shares more about future challenges, and provides top tips and advice for your next hike!   You can listen to Jessica/Dixie on the Tough Girl Podcast and watch her vlogs on the Homemade Wanderlust Channel.   Show notes Who is Jessica How she got into hiking Her passion for hiking  Wanting to travel abroad to hike Thinking about the Camino Hiking with her sister - Montana Getting her first passport at 30 Planning to head over to Europe Preparation for the trip Not wanting to over research Not booking a return flight The Wine Fountain! Taking the time to think The culture shock of Paris Getting homesick Ketchup!! Comparing thru hikes in America to the Camino Hiking Vs a pilgrimage Appreciating home more Stepping outside her comfort zone Heading over to New Zealand in October… Homemade Wanderlust Youtube Channel Reaching Santiago! Heading to “the end of the world!” Heading off to Italy after the walk Quick Fire Questions Final words of advice    Social Media   Website - https://homemadewanderlust.com    Facebook @homemadewanderlust   Instagram @homemadewanderlust   Youtube - Homemade Wanderlust

The Scott Alan Turner Show | FINANCIAL ROCK STAR
How The Rich Got Rich (Eat The Rich)

The Scott Alan Turner Show | FINANCIAL ROCK STAR

Play Episode Listen Later Feb 12, 2020 40:13


Seven traits among people who had successfully built wealth. Really four, because we ran out of time. - Should paying off debt come before putting money in a 401(k)(Olivia) - How can I make up 20% of our income to stay home with our kids (Kaya, Mississippi) - I'm struggling with budgeting, want to learn more about investing, as well as financial wellness (Jessica) - How do people achieve financial independence early(Instagram) - What are people doing with their extra gas money? Mentioned on the show: The financial planning survey: https://measure.datapoints.com/survey/e/p1mNU3aZBowmFC8XP77W  

rich kaya jessica how
Rock The Podcast
Feedback On Pitches and Relationships With Guests

Rock The Podcast

Play Episode Listen Later Apr 5, 2017 24:05


What do podcast hosts think of your pitch to be a guest on their show? In today’s episode, Margy and Jessica are joined by Interview Connection’s client Damion Lupo. Damion shares his essential feedback about how podcast hosts perceive the unique introduction he receives from Interview Connections bookers. And later, Adam Hommey of the Business Creators’ Radio Show gives his tips for exploiting the brilliance and passion of guests on his podcast.   Missed Connections This week’s missed connection is more of a missed synapse! Jessica and Aaron Walker were outside just before speaking on John Lee Dumas’ panel, at this year’s Social Media Marketing World and Aaron asked Jessica “How is Interview Valet going?”   Damion Lupo Client Feedback Damion says many hosts are impressed on how they were contacted by the Interview Connection’s team. They are engaging with the podcast hosts, and it shows they are paying attention. It’s unique, and it completely changes the dynamic. It also adds third-party validation. There is value in having someone else introduce you. Embrace feedback even if it’s bad, because it is an opportunity to learn. — Damion Lupo Damion also gives Jessica some advice on how to deliver her book, to make it rise above the rest. Listen to Why Entrepreneurs are Investing in Podcast Interviews with Damion Lupo   Adam Hommey Adam talks about relationship building, and how his intake process helps to shine a light on the guest’s brilliance and passion.   Help! How Do I Make My Podcast Guest Shine? ● Have the podcast guest supply interview questions. ● Connect with the guest on social media before the interview. ● Ask the guest for pronunciation of their name. ● Have the podcast guest fill out an intake form.   Help! I Want to Shine as a Podcast Guest ● Have your One Sheet ready, and get it to the host asap. ● Have all of your information in one place.   Resources Mentioned: Interview Connections Interview Connections TV Headspace App Social Media Marketing World John Lee Dumas Screw the Nine to Five Interview Valet Damion Lupo Business Creators' Radio Show

Inspire Nation Show with Michael Sandler
HOW TO BREAK THRU BARRIERS & EXPAND YOUR POSSIBILITIES! Jessica Lee | Inspirational | Motivational | Self-Help | Inspire

Inspire Nation Show with Michael Sandler

Play Episode Listen Later Aug 25, 2016 57:54


If you've ever wished you could be more, do more, dream bigger and succeed, then do we have the expansive possibilities show for you.  Today I'll be talking with Jessica Lee, my super-loving wife, and call-no-punches, fork in the side always challenging me, partner about expanding what you think is possible, and believing in yourself.  That plus we'll talk about shows from nowhere, why what you resist, persists…and why going to the east-coast, when you're living in Hawaii, just may be the greatest gift in the world. Empowering Self-Improvement and Self-Help Topics Include: What the law of attraction has to do with expanding your possibilities What it means to be pro-active without trying to be pushy What it means to expand your possibilities What Jessica's learned from an energy healing guest, Richard Gordon, Quantum Touch What we can learn from Andrew Holecek and dream yoga and lucid dreaming How you can fly in your dreams What Dr. Joe Dispenza has discovered in his retreats and on brain scan How to expand your consciousness How to make steps little by little How a strong desire can help you feed the meter through the law of attraction How meditation can help What was a cool visualization that came to Jessica How we can improve our eyesight from Meir Schneider What we can learn from Carlos Santana in the documentary 5 Keys to Mastery How we may need to move past fear How to rewire for possibilities Why Howard Martin's Heart-Coherence exercise has been so important Jessica Lee & Michael Sandler Share How to Expand Possibilities, Blast Thru Plateaus & Achieve Personal Success! Inspiration | Motivation | Spiritual | Spirituality | Meditation | Career | Fitness | Self-Improvement | Health | Self-Help | Inspire For More Info visit: www.InspireNationShow.com 

This Week in Travel
#76 - Andrew Evens, Jessica Spiegel - "It's Oprah's World"

This Week in Travel

Play Episode Listen Later Mar 7, 2011 61:03


This week's guests are Andrew Evans of National Geographic and Jessica Spiegel from Boots N' All.This week's news:    * Overheard locker tot outrage    * Thai mystery hotel death toll jumps to four    * Thais doubt seaweed killed Sarah Carter    * Shipping vs. Checking: Which would you rather do?    * Canadian Tourist Arrested For Giving Nazi Salute Outside Reichstag    * Gunman Flees Las Vegas Casino with $32,000 in Chips    * Egypt lures tourists with discounts, history in the making...and Oprah?    * Is Michelangelo's Statue of David Threatened by New High-Speed Train?Picks of the week    * Gary - The Island of Lanai    * Chris - Cinq.tunaverse.com    * Jen - Gasbuddy.com    * Andrew - Buy your beads online for Mardi Gras    * Jessica - How to travel around the world on $40/day