Podcast appearances and mentions of jen dary

Welcome back to The Businessology Show! Leadership coach and entrepreneur Jen Dary joins Jason to dive into the unique challenges and needs of entrepreneurs with ADHD. Exploring how structure, delegation, and direct communication can make a significant difference, Jen shares her expertise in coaching professionals with ADHD, discussing the balance between self-regulation and external support, especially in remote work environments. Jen also highlights the importance of building trust within teams and strategically managing personal well-being to prevent burnout. This insightful conversation offers practical advice for creating more inclusive and supportive professional settings. Whether you're an entrepreneur, manager, or someone navigating the complexities of ADHD, this episode is packed with valuable takeaways to enhance your leadership approach!

Becoming a manager for the first time comes with many common challenges: balancing your time, managing team conflicts, and delegating work to direct reports. But leadership coach Jen Dary says there are also subtler challenges—like learning to actually see yourself as a leader. Assuming responsibility for other people's professional development and personal happiness does change you. And the feelings can be mixed until you're able to build your identity and confidence back up. In this episode, Dary discusses how you can explore your new identity as a manager. You'll learn how to plan your own professional development, deal with disillusionment, and set priorities and boundaries with your team—all while juggling the responsibilities of your new role. This is the first episode in a special series highlighting the four best leadership episodes of 2023, curated from across Harvard Business Review's podcasts. Key episode topics include: leadership, gender, leadership development, managing people, early career. HBR On Leadership curates the best case studies and conversations with the world's top business and management experts, to help you unlock the best in those around you. New episodes every week. · Listen to the original Women at Work episode: How to Manage: Finding Yourself Again (2023)· Find more episodes of Women at Work.· Discover 100 years of Harvard Business Review articles, case studies, podcasts, and more at HBR.org.]]>

What if the challenges you encounter in life were the stepping stones to your greatest personal and professional triumphs? That's precisely the inspiring reality of our remarkable guest, Jen Dary, the guiding light behind Plucky. As a leadership coach to professionals from the world's leading companies, including Google and the New York Times, Jen's insights into the work culture, remote work, and relationship-building in a remote environment are unparalleled.The conversation takes a heartfelt turn as we delve into the personal side of our formidable guest. Jen graciously invites us into her world, shedding light on her journey as a parent entrepreneur and how she strikes a balance amidst the changing dynamics of work, especially in the wake of the pandemic. As a brain tumor survivor, her perspective on mental health is deeply enlightening. And then, we segue into a vital aspect of professional growth - mentorship. From making a strong first impression to approaching the mentorship relationship, Jen's wealth of knowledge is sure to leave you inspired and equipped for success. So, gear up for an episode that promises to challenge your notions of leadership, mentorship, and overcoming adversities.Connect with Jen Dary:More at beplucky.com https://linktr.ee/bepluckster  IG: @bepluckster  @jenniferdary @beplucky on socialsLooking for a wonderful Holiday Gift Giving Idea? Consider WordHaven BookHouse Book Boxes and Book Clubs (Banned Book Club and the Treehouse Book Club). Both contain a curated book that can be picked up locally or shipped to anywhere in the United States. WordHaven offers 1, 3, 6, or 12-month subscriptions to fit any size budget. Learn more on their website = https://www.kellydholstine.com/wordhaven-bookclubs Make 2024 the year your business SHINES! How does one make this happen? By partnering with the Ladies First Digital Media Company to elevate your brand through a podcast or YouTube Channel. Reach out this November to Rayna at rayna@ladiesfirstdigitalmedia.com to learn more and lock in 2023 prices before they go up in 2024. Check out the Ladies First Digital Media Company to learn more. Want to grow your brand and really elevate your voice this next year? Then consider starting a podcast or YouTube Channel with the Ladies First Digital Media Company in 2024. Already have a podcast or YouTube channel but need a stellar producer to take things off of your plate and help grow your audience, consider the Ladies First Digital Media Company. Reach out this November to lock in 2023 prices before they go up in 2024. Schedule a 15-minute call with Rayna to talk through your ideas - no strings attached. Email Rayna at rayna@ladiesfirstdigitalmedia.com and write "15-minute call" in the subject line to get started. You Betcha She Did! is produced by ⁠⁠⁠⁠⁠⁠The Ladies First Digital Media Company⁠⁠⁠⁠⁠⁠. Have a question or know a fab woman who should be featured on this podcast? Contact Rayna at youbetchashedid@gmail.com If you love the show, please subscribe, share it with your friends, and leave us a positive review

Action-centred leadership asks managers to juggle three priorities: the team, the task and the individual. and in this conversation Pilar and Tim discuss one-on-one meetings, one of the best tools that managers have to work on their relationship with an individual employee. Over coffee we talk about the nuances of this style of meeting and the myriad ways managers can benefit from them. Spoiler alert: Tim is a huge fan of one-on-one meetings. Today's shows are full of links, and one or two analogies! 00:00 mins We open with Tim sharing that he's only ever had one-on-ones as the manager, never the employee. 2:30 According to the Fellow.app guide to one-on-ones you should factor in the frequency of your current work communication when setting the pattern of your one-on-ones. 3:45 Employees benefit from getting their manager's undivided attention. It feels good! 5:30 One-on-ones are particularly important for relationship building in a remote work environment, where a manager and their direct report are unlikely to "bump into" each other. 9:00 Managers can get lots of benefits from one-on-ones. It's a great place for coaching. And also for managers to dust off their technical knowledge and share it. 11:00 Tim enjoyed using one-on-ones to practice things he found challenging. Which leads to Tim sharing his "work is like a video game" analogy. 14:10 Pilar quotes from Redesigning Work by Linda Gratton where Tata Consulting found managers who initiated frequent one-to-one meetings with their team members had the highest performing teams. 14:50 Manuela Bárcenas wrote an amazingly comprehensive guide to one-on-ones for Fellow. Artemis Connection made a nice short video for how employees can get the most from them. 15:30 Even if managers don't love one-on-ones they are valuable and we need to find ways to be effective at them. Tim took a long time to feel comfortable and relied on the Know Your Team application to provide him with structure. And excellent question cards from the 1:1 starter pack and manager pack produced by Jen Dary at Be Plucky. 18:30 Having a regular one-on-one schedule is helpful to make sure that issues will be discussed. 19:40 The one-on-one is the direct report's meeting. They should get priority in setting the agenda and items for discussion. But the manager still needs to be prepared just in case the employee doesn't bring an agenda. 20:50 Tim found that when he was managing managers the one-on-ones were an important place to build alignment on big picture topics like strategy, culture and values. 22:45 It's easy to slip into operational mode. But much of the value in one-on-ones comes from it being a discussion space that is free from operational issues. 25:50 Just because it's not operational it doesn't have to be personal. There is still a lot that you can discuss. Which leads Tim to a new analogy: work is like a soap opera. What about you, dear listener? Do you do one-on-ones? Are they valuable? We'd love to hear from you! Get in touch through our Contact Form https://managementcafepodcast.com/contact/ 

Introducing Jen Dary In most of our episodes, I'm introducing you to an author of a new book, looking for ways to apply key ideas from what they've written. But every once in a while, I come across someone who I just think is interesting--someone who brings a fresh perspective to the discussion that would help all of us who want to get better at leading teams and delivering projects. Today, I'm excited to introduce you to Jen Dary. Jen is the founder of a company that champions the concept that all humans are creative, resourceful, and whole… but sometimes they have a hard time moving forward. Jen and her team help people move forward through coaching and manager training. In this episode, Jen shares her insights on issues and situations that we often find ourselves in, like Struggles when moving into a management role Knowing what to hold onto and what to let go of Delivering bad news--as well as how to deal with it when bad news is delivered to us. Jen shares lessons she's learned about balancing work and life and gives some coaching insights for anyone who's recently lost their job and wants to move forward. And how about this? We've got some ideas for those of you who are still in your job but questioning whether you should stay. Jen shares some perspective on that as well. It's a fun discussion with an insightful human that I can't wait to share with you. Learn more about Jen and her company at BePlucky.com/About.   AI for Project Managers and Leaders With the constant stream of AI news, it's sometimes hard to grasp how these advancements can benefit us as project managers and leaders in our day-to-day work. That's why I developed our e-learning course: AI Made Simple: A Practical Guide to Using AI in Your Everyday Work. This self-guided course is designed for project managers and leaders aiming to harness AI's potential to enhance your work, streamline your workflow, and boost your productivity. Go to ai.PeopleAndProjectsPodcast.com to learn more and join us. The feedback from the program has been fantastic. Take this opportunity to unlock the potential of AI for your team and projects. Thank you for joining me for this episode of The People and Projects Podcast! Talent Triangle: Power Skills   The following music was used for this episode: Music: Tropical Vibe by WinnieTheMoog Free download: https://filmmusic.io/song/10446-tropical-vibe License (CC BY 4.0): https://filmmusic.io/standard-license Music: It's Funky by Frank Schroeter Free download: https://filmmusic.io/song/8061-its-funky License (CC BY 4.0): https://filmmusic.io/standard-license

Welcome to another episode of HIRED! The Podcast! Join your host Travis Miller in an engaging conversation with the incredible Jen Dary – writer, visionary Plucky founder, and host of the "Be Plucky Podcast".In this episode, Travis and Jen explore the fascinating world of embracing unique career backgrounds and the impactful art of storytelling. Discover the significance of acknowledging individual skills and understanding the distinctive contributions that each person brings to their journey. And that's not all – get ready for an exclusive peek into the realm of successful leadership coaching. Jen's expertise shines through as she unveils the secrets behind effective coaching, leaving you inspired to lead authentically and confidently.Meet Jen Dary, an exceptional leadership coach, entrepreneur, and Plucky founder. Jen's Plucky venture empowers CEOs, entrepreneurs, and leaders, fostering healthy work dynamics. With a legacy spanning 200+ companies including Google and Facebook, Jen's impact resonates globally through coaching, small group leadership, and innovative tools. Her "Be Plucky" podcast and appearances in outlets like the Wall Street Journal and numerous podcasts such as Harvard Business Review's Women at Work, exemplify her commitment to mentorship. Jen's upcoming book chronicles her journey as a brain tumor survivor, offering inspiration through life's challenges.Tune in to this invigorating episode of HIRED! The Podcast, where Travis Miller and Jen Dary dive deep into career individuality, the power of storytelling, and the keys to successful leadership coaching._________________________________________________Connect with Jen Dary & PluckyJen Dary's LinkedIn - https://bit.ly/3Oue43fJen Dary's Social Media - @jenniferdaryPlucky - beplucky.comPlucky Linktree - https://linktr.ee/beplucksterPlucky Shop - https://shop.beplucky.com/Plucky Instagram - @beplucksterPlucky Social Media - @beplucky_________________________________________________Want to stream our podcast on another platform?iTunes - https://apple.co/3vLWiNXAudible - https://adbl.co/3vJfOu7Spotify - https://spoti.fi/3xJFQzm

Jen Dary is a highly sought-after leadership coach, entrepreneur, brain tumor survivor, mom, podcast host, and founder of Plucky where she coaches CEOs, entrepreneurs, and leaders at every level to create healthy work dynamics and a better work life for all humans. Jen had a lot of golden advice on the types of questions we should ask in informational interviews and in mentorships! She even has products that can help you with that! In the midst of all the layoffs, Jen also had pointers and tips for mid-level managers that have to deal with the layoffs and communicate them, and on the flip side, the decisions you have to make and questions you have to ask yourself on if it's finally time for you to leave your job. Definitely an episode you don't want to miss in this climate! Connect with Jen Dary: Website: www.beplucky.com LinkedIn: https://www.linkedin.com/company/beplucky/https://www.linkedin.com/in/jen-dary-46b0367/ Instagram: https://www.instagram.com/bepluckster/ Twitter: https://twitter.com/beplucky FOLLOW ME: YouTube: https://www.youtube.com/ChristineWong Instagram: https://www.instagram.com/christine.innovates Linkedin: https://www.linkedin.com/in/christineywong Facebook: https://www.fb.me/ChristineWongFB Website: https://christineywong.me/ --- Support this podcast: https://podcasters.spotify.com/pod/show/christinewong/support

Who are you now, who do you want to be, and how can you stretch without taking on too much? Jen Dary regularly coaches first-time managers on these questions. She shares advice for finding yourself anew at work, dealing with disillusionment, and setting priorities and boundaries. Then, a former guest who's one year into leading a major project tells us about her aha moments. Finally, Kelsey answers the question of whether or not she's ready to try management again.

In 2016, Jen was faced with a life-changing event when she discovered a brain tumor. Determined to beat the odds, she underwent a craniotomy and took a break from her business for six months to recover. During this time, she wrote a book about her experience, "I Believe in Everything", which took her six years to complete. However, despite her efforts, the book faced rejection and Jen took a pause for her mental health. She is now considering starting her own independent press. Jen's journey is not just about overcoming a health challenge but also about finding purpose and leaving a lasting impact. Her journey also includes the transition from being a head of employee development at a creative firm to starting her own coaching business. She emphasizes the importance of finding the right audience for your business and working to mitigate risks before launching. She reflects on how she has worked on reinvented herself multiple times, some in small ways but some in bigger roles, starting multiple businesses and now moving onto a new chapter in her life. Jen recognizes the significance of connections in business and shares her insights on the questions that need to be asked in a mentorship relationship. Despite her success, she acknowledges her biggest fear in life is something happening to her children. She believes in reading the energy of what is ready to happen and not forcing herself through something that is not meant to be. Jen's story is a testament to the importance of finding purpose and leaving a lasting impact. Her journey is a reminder that life can be quick, sandy, and sometimes inspiring and terrifying at the same time. However, with determination and a positive mindset, anyone can overcome challenges and achieve their goals. Questions at the end of the show: What is your biggest fear and how do you plan to face it? What are your beliefs about success and how do they affect your daily choices? What is one experience you have had that you would like to relive and why? Jen Dary is a highly sought-after leadership coach and the founder of Plucky, a leadership coaching and consulting firm. She is also the survivor of a meningioma brain tumor, which was removed via brain surgery in 2016, a challenging experience that earned Jen a refreshed perspective and new goals for Plucky. A people person through and through, Jen's joy comes from connecting with people in every way. As a leadership coach, Jen works with individuals and companies to create healthy dynamics at work. To date, Jen has empowered professionals at over 200 companies, including Google, Facebook, The New York Times, Slack, Code for America and many digital agencies in tech and tech-adjacent industries. As a coach, Jen empowers her clients to move confidently along their individual career paths as leaders and creatives. Jen has taught over twenty cohorts of new managers in her “So Now You're A Manager” program and built a thriving community of leaders who support each other through the Plucky network. She is also the creator of specialized tools and resources for leadership (found here) which have been purchased and implemented by companies around the world. Jen lives in Arlington, VA with her husband and young sons. She finished writing her first book (about the brain tumor) which will be released in the coming year. More at beplucky.com @jenniferdary @beplucky on socials --- Send in a voice message: https://podcasters.spotify.com/pod/show/warriormindset/message Support this podcast: https://podcasters.spotify.com/pod/show/warriormindset/support

Galen Low is joined by Jen Dary—a leadership coach, speaker, and founder of Plucky—to talk about those crucial but otherwise adjacent and invisible skills that separate the great project managers from the rest of the pack.

Steph and Chris are recording together! Like, in the same room, physically together. Chris talks about slowly evolving the architecture in an app they're working on and settling on directory structure. Steph's still working on migrating unit tests over to RSpec. They answer a listener question: "As senior-level developers, how do you set goals to ensure that you keep growing?" This episode is brought to you by BuildPulse (https://buildpulse.io/bikeshed). Start your 14-day free trial of BuildPulse today. Faking External Services In Tests With Adapters (https://thoughtbot.com/blog/faking-external-services-in-tests-with-adapters) Testing Third-Party Interactions (https://thoughtbot.com/blog/testing-third-party-interactions) Jen Dary - On Future Goals (https://www.beplucky.com/on-future-goals/) Charity Majors - The Engineer Manager Pedulum (https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/) Charity Majors Bike Shed Episode (https://www.bikeshed.fm/302) Become a Sponsor (https://thoughtbot.com/sponsorship) of The Bike Shed! Transcript: STEPH: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Steph Viccari. CHRIS: And I'm Chris Toomey. STEPH: And together, we're here to share a bit of what we've learned along the way. So, hey, Chris, what's new in your world? CHRIS: What is new in my world? Actually, this episode feels different. There's something different about it. I can't quite put my finger on it. I think it may be that we're actually physically in the same room recording for the first time in two years and a little bit more, which is wild. STEPH: I can't believe it's been that long. I feel like it wasn't that long ago that we were in The Bike Shed...oh, I said The Bike Shed studio. I'm being very biased. Our recording studio [laughs] is the more proper description for it. Yeah, two and a half years. And we tried to make this happen a couple of months ago when I was visiting Boston, and then it just didn't work out. But today, we made it. CHRIS: Today, we made it. Here we are. So hopefully, the audio sounds great, and we get all that more richness in conversation because of the physical in-person manner. We're trying it out. It'll be fun. But let's see, to the normal tech talk and nonsense, what's new in my world? So we've been slowly evolving the architecture in the app that we're working on. And we settled on something that I kind of like, so I wanted to talk about it, directory structure, probably the most interesting topic in the world. I think there's some good stuff in here. So we have the normal stuff. There are app models, app controllers, all those; those make sense. We have app jobs which right now, I would say, is in a state of flux. We're in the sad place where some things are application records, and some things are Sidekiq workers. We have made the decision to consolidate everything onto Sidekiq workers, which is just strictly more powerful as to the direction we're going to go. But for right now, I'm not super happy with the state of app jobs, but whatever, we have that. But the things that I like so we have app commands; I've talked about app commands before. Those are command objects. They use dry-rb do notation, and they allow us to sequence a bunch of things that all may fail, and we can process them all in a much more reasonable way. It's been really interesting exploring that, building on it, introducing it to new developers who haven't worked in that mode before. And everyone who's come into the project has both picked it up very quickly and enjoyed it, and found it to be a nice expressive mode. So app commands very happy with that. App queries is another one that we have. We've talked about this before, query objects. I know we're a big fan. [laughs] I got a golf clap across the room here, which I could see live in person. It was amazing. I could feel the wind wafting across the room from the golf clap. [chuckles] But yeah, query objects, they're fantastic. They take a relation, they return a relation, but they allow us to build more complex queries outside of our models. The new one, here we go. So this stuff would all normally fall into app services, which services don't mean anything. So we do not have an app services directory in our application. But the new one that we have is app clients. So these are all of our HTTP clients wrapping external third parties that we're interacting with. But with each of them, we've taken a particular structure, a particular approach. So for each of them, we're using the adapter pattern. There's a blog post on the Giant Robots blog that I can point to that sort of speaks to the adapter pattern that we're using here. But basically, in production mode, there is an HTTP backend that actually makes the real requests and does all that stuff. And in test mode, there is a test backend for each of these clients that allows us to build up a pretty representative fake, and so we're faking it up before the HTTP layer. But we found that that's a good trade-off for us. And then we can say, like, if this fake backend gets a request to /users, then we can respond in whatever way that we want. And overall, we found that pattern to be really fantastic. We've been very happy with it. So it's one more thing. All of them were just gathering in-app models. And so it was only very recently that we said no, no, these deserve their own name. They are a pattern. We've repeated this pattern a bunch. We like this pattern. We want to even embrace this pattern more, so long live app clients. STEPH: I love it. I love app clients. It's been a while since I've been on a project that had that directory. But there was a greenfield project that I was working on. I think it might have been I was working with Boston.rb and working on giving them a new site or something like that and introduced app clients. And what you just said is perfect in terms of you've identified a pattern, and then you captured that and gave it its own directory to say, "Hey, this is our pattern. We've established it, and we really like it." That sounds awesome. It's also really nice as someone who's new to a codebase; if I jump in and if I look at app clients, I can immediately see what are the third parties that we're working with? And that feels really nice. So yeah, that sounds great. I'm into it. CHRIS: Yeah, I think it really was the question of like, is this a pattern we want to embrace and highlight within the codebase, or is this sort of a duplication but irrelevant like not really that important? And we decided no, this is a thing that matters. We currently have 17 of these clients, so 17 different third-party external things that we're integrating with. So for someone who doesn't really like service-oriented architecture, I do seem to have found myself in a place. But here we are, you know, we do what we have to with what we're given. But yes, 17 and growing our app clients. STEPH: That is a lot. [laughs] My eyes widened a bit when you said 17. I'm curious because you highlighted that app services that's not really a thing. Like, it doesn't mean anything. It doesn't have the same meaning of the app queries directory or app commands or app clients where it's like, this is a pattern we've identified, and named, and want to propagate. For app services, I agree; it's that junk drawer. But I guess in some ways...well, I'm going to say something, and then I'm going to decide how I feel about it. That feels useful because then, if you have something but you haven't established a pattern for it, you need a place for it to go. It still needs to live somewhere. And you don't necessarily want to put it in app models. So I'm curious, where do you put stuff that doesn't have an established pattern yet? CHRIS: It's a good question. I think it's probably app models is our current answer. Like, these are things that model stuff. And I'm a big believer in the it doesn't need to be an application record-backed object to go on app models. But slowly, we've been taking stuff out. I think it'd be very common for what we talk about as query objects to just be methods in the respective application record. So the user record, as a great example, has all of these methods for doing any sort of query that you might want to do. And I'm a fan of extracting that out into this very specific place called app queries. Commands are now another thing that I think very typically would fall into the app services place. Jobs naming that is something different. Clients we've got serializers is another one that we have at the top level, so those are four. We use Blueprinter within the app. And again, it's sort of weird. We don't really have an API. We're using Inertia. So we are still serializing to JSON across the boundary. And we found it was useful to encapsulate that. And so we have serializers as a directory, but they just do that. We do have policies. We're using Pundit for authorization, so that's another one that we have. But yeah, I think the junk drawerness probably most goes to app models. But at this point, more and more, I feel like we have a place to put things. It's relatively clear should this be in a controller, or should this be in a query object, or should this be in a command? I think I'm finding a place of happiness that, frankly, I've been searching for for a long time. You could say my whole life I've been searching for this contented state of I think I know where stuff goes in the app, mostly, most of the time. I'm just going to say this, and now that you've asked the excellent question of like, yeah, but no, where are you hiding some stuff? I'm going to open up models. Next week I'm going to be like, oh, I forgot about all of that nonsense. But the things that we have defined I'm very happy with. STEPH: That feels really fair for app models. Because like you said, I agree that it doesn't need to be ActiveRecord-backed to go on app models. And so, if it needs to live somewhere, do you add a junk drawer, or do you just create app models and reuse that? And I think it makes a lot of sense to repurpose app models or to let things slide in there until you can extract them and let them live there until there's a pattern that you see. CHRIS: We do. There's one more that I find hilarious, which is app lib, which my understanding...I remember at one point having one of those afternoons where I'm just like, I thought stuff works, but stuff doesn't seem to work. I thought lib was a directory in Rails apps. And it was like, oh no, now we autoload only under the app. So you should put lib under app. And I was just like, okay, whatever. So we have app lib with very little in it. [laughs] But that isn't so much a junk drawer as it is stuff that's like, this doesn't feel specific to us. This goes somewhere else. This could be extracted from the app. But I just find it funny that we have an app lib. It just seems wrong. STEPH: That feels like one of those directories that I've just accepted. Like, it's everywhere. It's like in all the apps that I work in. And so I've become very accustomed to it, and I haven't given it the same thoughtfulness that I think you have. I'm just like, yeah, it's another place to look. It's another place to go find some stuff. And then if I'm adding to it, yeah, I don't think I've been as thoughtful about it. But that makes sense that it's kind of silly that we have it, and that becomes like the junk drawer. If you're not careful with it, that's where you stick things. CHRIS: I appreciate you're describing my point of view as thoughtfulness. I feel like I may actually be burdened with historical knowledge here because I worked on Rails apps long, long ago when lib didn't go in-app, and now it does. And I'm like, wait a minute, but like, no, no, it's fine. These are the libraries within your app. I can tell that story. So, again, thank you for saying that I was being thoughtful. I think I was just being persnickety, and get off my lawn is probably where I was at. STEPH: Oh, full persnicketiness. Ooh, that's tough to say. [laughs] CHRIS: But yeah, I just wanted to share that little summary, particularly the app clients is an interesting one. And again, I'll share the adapter pattern blog post because I think it's worked really well for us. And it's allowed us to slowly build up a more robust test suite. And so now our feature specs do a very good job of simulating the reality of the world while also dealing with the fact that we have these 17 external situations that we have to interact with. And so, how do you balance that VCR versus other things? We've talked about this a bunch of times on different episodes. But app clients has worked great with the adapter pattern, so once more, rounding out our organizational approach. But yeah, that's what's up in my world. What's up in your world? STEPH: So I have a small update to give. But before I do, you just made me think of something in regards to that article that talks about the adapter pattern. And there's also another article that's by Joël Quenneville that's testing third-party interactions. And he made me reflect on a time where I was giving the RSpec course, and we were talking about different ways to test third-party interactions. And there are a couple of different ways that are mentioned in this article. There are stub methods on adapter, stub HTTP request, stub request to fake adapter, and stub HTTP request to fake service. All that sounds like a lot. But if you read through the article, then it gives an example of each one. But I've found it really helpful that if you're in a space that you still don't feel great about testing third-party interactions and you're not sure which approach to take; if you work with one API and apply all four different strategies, it really helps cement how to work through that process and the different benefits of each approach and the trade-offs. And we did that during the RSpec course, and I found it really helpful just from the teacher perspective to go through each one. And there were some great questions and discussions that came out of it. So I wanted to put that plug out there in the world that if you're struggling testing third-party interactions, we'll include a link to this article. But I think that's a really solid way to build a great foundation of, like, I know how to test a third-party app. Let me choose which strategy that I want to use. Circling back to what's going on in my world, I am still working on migrating unit tests over to RSpec. It's a thing. It's part of the work that I do. [laughs] I can't say it's particularly enjoyable, but it will have a positive payoff. And along that journey, I've learned some things or rediscovered some things. One of them is read expectations very carefully. So when I was migrating a test over to RSpec, I read it as where we expected a record to exist. The test was actually testing that a record did not exist. And so I probably spent an hour understanding, going through the code being like, why isn't this record getting created like I expect it to? And I finally went back, and I took a break, and I went back. And I was like, oh, crap, I read the expectation wrong. So read expectations very carefully. The other one...this one's not learned, but it is reinforced. Mystery Guests are awful. So as I've been porting over the behavior over to RSpec, the other tests are using fixtures, and I'm moving that over to use factorybot instead. And at first, I was trying to be minimal with the data that I was bringing over. That failed pretty spectacularly. So I have learned now that I have to go and copy everything that's in the fixtures, and then I move it over to factorybot. And it's painful, but at least then I'm doing that thing that we talked about before where I'm trying to load as little context as possible for each test. But then once I do have a green test, I'm going back through it, and I'm like, okay, we probably don't care about when you were created. We probably don't care when you're updated because every field is set for every single record. So I am going back and then playing a game of if I remove this line, does the test still pass? And if I remove that line, does the test still pass? And so far, that has been painful, but it does have the benefit of then I'm removing some of the setup. So Mystery Guests are very painful. I've also discovered that custom error messages can be tricky because I brought over some tests. And some of these, I'm realizing, are more user error than anything else. Anywho, I added one of the custom error messages that you can add, and I added it over to RSpec. But I had written an incorrect, invalid statement in RSpec where I was looking...I was expecting for a record to exist. But I was using the find by instead of where. So you can call exist on the ActiveRecord relation but not on the actual record that gets returned. But I had the custom error message that was popping up and saying, "Oh, your record wasn't found," and I just kept getting that. So I was then diving through the code to understand again why my record wasn't found. And once I removed that custom error message, I realized that it was actually because of how I'd written the RSpec assertion that was wrong because then RSpec gave me a wonderful message that was like, hey, you're trying to call exist on this record, and you can't do that. Instead, you need to call it on a relation. So I've also learned don't bring over custom error messages until you have a green test, and even then, consider if it's helpful because, frankly, the custom error message wasn't that helpful. It was very similar to what RSpec was going to tell us in general. So there was really no need to add that custom step to it. For the final bit that I've learned or the hurdle that I've been facing is that migrating tests descriptions are hard unless they map over. So RSpec has the context and then a description for it that goes with the test. Test::Unit has methods like method names instead. So it may be something like test redemption codes, and then it runs through the code. Well, as I'm trying to migrate that knowledge over to RSpec, it's not clear to me what we're testing. Okay, we're testing redemption codes. What about them? Should they pass? Should they fail? Should they change? What are they redeeming? There's very little context. So a lot of my tests are copying that method name, so I know which tests I'm focused on, and I'm bringing over. And then in the description, it's like, Steph needs help adding a test description, and then I'm pushing that up and then going to the team for help. So they can help me look through to understand, like, what is it that this test is doing? What's important about this domain? What sort of terminology should I include? And that has been working, but I didn't see that coming as part of this whole migrating stuff over. I really thought this might be a little bit more of a copypasta job. And I have learned some trickery is afoot. And it's been more complicated than I thought it was going to be. CHRIS: Well, at a minimum, I can say thank you for sharing all of your hard-learned lessons throughout this process. This does sound arduous, but hopefully, at the end of it, there will be a lot of value and a cleaned-up test suite and all of those sorts of things. But yeah, it's been an adventure you've been on. So on behalf of the people who you are sharing all of these things with, thank you. STEPH: Well, thank you. Yeah, I'm hoping this is very niche knowledge that there aren't many people in the world that are doing this exact work that this happens to be what this team needs. So yeah, it's been an adventure. I've certainly learned some things from it, and I still have more to go. So not there yet, but I'm also excited for when we can actually then delete this portion of the build process. And then also, I think, get rid of fixtures because I didn't think about that from the beginning either. But now that I'm realizing that's how those tests are working, I suspect we'll be able to delete those. And that'll be really nice because now we also have another single source of truth in factory_bot as to how valid records are being built. Mid-Roll Ad: Flaky tests take the joy out of programming. You push up some code, wait for the tests to run, and the build fails because of a test that has nothing to do with your change. So you click rebuild, and you wait. Again. And you hope you're lucky enough to get a passing build this time. Flaky tests slow everyone down, break your flow and make things downright miserable. In a perfect world, tests would only break if there's a legitimate problem that would impact production. They'd fail immediately and consistently, not intermittently. But the world's not perfect, and flaky tests will happen, and you don't have time to fix them all today. So how do you know where to start? BuildPulse automatically detects and tracks your team's flaky tests. Better still, it pinpoints the ones that are disrupting your team the most. With this list of top offenders, you'll know exactly where to focus your effort for maximum impact on making your builds more stable. In fact, the team at Codecademy was able to identify their flakiest tests with BuildPulse in just a few days. By focusing on those tests first, they reduced their flaky builds by more than 68% in less than a month! And you can do the same because BuildPulse integrates with the tools you're already using. It supports all the major CI systems, including CircleCI, GitHub Actions, Jenkins, and others. And it analyzes test results for all popular test frameworks and programming languages, like RSpec, Jest, Go, pytest, PHPUnit, and more. So stop letting flaky tests slow you down. Start your 14-day free trial of BuildPulse today. To learn more, visit buildpulse.io/ bikeshed. That's buildpulse.io/bikeshed. Pivoting just a bit, there's a listener question that I'm really excited for us to dive into. And this listener question comes from Joël Quenneville. Hey, Joël. All right, so Joël writes in, "As senior-level developers, how do you set goals to ensure that you keep growing? How do you know what are high-value areas for you to improve? How do you stay sharp? Do you just keep adding new languages to your tool belt? Do you pull back and try to dig into more theoretical concepts? Do you feel like you have enough tech skills and pivot to other things like communication or management skills? At the start of a dev career, there's an overwhelming list of things that it feels like you need to know all at once. Eventually, there comes a point where you no longer feel like you're drowning under the list of things that you need to learn. You're at least moderately competent in all the core concepts. So what's next?" This is a big, fun, scary question. I really like this question. Thank you, Joël, for sending it in because I think there's so much here that can be discussed. I can kick us off with a few thoughts. I want to first highlight one of the things that...or one of the things that resonates with me from this question is how Joël describes going through and reaching senior status how it can really feel like working through a backlog of features. So as a developer, I want to understand this particular framework, or as a developer, I want to be able to write clear and fast tests, or as a developer, I want to contribute to an open-source project. But now that that backlog is empty, you're wondering what's next on your roadmap, which is where I think that sort of big, fun scariness comes into play. So the first idea is to take a moment and embrace that success. You have probably worked really hard to get where you're at in your career. And there's nothing wrong with taking a pause and enjoying the view and just being appreciative of the fact that you are able to get your work done quickly or that you feel very confident in the work that you're doing. Growth is often very important to our careers, but I also think it's important to recognize when you've achieved certain growth and then, if you want to, just enjoy that and pause. And you're not constantly pushing yourself to the next level. I think that is a totally reasonable and healthy thing to do. The second thing that comes to mind is that you're on a Choose Your Own Adventure mode now, so you get to...I would encourage folks, once you've reached this stage, to reflect on where you're at and consider what is your dream? What are your aspirations? Maybe they're related to tech; maybe they're not. And consider where is it that you want to go next? And then, what are the concrete steps that will help you achieve those goals? So there's a really great article by Jen Dary, who's a career coach and owner of Plucky Manager Training, that describes this process. And there's a really great blog post that I'll be sure to include a link to in the show notes. But she has a couple of great questions that will then help you identify, like, what are my goals? Some of those questions are, "If I could do anything and money wasn't an object, I'd spend my time doing dot dot dot." And that doesn't necessarily mean sitting on a beach with your toes in the sand all day. I mean, it could, but then that probably just means you need a vacation. So take the vacation. And then, once you start to get bored, where does your mind start to wander? What are the things that you want to do? Where are you interested in spending your time? And then, once you have an idea of how you'd like to spend your time, you can consider what actions you could take next that will point you in that direction. There's also the benefit that by this point, you probably have an idea of the type of things that you like to do and where you like to spend your time. And so you can figure out which areas of expertise you want to invest in. So do you like more greenfield projects? Do you like architecture discussions? Do you like giving talks? Do you like teaching? Or maybe you're interested in management. I think there's also a more concrete approach that you can take that. You can just talk to your managers in your team and say, "Hey, what big, hard problems are you looking to solve? And then, you can get some inspiration from them and see if their problems align with your interests. Maybe it's not even your own team, but you can talk to other companies and see what other problems industries are trying to solve. That might be an area that then spurs some curiosity or some interest. And then, where do you feel underutilized? So with your current day-to-day, are there areas where you feel that you wish you had more responsibilities or more opportunities, but you feel like you don't have access to those opportunities? Maybe that's an area to explore as well. This feels like a wonderful coaching question in terms of you have done it; congratulations. You've reached a really great spot in your career. And so now you're figuring out that big next step. This is going to be highly customized to each person to then figuring out what it is that's going to help you feel fulfilled over the next five years, ten years, however long you want to project out. Those are some of my thoughts. How about you? What do you think? CHRIS: Well, first, those are some great thoughts. I appreciate that I get to follow them now. It's going to be a hard act to follow. But yeah, I think Joël has asked a fantastic question. And coming from Joël, I know how intentional and thoughtful a learner, and sharer, and teacher and all of these things are. So it's all the more sort of framed in that for me knowing Joël personally. I think to start, the kernel of the question is as senior developers, that's the like...or senior level developers is the way Joël phrased it, but it treats it as sort of this discrete moment in time, which I think there's maybe even something to unpack. And I think we've probably talked about this in previous episodes, but like, what does that even mean? And I think part of the story here is going from reactive where it's like, I don't know how anything works. I know a little bit. I can code some. And every day, I'm presented with new problems that I just don't understand. And I'm trying to build up that base of knowledge. Slowly, you know, you start, and it's like 95% of the time you feel like that. And slowly, the dial switches over, and maybe it's only 25% of the time you feel like that. Somewhere along that spectrum is the line of senior developer. I don't actually know where it is, but it's somewhere in there. And so I think it's that space where you can move from reactive learning things as necessitated by the work that's coming at you to I want to proactively choose the things that I want to be learning to try and expand the stuff that I know, and the ways that I can think about the work without being in direct response to a piece of work coming at me. So with that in mind, what do you do with this proactive space? And I think the way Joël frames the question, again, to what I know of Joël, he's such an intentional person. And I wouldn't be surprised if Joël is very purposeful and thinks about this and has approached it as a specific thing that he's doing. I have certainly been in more of “I'll figure it out when I get there.” I'll explore. Or actually, probably the most pointed thing that I did was I joined a consultancy. And that was a very purposeful choice early on in my career because I'm like, I think I know a little bit. I don't think I know a lot. I would like to know a lot. That seems fun. So what do I think is the best way to do that? My guess, and it turned out to be very much true, is if I join a consultancy, I'm going to see a bunch of different projects, different types of technologies, organizations, communication structure, stuff that works, stuff that doesn't work. And to be honest, I actually thought I would try out the consultancy thing for a little while, like a year or two, and then go on to my next adventure. Spoiler alert: I stayed for seven years. It was one of the best periods of my professional life. And I found it to be a much deeper well than I expected it to be. But for anyone that's looking for, like, how can I structure my career in a way that will just automatically provide the sort of novelty and space to grow? I would highly recommend a consultancy like thoughtbot. I wonder if they're hiring. STEPH: Well, yes, we are hiring. That was a perfect plug that I wasn't expecting for that to come. But yes, thoughtbot is totally hiring. We'll include a link in the show notes to all the jobs. [laughs] CHRIS: Sounds fantastic. But very sincerely, that was the best choice that I could have made and was a way to flip the situation around such that I don't have to be thinking about what I want to be learning. The learning will come to me. But even within that, I still tried to be intentional from time to time. And I would say, again, I don't have a holistic theory of how to improve. I just have some stuff that's kind of worked out well. One thing is focusing on fundamentals wherever I can, or a different way to put it is giving myself permission to spend a little bit more time whenever my work brushes up against what I would consider fundamentals. So things that are in that space are like SQL. Every time I'm working on something, I'm like, ah, I could use like a CROSS JOIN here, but I don't know what that is. Maybe I'll spend an extra 30 minutes Googling around and trying to figure out what a CROSS JOIN is. Is that a thing? Is a CROSS JOIN a real thing? I may be making it up. [laughs] A window function, I know that those are real. Maybe I'll learn what a window function is. I think a CROSS JOIN is a real thing. A LEFT OUTER JOIN that's a cool thing. And so, each time I've had that, SQL has been something that expanding my knowledge; I've continually felt like that was a good investment. Or fundamentals of HTTP, that's another one that really has served me well. With Ruby being the primary language that I program in, deeply understanding the language and the fundamentals and the semantics of it that's another place that has been a good investment. But by contrast, I would say I probably haven't gone as deep on the frameworks that I work with. So Rails is maybe a little bit different just because, like many people, I came to Ruby through Rails, and I've learned a lot of Rails. But like in JavaScript, I've worked with many different JavaScript frameworks. And I have been a little more intentional with how much time I invest into furthering my skills in them because I've seen them change and evolve enough times. And if anything, I'm trying to look for ones that are like, what if it's less about the framework and more about JavaScript and web fundamentals underneath? Thus, I've found myself in Svelte land. But I think it's that choice of trying to anchor to fundamentals wherever possible. And then I would say the other thing that's been really beneficial for me is what can I do that's wildly outside the stuff that I already know? And so probably the most pointed example I have of this is learning Elm. So I previously spent most of my career working in Ruby and JavaScript, so primarily object-oriented languages without a strong type system. And then, I was able to go over and experience this whole different paradigm way of working, way of structuring programs, feedback loop. There was so much about it that was really, really interesting. And even though I don't get to work in Elm, frankly, as much as I would want at this point or really at all, it informs everything that I do moving forward. And I think that falls out of the fact that it was so different than what I was doing. So if I were to do that again, probably the next type of language I would learn is Lisp because those are like, well, that's a whole other category of thing that I've heard about. People say some fun stuff about them, but I don't really know. So it's that fundamentals and weird stuff is how I would describe it. And by weird, I mean outside of the core base of knowledge that I have. STEPH: I love that categorization, and I'll stick with it, fundamentals and weird stuff, to stretch and grow and find some other areas. I also really like your framing, the reactive versus proactive. I think that's a really nice way to put it because so much of your career is you are just learning what your company needs you to learn, or you're learning what you need to keep progressing and to feel more competent with the types of features or the work that you're handling. And I think that's why Jen Dary's blog post resonates with me so much because it's probably...up until now, a lot of someone's career, maybe not Joël's particularly, but I know probably for my career, a lot of it has been reactive in terms of what are the things that I need to learn? And so then once you reach that point of like, okay, I feel competent and reasonably good at all the things that I needed to know, where do I want to go next? And rather than focus on necessarily the plans that are laid out in front of me, I can then go wide and think about what are some of the bigger things that I want to tackle? What are the things that are meaningful to me? Because then I can now push forward to this bigger goal versus achieving a particular salary band or title or things like that. But I can focus on something else that I really want to contribute to. And there do seem to be two common paths. So once you reach that level, either you typically go into management, or you become that more like principal and then onward and upward, whatever is after principal. I don't even know what's after that, [laughs] but the titles that come after principal. So there's management, and then I've seen the other very strong contributors, so Aaron Patterson comes to mind. And I feel like those people then typically will migrate to places where they get to contribute to a language or to a framework. And I think it comes down to the idea of impact because both of those provide a greater impact. So if you go into management, you can influence and affect a team of individuals, and you can increase the value created by that team. Then you've likely exceeded the value that you would have created as your own individual contributor. Or, if you contribute to a language or a framework, then your technical decisions impact a larger community. So I think that would be another good thing to reflect on is what type of impact am I looking for? What type of communities do I want to have a positive impact on? And that may spur some inspiration around where you want to go next, the things that you want to focus on. CHRIS: Yeah, I think one of the things we're picking up in that that Joël mentioned in his question is the idea of there is the individual contributor path. But then there's also the management path, which is the typical sort of that's the progression. And I think, for one, naming that the individual contributor path and the idea of going to principal dev and those sorts of outcomes is a fantastic path in and of itself. I think often it's like, well, you know, you go along for a certain amount of time, and then you become a manager. It's like, those are actually distinctly different things. And people have different levels of interest and aptitude in them, and I think recognizing that is critically important. And so, not expecting that management just comes after individual contributor is an important thing. The other thing I'll say is Charity Majors, who we had on the podcast a bit back, has a wonderful blog post about the pendulum swing called The Engineer/Manager Pendulum. And so in it, she talks about folks that have taken an exploration over into manager land and then come back to the individual contributor path or vice versa sort of being able to move between them, treating them as two potentially parallel career tracks but ones that we can move between. And her assertion is that often folks that are particularly strong have spent some time in both camps because then you gain this empathy, this understanding of what's the whole picture? How are we doing all of this? How do we think about communication, et cetera? So, again, to name it, like, I think it's totally fine to stay on one of those tracks to really know which of those tracks speaks to you or to even move between them a little bit and to explore it and to find out what's true. So we'll include a link to that in the show notes. And we'll also include a link to the previous episode a while back when we had Charity on. But yeah, those I think are some critical thoughts as well because those are different areas that we can grow as developers and expand on our impact within the team. And so, we want to make sure we have those options on the table as well. STEPH: Absolutely. I love where teams will support individuals to feel comfortable shifting between experiences like that because it does make you a more well-rounded contributor to that product team, not just as an engineer, but then you will also understand what everybody else is working on and be able to have more meaningful conversations with them about the company goals and then the type of work that's being done. So yeah, I love it. If you're in a place that you can maybe fail a little bit, hopefully not in a too painful way, but you can take a risk and say, "Hey, I want to try something and see if I like it," then I think that's wonderful. And take the risk and see how it goes. And just know that you have an exit strategy should you decide that you don't like that work or that type of work isn't for you. But at least now you know a little bit more about yourself. Overall, I want to respond directly to something that Joël highlighted around how do you know what are high-value areas for you to improve? And I think there are two definitions there because you can either let the people around you and your team define that high value for you, and maybe that really resonates with you, and it's something that you enjoy. And so you can go to your manager and say, "Hey, what are some high-value areas where I can make an impact for the team?" Or it could be very personal. And what are the high-value areas for you? Maybe there's a particular industry that you want to work on. Maybe you want to hit the public speaking circuit. And so you define more intrinsically what are those high-value areas for you? And I think that's a good place to start collecting feedback and start looking at what's high value for you personally and then what's high value to the company and see if there's any overlap there. With that, I think we've covered a good variety of things to explore and then highlighted some of the different ways that you and I have also considered this question. I think it's a fabulous question. Also, I think it's one, even if you're not at that senior level, to ask this question. Like, go ahead and start asking it early and often and revisit your answers and see how they change. I think that would be a really powerful habit to establish early in your career and then could help guide you along, and then you can reflect on some of your earlier choices. So, Joël, thank you so much for that question. STEPH: On that note, shall we wrap up? CHRIS: Let's wrap up. The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review on iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey. STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeeee!!!!!!! ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Often, when we think of coaches, we think of someone involved in the life and performance of an athlete, or someone who is responsible for pushing us and bringing out the best in us. Jen Dary is a leadership coach, mom, business owner, and founder of Plucky, and is our guest this week. Listen to this week's episode as she discusses her unique and creative approach to coaching others to be their best.    >> Plucky >> Jen Dary on Twitter >> Jen Dary on LinkedIn >> Jen Dary on Instagram

Hot Damn. This episode. 'Tis the Season for Soul Searching, indeed.Jen found herself -  successful entrepreneur, thirty-something, mother of two young boys - sitting on the other end of a phone call that said, “You have a brain tumor.” This conversation is equal parts head and heart, with a hefty dose of middle fingers to the air.  If you're building a business, or just a big life, this episode is for you.  Jen Dary is the real f*cking deal.Hit play. Listen to this brilliant, beautiful, complex and lovely soul. We are forever grateful for your advice all those years ago (listen ~3:18), and the magic you're committed to bringing the world through your coaching, your products (click here to buy, y'all!), your parenting, your writing, and your being.We love you.

Chris regains several of his developer merit badges and embarks on a perilous CSRF (Cross-Site Request Forgery) adventure. Steph shares highlights from Plucky, a management training course, including ways we can "click" and "break apart" from our current role, and how to have hard conversations. They also discuss how software development processes change at different team sizes, processes that break down as teams grow, and processes that are resilient at any team size. This episode is brought to you by ScoutAPM (https://scoutapm.com/bikeshed). Give Scout a try for free today and Scout will donate $5 to the open source project of your choice when you deploy The Nightmare Before Christmas - What's This (https://youtu.be/QLvvkTbHjHI) Giant Robots Smashing into other Giant Robots - Plucky with Jen Dary (https://www.giantrobots.fm/search?utf8=%E2%9C%93&term=plucky) Plucky (https://www.beplucky.com/) Services are Not a Silver Bullet (https://thoughtbot.com/blog/services-are-not-a-silver-bullet) Become a Sponsor (https://thoughtbot.com/sponsorship) of The Bike Shed! Transcript: STEPH: Boom. I'm recording. Magic is happening. [singing] What's this? What's this? It's a Bike Shed episode. What's this? What's this? CHRIS: You did that on the mic. [laughter] So you just started recording too, so it's not like you're like, "Oh, I forgot I was recording." STEPH: Oh, I didn't have a finishing line that rhymes with shed. CHRIS: Head, dead, bread, spread. STEPH: [singing] Is TDD dead? I don't know. [laughs] CHRIS: Cool. I liked it. STEPH: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Steph Viccari. CHRIS: And I'm Chris Toomey. STEPH: And together, we're here to share a bit of what we've learned along the way. Hey, Chris, what's new in your world? CHRIS: What's new? I had a fun experience over the past week or two of regaining some of my developer merit badges, which is always enjoyable. So one was I had to configure AWS, specifically S3 and IAM such that I could upload files to an S3 bucket, which seems like one of those things that a developer should be able to do, and it's just not that hard. And, man, I failed so many times, and I stared at the screen. And the ARNs I think that's another acronym that I had to try and figure out what it means and fight against. Anyway, I got there. So that's one merit badge earned. I really hope [laughs] I correctly and securely configured access to an S3 bucket such that we could upload files in our Rails app. Cool, neat. Moving on, the next merit badge that I went for was restoring the sea of green dots. Our RSpec output had gathered some noise. There was a whole bunch of noise across a variety of things. There were some dev tools that were dumping some stuff in there. And there was something related to apparition, which is the...I want to say it's the Capybara feature spec driver that we're using now, which sits on top of ChromeDriver or something like that. I don't really understand the details, but it was complaining about something. And I found a fix, and then I fixed it and whatnot. But it was one of those. I did this on a Saturday because I was just like, you know what? This will be cathartic and healing. And then I got to the sea of green dots, and I was so happy to get to it. STEPH: This is me...I'm giving you a round of applause. CHRIS: Well, thank you. Arguable whether it delivered any real value to users, but again, this was Saturday effort, so I was allowed to indulge my fastidious caretaker of the code role. STEPH: Sorry, before we move on to more serious, can we pause to talk about developer merit badges? I really, really want cute felt badges that we can...I mean, I can't design them. I don't have the talent. But I think between us and other folks, we could design amazing merit badges, and then people could collect those. I'm very much in love with that idea. CHRIS: I love the idea. I am now certain that if we were to really pursue this, that we would fall into the deepest of bike sheds as we try and define well; what are all the merit badges? And what are the different levels? STEPH: [laughs] CHRIS: And how many do you need to collect before you can get to what are the different...There are just so many different taxonomies that we could introduce, and, oh man, I could spend a couple of weeks on that. STEPH: [laughs] It has a very strong Pokémon vibe too of you got to catch them all. CHRIS: Absolutely. STEPH: Okay. All right. We won't digress into bikeshedding merit badges, but I'm still very, very interested in that idea. CHRIS: Indeed. If anyone out there in the listener space wants to just make these, that would be great. This is the way that I avoid bikeshedding now is I just say I'm not allowed to make these decisions or even think about it. But if these happened into the world, I would be happy about that. STEPH: Oh, I just remembered we do have something similar at thoughtbot. They're not physical where you can hold them, but I think we've talked about turning them into physical badges. But we have our internal tool hub that we used to track our schedules. And one of the fun Ralphapalooza events that we had, a team came up with the idea of introducing badges in the tool hub, so then you could award people badges. You could give people badges. And it's very cute. So they could probably help us with the taxonomy. They've probably already figured out a number of badges we could get started with. CHRIS: And of course, this is where my brain went initially to like, oh, what would the taxonomy be? But I think that's how this goes bad. And if we just keep it in the this is cute and fun, and what are all the possible merit badges, but they're all equal, and the points are made up anyway, and then it's just a fun thing, then I'm like, I'm super into this. Let's do that. Have you used a regular expression to parse HTML? Congratulations, you get a merit badge. Have you not used regular expressions to parse HTML? You get a different merit badge. [chuckles] STEPH: [laughs] I feel very positive that I could be chief of cute and fun. I could manage that department. CHRIS: Yes, that feels like definitely a role that you could really excel at. But shifting around ever so slightly, I did run into a fun bug this week. And it was a mystery tour of, I'm going to say, sadness and then eventual learning and understanding, and I think we've come to a better place. But I want to tell a story, take us on a quick tour of the adventure that I went through. So we recently saw a handful of exceptions come through in our exception monitoring service and then piped into Slack, where we see those around CSRF token expiry. So this occasionally happens in a Rails app. The CSRF token that was on the page gets rotated. And therefore, when someone...if they have an older version of the page open and they try and submit a form or something like that, then CSRF protection is going to kick in. And you do get some false negatives there or some cases where like, nope, this is actually a fine user, this is not hacking, this is nothing bad. It's just that that user had a tab open or something like that. I'll be honest; I want to understand better the timeline of expiry and how Rails expires those and whatnot. But it's one of those things; it's deep enough in Rails that I trust that they are doing a very reasonable thing. And I think the failures that we're seeing that's part of the game. And so, mostly, we wanted to add a nicer handling around that. So thankfully, Inertia actually has a really wonderful page in their docs about handling Cross-Site Request Forgery expiration token, this whole thing. This is a particular failure mode that your app might have. And so it's nice to be able to provide a nicer user experience. And so what we ended up doing is if we catch that exception, we have a rescue_from in our application controller that will instead of having this be a 500 and just a full, like, something went wrong error page, we instead respond in an Inertia-like way to basically show a flash message that says, "This page has expired. Please refresh the page to continue." And if the user just refreshes the page, then they will get a new CSRF token. And from there, everything is going to be fine. So it's not ideal. But it is, I think, both secure and now a nicer user experience. STEPH: Yeah, that sounds really nice. When they refresh the page, do they lose all that form data? I'm curious how painful of a flow that is for the user. CHRIS: Currently, yes. Inertia actually has a really nice feature for remembering form data. If you've ever been on GitHub and you're filling in a box, and then you go away to a different tab, and you come back, and it's still there, and you're happy about that, it's that sort of thing. So we could configure that. At this point, we don't have...most of our forms are pretty small. So this is not something that we opted to do proactive management around. But that is definitely something that we could add but not something that's default or anything like that. STEPH: Cool. Yeah, that makes sense. I was just curious because yeah, either small form doesn't really matter, or also, this may be just a small enough error that only a handful of people are experiencing it that it's also just not that big of a deal. CHRIS: Yes, this definitely should be an edge case. And we've also recently been working on functionality to log folks out after a period of inactivity, which would also, I think, obviate this in a different way. So all total, this shouldn't be a big deal. And this was basically a quick, little snippet of code that we thought we could just drop in, and everything would be great because it shouldn't happen much. But then I was testing out a different feature on staging, and everything I tried to do was popping up this little alert flash message that was like, "Hey, your page is expired." And I was like, that seems bad. And then I realized literally every action, any non-GET request, was getting this response that the CSRF token didn't match. And I was like, well, this seems bad. Luckily, it was only on staging and hadn't made it to production. But it had made it to staging, which meant it had gotten through CI, which was very concerning because we have a pretty robust set of feature specs at this point. We built up a bunch of fakes for all of the external data systems that we're interacting with. And we're really putting the app through its paces and trying to do so in a very production-like way. And so I was like, this is such a deep fundamental breakage. I don't know what's going on here. And so I started to investigate. And it turns out that in a recent commit, I had started using Axios, which is a little wrapper around the Fetch API. They may not actually use the Fetch API under the hood, but it allows you to have a nicer interface to make XHRs. And we implicitly had that in our package already by virtue of Inertia. Inertia uses it under the hood, but I wanted to make it explicit because now I was using it directly. So I figured that's cool. I will yarn add Axios, and then I will continue on with my day. And I worked on my feature and everything was great. And then I pushed it up into a pull request, and everything was great, and CI passed. And I got it onto staging, and everything was very sad. So then I started on the adventure of like, what is going on here? It turns out that somewhere between version 0.21.1 of Axios and 0.23.0, which there's a bunch of things about those version numbers that make me uncomfortable but here we are, somehow the behavior where you can configure the XSRF header name, which is what they're calling it on their side, the configuration stopped working. And so our override that says this is what our CSRF or XSRF token should be called when it's sent back up to the server in a header that was getting lost. And so they were falling back to their default name, Axios was. And, therefore, Rails was like, "There's no CSRF token here. So this is going to be a no for me. I'm going to reject all of the requests." So the fix was relatively easy to roll back and to pin the version of Axios to the previous version that we had been using. I didn't actually intend to upgrade it. I just intended to make it an explicit dependency. But by doing that, I accidentally upgraded it. I don't love that there was this pretty deep breakage in that. I haven't done the good work of trying to open an issue. I still want to scan through and see if there is an open issue or a conversation around this before I start making any noise. But I think if I don't find anything, this is the sort of thing that should be reported because I can't imagine I'm the only one running into this. Likewise, I was very sad that my test suite did not find this. Turns out in Rails, CSRF protection is just turned off in test mode, which may be overall makes sense. But for feature specs, in particular, I definitely want to have it. And so, it was nice that I was able to find the relevant configuration. And we introduced an RSpec configuration that says, "If it's a feature spec, save off the existing configuration and enable CSRF. And then after the spec, go back to whatever the previous was." So now all feature specs run with CSRF. And I did make sure to push up that as a singular change to CI, and CI was very unhappy with me. Many, many features-specs failed, which was good. That was what we were going for. They failed for the right reason because things were fundamentally broken. And then, I was able to update the package-lock or the package.json on the yarn lock, pin the version, fix everything. But man, there was this period of like, oh man, the app is broken in such a fundamental way. Users just can't do stuff anymore. They can view anything, but they couldn't change any data. And it just snuck through CI. And that feeling is the worst feeling. We had, at this point, built up a lot of trust in our test suite. It was really telling us when stuff was wrong, and if it was green, I felt very good merging. And suddenly, this just really shook me to my core on that front. STEPH: I love these journeys that you take us on. I mean, they're painful for you, and I am sorry to hear that. But I love these journeys that you take us on. [chuckles] CHRIS: I usually only take us on them when I've figured out the answer. And I'm like, all right, here's where we're at. It was rough for a little while, but now we are happy. And thankfully, the one configuration of saying, hey, Rails, also, please include this as part of our production like, configuration for test mode. So I feel better that moving forward, this breakage won't happen again. STEPH: We should add that as another merit badge for telling a bug story. All right, I'm taking off my hat of chief of fun and cuteness. So this may not be terribly relevant to all the things that you just shared. But I am curious where you mentioned that with Axios because you'd specified the name of the token, and then that overriding behavior is what then broke. And so then that's what led to this whole adventure that you went on. I'm curious, why did y'all customize the name of that token? CHRIS: A, this is a great question. B, I'm not super sure. C, I think the reason is because we were trying to align to Rails. So we have a little middleware on the Rails side that will serialize the CSRF token into a cookie. And then that cookie value gets read by Axios and sent back up as a header on the request. So this is the way that with Inertia CSRF just kind of works and is good. And it's different than Rails' normal. We put a hidden input into any form. And so Rails holistically knows about both sides of that, and everything works fine. But now I have to manually round trip the CSRF token. And Axio's default configuration is a header name X-XSRF-TOKEN, and we needed X-CSRF-TOKEN because that's what Rails is looking for. I probably could have configured it the other way on the Rails side. But one way or another, I had to get Rails and Axios to come to an agreement, to meet at a table, and to agree to collectively protect the app. And so I had to mediate that discussion, and that's what ended us here. STEPH: A meeting of the minds. [chuckles] Cool, cool, cool. Yeah, that makes sense. I was just curious because then that would have changed the whole journey. But yeah, that is super interesting. And I definitely resonate with the idea of when you've really invested in your test suite, and you trust it that then when it doesn't catch something that obviously breaks the application, then that feels like something worth prioritizing and digging into and then figuring out how to bring back that parity. I don't know that I've turned on enable CSRF for feature spec. So I'm also very interested in looking at that configuration and considering if I need that for any of my future client projects if that's something that I need to remember for the future because that's very niche but good to know about. CHRIS: I feel like this only really comes up if you're working in the...it's called the odd middle ground that Inertia ends up occupying. If you're in a traditional Rails app that is generating HTML server-side, forms are generated. They got the CSRF token inlined there in a hidden input. And then when you post that form, it's coming back up. The names automatically are going to match. You don't need to worry about it. And it's probably fine to not have it included in test mode. And if you're at the other end of the spectrum and you've got API interaction, and that's the way you're doing everything, then you have a different auth mechanism and cookies, and whatnot just don't apply in the same way. And so it won't really matter on that side but for a different reason. And it's only because we're in this interesting middle ground, which, again, I really love. And it's the thing that I love about Inertia. But this is a rare case where it's like, oh, we do have to bring the two sides to meet in the middle. And this is a case where, unfortunately, due to a very subtle breakage on a minor release of...a package that we're using silently broke so, yeah. But yeah, thankfully, everything is back to working. And again, we've been able to enhance the test suite in that little way that I feel confident again because this won't sneak in another time. We have coverage around this. We're good to go. So while I was very scared when this initially happened, I feel better now. I'm happy to go into the weekend feeling better about this. But that's my story. What's new in your world? STEPH: So I feel like I've been having one of those weeks where I have less code adventures. In fact, it's one of those days where I went to thoughtbot's daily sync...because we often have our client daily syncs, but then we still have a thoughtbot sync as well. And I went to the group, and I was like, I get to write code today. It's going to be a great day. All the other things I'm doing are also interesting, but I get particularly excited when I get some maker's time and get to write some code. So I feel like I've had less coding adventures recently and more hiring and process-related adventures. And specifically, I just completed the Plucky Manager Training, which is a program that's founded and led by Jen Dary, who was recently on thoughbot's podcast, The Giant Robots Smashing Into Other Giant Robots. I'll be sure to include a link in the show notes for anyone that's interested. CHRIS: I believe this was the third time she was on. It's at least the second, possibly the third. And all of them are great listens, just as an aside, so we should include links to all of them. STEPH: Yes, I think she's one of the rare guests that has been on the show three times. And I think I've only listened to the first couple minutes of that episode. But I think they talk about the fact that this is her third episode, which is really, really cool. And I'm still frankly synthesizing all the information and the ideas that I've collected from the course. But I do have a few quick takes that I'm interested in sharing with you. So the first one is my cohort...we were the Panda Cohort, so go, Pandas. And some of the things that we talked about were…, and I think that this may have been the first day. So it was three days, and it was three hours for those three days. And they're spread out over a couple of weeks, which is really nice because then you show up for those three hours of the class, but then you leave with some ideas and some things to experiment with. You get a week to then try out an experiment and then come back to class next time and talk about this is how it went; it went to wonderful, or it went terrible. And you get to share that with others and work through it. And in the first class, we talked about coaching versus managing, which I found just a helpful definition to review. So managing is more direct, and telling someone what to do while coaching is encouraging someone to determine their own path and find their own solution. And I find that as a team lead at thoughtbot, I'm very often more in that coaching space than I am in that managing space. I think it's frankly pretty rare that I actually need to put on a manager's hat. And I often feel like I'm wearing my coaching hat instead. And some of the other things we talked about one of them is what is work? Which is a fun question to ask. And Jen had an analogy for this speaking about imagine that you have a plastic Easter egg. So it's got two sides, and side one is all the skills and desires and things that you're fulfilled by. And side two is a company that needs those skills. And it's great when those line up and click together, like when you take a job or get a promotion. Have you ever played...do you know what I'm talking about? Those little plastic Easter eggs. Have you ever played with those as a kid? CHRIS: Yes, certainly. STEPH: [laughs] I realize I just launched into that analogy. [chuckles] And then Jen goes on to say that's totally normal for then those sides to unclick. And Jen continues to say that it's totally normal for them to unclick. So maybe the company changes direction, the company is acquired. You've fallen out of love with something that you do about your job, or you have kids, and that has changed the things that you are fulfilled by and what you're looking for. And that's not necessarily bad. So it can be like, hey, you are working on x now, and you're not fulfilled by that anymore. But then another company comes along and says, "Hey, we're working on this, and you are fulfilled by that." So then another click happens. And essentially, it's a nice analogy to represent someone's career path and the ways that we are going to shift and re-prioritize what we're interested in. But it's also a really nice way to help it feel less personal because both sides are allowed to change. The company can change. You, as an employee, can change. And then you can look for that next click that is going to match up with a company that meets your skills and things that help you feel fulfilled. One of the other topics that we talked about are hard conversations, which I love that we dug into this one because that's certainly one that I struggle with or...I mean, we all get that feeling if you have to confront someone if you have to have that uncomfortable discussion with someone. It is a very hard thing to do. And so we had some very honest conversations around what is a hard conversation? What does that represent? And essentially, they represent that there is stalled progress and something can be improved. So Jen likens a hard conversation to a tool. It's something that you can use to then help something move forward again if something feels stalled or if there's something that needs to change. And during those hard conversations, you may not get to the resolution that you're looking for. So you may be looking for a specific outcome. But you also have another person that needs time to respond and to take in everything that you have said and process that information. So when you have a hard conversation, you may actually only move forward an inch. So if you had a lofty goal of we're going to talk and then we're going to have this hard conversation, and we're going to get to this space...But instead, you actually just make incremental progress. Like, okay, at least this person is now aware of this concern. That might be your win for the hard conversation versus actually tackling; how are we going to address it? I just want them to be aware of this concern. And it's a very vulnerable conversation, and they often take time before you can get to that ideal resolution. But essentially, the idea is get in the game, start the conversation, and then have follow-up conversations for that hard conversation. And I really appreciated that framing because I often will think of hard conversations of oh, we have to have this hard conversation and get to this specific outcome. But if you shift the goal line to be like, no, I really just need to at least make this person aware of a concern, that makes it a lot more approachable. And then also probably yields more fruitful outcomes because that gives the other person time to think about what you've shared to also come to the table with their own ideas and then work together to then get to that ideal resolution. CHRIS: I like that framing a lot. I can definitely see the case where you, as someone who has recognized something that needs to change (perhaps you're a manager),lineup you've now thought about that a good bit; you've observed it, but the individual that you're bringing that to this may be novel. This may be a surprise for them. And so if you come into that interaction both about to share this information but then also trying to resolve it and trying to get to I need you to internalize it, and I need you to fundamentally change your behavior as a result of this conversation we're going to have, that's quite possibly not a realistic outcome. And if you're trying for that, it might inherently lead to just a bad outcome because that individual is not in a position to do that. But they are potentially ready to hear it. And so you can just achieve step one and then later have step two. So I like that a lot. STEPH: Yeah, in general, I found the course incredibly helpful, very insightful. It was also really nice to hear from other managers that are facing similar problems or perhaps novel problems and then getting to weigh in and help each other. So it's a wonderful course. I'll be sure to include a link in the show notes for anyone that is interested. And I'll probably come back with some more insights from the class because it's really...we just wrapped up. So I'm sure I still have some ideas that will percolate over time, and I want to come back and share those with the group. Mid-roll Ad And now a quick break to hear from today's sponsor, Scout APM. Scout APM is leading-edge application performance monitoring that's designed to help Rails developers quickly find and fix performance issues without having to deal with the headache or overhead of enterprise platform feature bloat. With a developer-centric UI and tracing logic that ties bottlenecks to source code, you can quickly pinpoint and resolve those performance abnormalities like N+1 queries, slow database queries, memory bloat, and much more. Scout's real-time alerting and weekly digest emails let you rest easy knowing Scout's on watch and resolving performance issues before your customers ever see them. Scout has also launched its new error monitoring feature add-on for Python applications. Now you can connect your error reporting and application monitoring data on one platform. See for yourself why developers call Scout their best friend and try our error monitoring and APM free for 14 days; no credit card needed. And as an added-on bonus for Bike Shed listeners, Scout will donate $5 to the open-source project of your choice when you deploy. Learn more at scoutapm.com/bikeshed. That's scoutapm.com/bikeshed. STEPH: Pivoting just a bit, we have a listener question that I'm excited to dive into. This question comes from the one and only, the Edward Loveall, fellow thoughtboter. And Edward wrote in, "How does the process of software development change at different team sizes? What's a process that breaks down soon after the team starts growing? What's a process that is resilient at all sizes? And by process, I mean anything that involves other people including organizing tasks, code review, deployment, or anything else that isn't you alone writing code in a vacuum." I'm really excited about this question because I think there's a lot here. And there's actually one part that I'm struggling with a bit, so I'm curious to see what you think, Chris, about it. But I'm going to start off with saying that I think there are a number of management processes that definitely break down as a team grows. But in the spirit of Edward's question, I'm going to focus more on the software development process and how those might need to change and what starts to break as your team grows. So starting off with processes that break after the team starts growing, this one, frankly, what really starts to break is not a process specifically, but it's the lack of process that really starts to become visible and painful. So, how do we track work? Before, maybe the product manager or someone would just send you a message and say, "Hey, can you work on this?" or "Hey, can you fix this thing?" And how does code need to be reviewed before being merged? Does it need to be reviewed? Are people just merging as they get stuff done? How are deploys performed? Oh, we have a super urgent production fix that needs to go out, and the only person that knows how to deploy is out sick today? Cool. That's the type of process that I think that really breaks down, or at least you start to notice when the team starts to grow. What are your thoughts? CHRIS: I definitely feel that first one very strongly. We're feeling it right now on the team, which is still very small. There are only three developers working on the project, and then we have a product manager. And each week, we're slowly iterating, and tweaking, and honing, and trying to introduce just enough process in terms of how we define the work to be done, communicate the status of it, all of that fun stuff. We started with Trello. And we just had a board with some columns, and then we had more columns, and then we got rid of a few of them. And then we recently added a Power-Up to the Trello board, which allows for epics. So there are cards which are epics which tie to sub cards. And I'm staring at it, and I'm like, how long until we're Jira? How long can I hold out here and not be Jira? But it does feel like we're slowly iterating towards a more useful process for this team rather than process for process' sake, which I feel like is a really useful distinction. There's also a question of like, what can be known or what can be adequately measured and whatnot versus what can't be? So we've talked many a time on the show about estimation and velocity and trying to track that and the pitfalls inherent with that. And so there's, in my mind, two different camps. There's the process we want to avoid. And again, to reference German Velasco's wonderful blog post, Say No To More Process. And I really feel like there is a tendency often when things go wrong to then try and paper over that with process. Oh, this team didn't use the design system. So we need to write ESLint rules to make sure you can't import from the directories that aren't the thing. And it's like, we can do that, and I've definitely done that. And I will do that again in the future. But I always have the lens of do we need this? Is it worth the trade-off, the cost, the overhead, the complexity that it's bringing in? But definitely, organizing and communicating tasks is one of the ones that becomes really difficult. The more people that are working on something, the more you need probably more than one person staying out in front of them and trying to define the next bit of work that needs to be done after that. Code review feels like it probably should stay similar, with the exception that I lose the ability to review all code at some point. Right now, I'm trying to review every single PR that goes through or close to it. At some point, I'm just going to have to give up on that. But for now, that's my goal. But fundamentally, code review, I think, will hopefully take the same shape. Deployment, similarly, like, I've talked about the merge queue thing. I want to get a little bit of process in there but not too much. There is definitely some necessity for change. But I definitely want to resist the urge to change everything and to just say, like, slowly over time; we're going to have to be a big Byzantine organization with lots of rules and standard operating procedures and all of that. I've heard anecdotally, and I don't know if this is true, so maybe someone out there on the internet can correct me if I'm wrong, but my understanding is that at Google, they're pretty tight in terms of what languages and frameworks can be used and what processes, and workflows, and build tools and all of that whereas Facebook, as a counterpoint, is relatively lax. Obviously, React is used very heavily on the core web application. But there's some flexibility in terms of different languages and frameworks and things for sub-projects or small individual teams having a little bit more autonomy. And I think that's a really interesting thing of are you one large, cohesive, organized company or do you try to act like a bunch of small disparate but roughly connected teams that share good ideas but can work independently? And that changes how I would think about this question. STEPH: I really like how you're describing the addition of process. It sounds like a just-in-time process. So as you're learning that something needs to be added, then that's when you look for answers. And then you sprinkle on a bit of process that everyone agrees that feels very helpful within also the right to review and see if that still makes sense for the team. There's one additional area where I think the lack of process really shines through in addition to the number of ways that you've mentioned is also onboarding. So if you have a very small team and you are onboarding, it's likely that...Chris, you can let me know if I'm wrong, but when someone's joining the team, there's probably a good chance that they get to pair with you at some point, or they even get welcomed by you to the team. And then, they get an overview of the product and the codebase. And there's probably this really nice session where they get to ask you questions, and then they have that onboarding session. Does that sound about right? CHRIS: Yes. But I would go so far as to say it's not just a day or a session, but it's probably a couple of days. So yes, and. STEPH: That's even better. And with some of the smaller teams that I've seen, that onboarding process is where they are pairing with that lead person on the team. And that's going well until suddenly that lead person can't pair with everybody. And nobody has really thought about how to streamline that onboarding or how to coach or teach someone else to be a really good onboarding pair. And I have strong feelings about this area because we often focus so much on hiring, but then we drop the ball when it comes to onboarding that new, wonderful colleague that we've worked so hard to recruit. And at the end of that day, someone's going to reach out to them and say, "Hey, how was your first day?" And it makes a big difference for that person's retention as to how those first couple of days ago. So I think onboarding is another really important part that when you're a smaller team, you probably don't need much process because you have more of that personable onboarding experience. But as the team grows, there needs to be more of a process to help other teammates join the team. CHRIS: It's interesting. I think I totally agree with you that over time, there is a necessity to be more intentional and to have a little bit more structure in the process. And I don't think you're saying this, but I just want to make sure we are saying the thing that I think we believe, which is that shouldn't replace the human that helps you onboard. Like, I still like the idea that everybody gets a pair for some amount of time when they start at a new company. And you're working together on a feature, or you're working together on bug fixes. You're shipping to production as soon as possible. But you're not doing that based on some guides in a wiki. You're doing that with another human that's helping you. There should also be guides, and a wiki, and documentation, and formalization as the organization grows but not in place of having another person that you get to talk to. STEPH: We're just going to send you a little yellow rubber duck and then with a little Post-It note that says, "Good luck [laughs] with your onboarding process." Definitely. I agree with everything you said. It does not replace that human element where there's someone that's helping you onboard. I just see that onboarding is one of those things that gets forgotten, or we often point someone to a README which I do think is great because then it is battle-testing our README. But then there still needs to be someone that is readily there to say, "Hey, how's it going? What are you struggling with? Can I pair with you?" There still has to be that human element that is helping guide you through the process. And I think smaller teams may forget that they actually need to assign somebody to you to make sure that you have someone that you know. Like, hey, this is who I can reach out to with all my questions. Because they're probably not going to be comfortable posting in the company channel at that point or a larger communication to say, "Hey, I'm stuck on something." CHRIS: There's one other area that comes to mind, or I guess it's more of an anecdote that I have heard, but it speaks back to GitHub's early, early days. And they were somewhat famous for being very flat in terms of the organization and very self-organized, and everybody's figuring it out, and you're working on the thing that's most important in your mind. And for a long time, this was a celebrated facet of the company and a thing that they talked about rather publicly. And then I think there was this collective recognition, and maybe they reached a tipping point where that just didn't work anymore. Or maybe it actually hadn't been working for a bit, and there was just the collective realization of that. But it was interesting to watch from the outside as GitHub added more formalization, more structure, more managers, and hierarchy, and career ladders, and things of that nature. And I think there's a way to do all of those things in a complicated, overloaded, heavy way. But I think a different version of it is...like, you were using the word coaching earlier. Having formal structures within your organization to encourage people on their career path, to help them grow, to have structure around that, I think is a really difficult thing to get right. But I think it is critical, and I think just not having it can't be the answer past a certain probably pretty small size. So that is an interesting one where I think you do need to introduce some process and formalization around how you think about the group of people and how they work together within your organization. STEPH: I agree. I think where some folks may see a lack of hierarchy; others feel a lack of support. And adding levels of management should really be focused on the outcome is that we're helping people feel supported. So even getting feedback as you're adding those different levels of management, like, hey, did we make your life better? Did we make your life worse? I think that's a great question for management to ask as they're exploring a less flat structure. CHRIS: So, Steph, I have a question for you now on a variant of this topic. In general, we seem to be fans of having a codebase. Probably a Rails app that's got a database behind it, and that's where you put the data. Everybody commits to that same repository. It's all kind of one collected thing. And often, organizations grow to a certain size, and they're like, this is untenable. We cannot have this many people working on this same codebase. So we shall do the logical thing, which is we will break it up into small pieces. And those pieces will communicate over HTTP, and it will be great because then our teams can be separate from each other and can manage their little piece of the world. What do you think about that? Is there truth there? Is it not true at all? What do you think? STEPH: All right, so your team is getting too big, and to the point that you feel like you need to split it out so then you can have small teams, and they can all work independently on different parts and services of the codebase. I don't love the idea. I'm trying to think through because I feel like there's a lot of nuance here. But I don't love the idea that that's the driving force as to why are we making the change? And that is often a question that comes to mind whenever we are making a big change, either architecture or process-related is like, what's driving this? And then how are we going to measure it? And if we are driving it just because we have a large team, let's talk more. Why are people blocked? Why can't people work together? What's preventing people from being able to contribute to the same codebase? Are people blocked for a long time because they're having to wait on someone else to complete that work? I have a lot of questions that I don't know if I can fully answer your question. But my instinct is to say let's not break up the architecture just because our team grew in size. CHRIS: Yeah, I think I definitely agree with that. There's probably a breaking point where it's just too many individuals, and there'll be too much contention. But I think resisting that or at least naming that as like, okay, that's what we're saying but is that really what's true? Or are we actually feeling that this system is so deeply coupled that there's no way to change some small piece of the code without impacting other parts of it? Like, is the CSS completely untenable because we're just using global class names, and it's leaking everywhere? Okay, do we need a different solution there? And then it's actually fine. We don't need to have different services that have their own different style sheets. We just need a different approach to CSS. That's a particularly easy one to go for because there's inherently a global namespace there. But the same thing is true in a lot of different contexts. So services are a way to break things apart and enforce those boundaries. But if inherently coupling is your problem, then you're just going to be coupled over HTTP, and I think it's going to be difficult. There's a wonderful blog post by Josh Clayton, which I think does a better job than I'm doing in this moment of highlighting some of the questions I would want to ask. The blog post is titled Services are Not a Silver Bullet. And so Josh goes through and enumerates a bunch of the different versions of the story that he's heard throughout the years of well, we need to go to services because x, because our test suite is slow because pull requests are constantly having merge conflicts and whatnot, because the code is very deeply coupled and any change here affects everything else. And a fix over here broke something over there. This is no good. And so he does a really good job of presenting alternatives or at least questions that you can ask to say, like, is this the problem, or is this a symptom? And we need to address the more underlying cause. And so I think there is a point where you just can't have 1,000 people trying to commit to the same Rails codebase. That feels like it's maybe too big. But it takes a while to get to 1,000 people. And there will be times where extracting a service makes sense or integrating with an external service that exists. Like, I've talked about Stripe before as my canonical like, yeah, it's actually deeply intertwined with the data model, but they're just dealing with such a distinct complexity set over there. And they have such expertise on that that I'm happy to accept the overhead of the fact that that service lives outside of my core application, and I need to deal with synchronizing state and all of that. I will take on that complexity, but it's not worth it for everything, and it's not a silver bullet. Again, to reference the name of Josh's blog post there, Services are Not a Silver Bullet. And so, coming back to Edward's original question, I would say that having a monolithic codebase works for a really long time, but there is probably a breaking point somewhere well along, but fight it for as long as you can. I think. STEPH: I really like how you touched on coupling because it really helps ask those questions to get to the heart of what are the pain points that you are feeling? And it is less of a decision that is based on people and process but more if you're going to split out a portion of your architecture. It is in response to an actual business need and a business value versus some other pain points that you're trying to fix. A particular example might be like maybe you have a portion of your application that really just needs to spend a lot of time crunching data. And it's really not as specific to your application; it's something that can happen on its own. And then it's beneficial to move that outside so it can scale and relate it to the work that it needs to perform versus keeping it in-house with the application. I do want to circle back to another question that Edward included which is what's a process that is resilient at all sizes? And the ones that really come to mind for me...and these are a bit amorphous intentionally because it will look different for each company. But three areas that are very resilient at all sizes, whether you are 1 to 2 employees versus you've got hundreds or thousands it's communication, testing, and accountability. So communication, where are we headed, and how do we know what we're working on? For testing, it's how do we test our changes? Do we write tests? Do we use QA? Do we have a staging environment? What does that look like? What's our parity between staging and production? And then how do we know what's in progress, and how do we know when it's done? Those are three core areas that, regardless of your team size,,I think are very crucial to the team success. What do you think? What are some of the processes that are resilient at all sizes? CHRIS: I actually really like the list that you just provided. That is a wonderful trifecta, and I think it will take you very far, so probably not much to add from me. But I guess on that note, should we wrap up? STEPH: Let's wrap up. CHRIS: The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. All: Byeeeeeeeeeee! Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Chad talks to Leadership Coach and Founder of Plucky, Jen Dary, about working with individuals and companies to create healthy dynamics at work. In fact, Plucky just released a new product that aids in doing just that! Manager Weeklies are notebooks designed to help leaders intentionally set up their weeks and track progress. It includes tips and tricks, including useful 1:1 tools. Each notebook is designed to last one quarter. Follow Jen Dary on Twitter (https://twitter.com/jenniferdary) or LinkedIn (https://www.linkedin.com/in/jen-dary-46b0367/) Plucky (https://www.beplucky.com/) Manager Weeklies info & order link (https://shop.beplucky.com/products/manager-weeklies-2-pack) Newsletter: beplucky.com/newsletter (https://beplucky.com/newsletter) Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: CHAD: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Chad Pytel. And with me today is Jen Dary, founder of Plucky. Jen, welcome back to the podcast. JEN: Thank you. My third time. Three time's a charm. I feel very lucky. CHAD: There aren't many people who have been on the podcast as guests three or more times. So you're in an ever-increasing select group of returning guests. JEN: Thank you. I feel like it's maybe because the Tokyo Olympics have just started, but I feel competitive and ready to take on this third session. CHAD: [laughs] So the last time you were on was October 28th, 2019 is when the episode came out. JEN: Millennia ago. CHAD: Not quite two years ago, but yeah, also a millennia ago. And that was Episode 342 so if people want to go back and take a listen to that. And then before that, you were on Episode 270, which I actually don't even know the date of. It was even longer. So welcome back. You are celebrating the eighth anniversary of Plucky. JEN: I know. I don't really think of it in these ways because I don't have an MBA, or I didn't come from a business background or anything. But definitely when I hit five years, I feel like my husband said something about that. He was like, "Honey, you should be really proud. Not a lot of businesses make it five years." And that was not really on my mind. But now that Plucky is eight, I feel like oh man, I'm just so happy to talk about how businesses evolve and how what you thought it was going to be in year one was different than year three, was different than year five, and of course, it's different than year eight. So we're eight years in, but nothing's the same, and everything's the same. I'm sure you've experienced that too. CHAD: It was actually the eighth year going into the ninth year mark that we at thoughtbot started to make big changes. And it was that idea of coming up on a decade. It started to feel like, wow, there's real momentum here. And instead of thinking about what the next year looks like, what does the next decade look like? And are we the kind of company that is going to last 20 years? And that put us in a different mindset. And I started to think about the impact we were having and the legacy that we would have. And was it big enough for the size of the company that we had? JEN: How old is thoughtbot right now? CHAD: We just celebrated our 18th anniversary. JEN: Oh my gosh. All right. Well, maybe at the very end, you can give me your best wisdom for the ninth year. [laughter] CHAD: Oh jeez. Okay. [chuckles] JEN: No presh, but tuck that in the back of your brain. CHAD: Yeah, get some sleep. That's my best advice. JEN: [laughs] Great. CHAD: That would be great. We can come back to that. JEN: Cool. CHAD: So obviously, it's been a big two years since we last talked. I'm sure a lot has progressed in Plucky. How have things changed? JEN: Well, what's funny is that the two years spread that we're talking about or 18 months or whatever it is, for the most part, overlaps with COVID so far. So by the end of 2019, things were cooking, and everything is good. And even, personally speaking, my youngest son would be entering kindergarten in the fall of 2020. Again, as a business owner, a mom, all those things I was sort of at the end of 2019 hot, so good. And then I was anticipating 2020 to be continued pretty much the same as is. Like, we would keep training managers. I would keep traveling. All that would get easier because the kids are getting bigger, then my kid would go to kindergarten. And I was also finishing a book about...I can't remember if we talked about this before, but I was really sick in 2016. I had a brain tumor diagnosis, and I'm okay now. It was benign. I had this memoir that was eh, I don't know, maybe two-thirds done. All that was the plan for 2020, Chad. And I'm sure this is shocking news to you, but none of it happened, including freaking kindergarten, obviously in person. So on the business side of things, I kept everything stable as best as I could. So coaching kept going because coaching has always been remote. We have some products, and we kept shipping those out as best we could. At the very beginning of COVID, when everybody thought it was this three, four-week hiatus from real life, I recorded a story every day. Because I was like, what can I do for all the world that's working? So I recorded a storytime for Plucky with my kids. And I put it out on social media so that working parents could have another 15 minutes of distraction for their kids. That's how cute I was back then. [laughter] After one month of that, I was like, I need somebody to read stories to my kids. Yikes. CHAD: Yeah. [laughs] JEN: So the big thing that changed was that our manager trainings in person obviously I had to cancel those. So I transitioned from in-person to virtual events, and that has continued. And as of this recording, end of July, I was thinking that our November event this year…it's the 20th cohort of So Now You're a Manager. I was going to have it in person. And just last week, I pulled the plug on that. And I was like, no, we're going to stay virtual a little bit longer because I don't know how to predict what the hell is coming. So again, that sort of stabilizing, right? Like, okay, well, now I know how to do the virtual. That will be the stable choice this year, which is weird to say, but true. CHAD: Yeah. So you just gave a great organic listing of the things that Plucky does, and a big part of that was that in-person So Now You're a Manager training, which, if people remember from the previous episodes, new managers at thoughtbot have attended over the years. It's a really great training for people who become managers. So what was transitioning that to remote like? Because you'd only ever done it in person before, right? JEN: Yeah, totally. The first 11 cohorts were in person, and then we got to 12, and that was supposed to happen in March in Atlanta. We canceled that, and it wasn't until June that we had the 12th, and that was the first virtual one. And to say that I needed to go through stages of grief is probably pretty accurate. [chuckles] My energy in person is so a thing, like a tool of mine and just pulling people together, and making safe space for conversations and all that jazz. So I was like, what the hell is that going to be like on Zoom? And meanwhile, remember I'm watching my first grader go through the shenanigans of Zoom for the end of that year. And I'm like, oh my God, how am I possibly going to get grown-ups on this and paying attention and not being distracted? So a couple of things, I will say number one is I definitely interviewed four or five people in the industry who are good at virtual events, and I tried to get their deepest wisdom about it. The second thing is that I made the cohorts smaller. So in person, we have around 20 to 22 max, and in virtual, we do 10 to 12 max. And so that got a lot smaller. Also, instead of being two days back to back, I broke it into three half days which is just a different ask. And I wasn't sure if people would bite at that. I tried to mimic it after how some people do an MBA on the side. So then they go to work, and they practice the stuff they're learning at the MBA. And so that has been my thought like, okay, you'll be with me basically for a month. We'll have three half days together, usually on a Friday. And then you're practicing in the meantime. So between the times I see you, you're improving your listening skills. You're coming back with anecdotes about hires or tough conversations or whatever. So I won't say that's like a silver lining, but it's just a different beast. And the first day I did it, I mean, I'm telling you, I was on the bathroom floor on my knees like, don't let the internet go out. CHAD: [laughs] JEN: I was so scared. I don't know why looking back. I'm in tech, but I'm not technical. It's my husband who helps me set up a monitor and whatnot. Oh God, I was so nervous. And I just thought, shit, this is the thing I can't problem-solve. If the internet goes out, I don't know what to do, but if someone's upset, I can help them. So it just brought all of my skills in a different environment. And now I feel pretty good about it. I don't know if you found this with your distributed company overall, but I have worked very hard to make sure that it's a blend, of course, this digital experience, but also I use the mail. I use snail mail a lot. So attendees get a packet before we begin. They get a gift at the end, a graduation gift. And yeah, I feel like I've learned a lot about how to have a hand-in-hand experience of digital as well as a physical object that they can touch to make that experience more than just a screen. CHAD: Yeah, I think that's important. How did changing the format, reducing the class size, what business ramifications were there for that? JEN: Well, it's way less money. [chuckles] CHAD: Right. Okay, sorry. JEN: No. Oh my God. I want to be very real about these things, especially for people starting their businesses. It's way less money. And also if you think about it, everybody had already bought tickets to Atlanta, and then they had already started buying tickets to...I can't remember what the next one was going to be, New York, I think. So for a lot of the year, everything was, I'll say, comped, but that's not really what's going on. All of a sudden, the amount of seats that I thought I was selling for the year got reduced in about half, and much of that were already pre-bought tickets. So, as a line item, that was way lower. I also think I got...man, I haven't really said this transparently to anybody before, but I'll say it here. I got really scared about what to charge. Do you charge the same thing virtually than you do in person? And so I lowered it, I would say for a year. I lowered it by a couple of hundred dollars for each ticket because I didn't know what the market wanted. And also, I didn't know, oh God, were businesses closing? Were people getting prof dev budgets? Everybody was frozen for a good while. So I'm lucky that now today I'm back up to the same price that it had been before, but it's not as much income per event. And the other thing I'll say which affects money…but again, I want to be transparent for other folks who think about or currently run businesses. One great thing to come out of some of the social unrest of last year is that we now have an equity scholarship for So Now You're a Manager. So in every cohort, be that virtually or in person, I always reserve a seat for someone who's coming from an underrepresented group, so people apply. And that is something that I very happily said I will eat the cost of that ticket because it's important to me to have different voices in the room. And that has been a total awesome thing this year. That just started in January of 2021, but that's something really great that came out of last year. CHAD: Yeah. What did you find that customers wanted, and did it change over time? Was there an appetite for it to be remote, or was there resistance to it? JEN: I think at first people were overwhelmed and didn't want it. That's why I held it from March until June until I thought people were ready. I can tell you categorically that I've had the lowest percentage of parents attend of all time because, let's be real, who wants another kind of obligation? Or also, parents during this time, especially with young children, were not in that growth space necessarily for work because there was so much to keep afloat. So other than the three half days, I also have this optional hour that I throw in just if people can come; there's this extra exercise that didn't fit in from the original curriculum. And I don't think I've had one parent, maybe one, come across all those cohorts that have been virtual to that. So the optional stuff I see parents opting out of. That said, I saw more folks who maybe either live alone or maybe have a roommate but who are pre-family or some people won't have families but someone who was socially like, "It was so hard and tiring last year." And that sort of swung back around towards the summer and end of summer. I saw much more interest there because I think people were really lonely. CHAD: Yeah. And I also think, at least for me personally and for thoughtbot, that was when the thinking definitely shifted that this wasn't going to be going away anytime soon. And so we came to terms with that and started to then make much more long-term plans and permanent changes. JEN: I think it was also in the...I want to say like early fall when Twitter announced they'd be remote. Like, they have an office, but they wouldn't oblige anyone to ever come back again. And whenever that decision was made, there were a couple of other companies...At that point, I was still living in the Bay Area, and there were a couple of other companies that made similar suggestions. And so again, to your point, there was a revisioning of what the next phase was like or at least what to expect. And so, I think people weren't holding out to go back to normal. It was like, what's the new normal? CHAD: Yeah. So when we first shut down offices and went remote, we were giving updates every two weeks, and then it changed to every month. And then it would be like, "There's really no change. We're going to give another update in April." And then April was, "We'll give another update in May." And when it came to June, we just said, "We're planning on being in this mode for at least the end of the year. Let's start all acting and make this sustainable." So that is when our thinking changed too. JEN: Did you feel like with your CEOness and business responsibility over there...what kept you grounded for all that thing? Because obviously every time you make that announcement or regardless of whether that's in person or just...I don't even know– retention or whatever it is. It feels like you're just building strategy on freaking quicksand. CHAD: It wasn't easy. You feel responsible for everybody's well-being, both financially and everything else. And so the lack of stability…you want to provide it in an unstable world. You want to say, "Well, at least you shouldn't have to worry about this. Let's provide…" but it was impossible to do. And I'm much more comfortable with uncertainty. I think there's a spectrum of comfortableness with uncertainty, and I'm pretty far on one end of it, and even I was struggling. Same thing with like I'm very much on the spectrum of not having to worry about anxiety or anything like that, and even I was feeling it. And so I was just like...at one point I said to I think it was Diana or whatever "If I'm feeling this, if I'm getting chest palpitations, [laughs] something's really wrong, and we really need to pay attention to how everybody else is feeling." JEN: Oh, yeah. I even saw that anxiety obviously with coaching clients. There are some clients that when budgets dried up, there was like an initial drop-off, I would say March, April. But then I feel very lucky that the pipeline was still very strong, and I had clients stay with me or join or whatever. You remember as well as anybody not only did we have this health crisis going on, which again we still do but my last class...So third of three of the cohort in May last year was a couple of days after George Floyd's murder. And the responsibility I felt too...like, when all these things were going on last summer, it was like, who freaking cares about anything? It's like these huge things. And you start to say nothing matters. There are only three things that matter in life. And then you kept sort of recycling the drain on that. So here I am going into teaching the third of three classes. And during the third class, I always teach concepts on how to hire, concepts on how to lay someone off and fire someone, which everyone's always very barfy and nervous about. And I try to bring us together and graduate us in what feels like a victorious moment. But that's three days after George Floyd's murder, and everyone is reeling and needing to process. And I remember thinking that morning, I don't know how this is going to go because I was fully willing to rip up the plan and do something different. But at the same time, there's also sometimes they want some structure. Folks want to just show up and take this class and be distracted from what's going on in the world. So we sort of talked about this a few minutes before we started recording but really, what has been fascinating and challenging about continuing to train managers over the last two years is that these very large things are going on in the background: George Floyd's murder, a lot of social unrest in Minneapolis, the election, COVID, all these things. And you can't just put that away and show up to manager training. It is freaking relevant because it is relevant for them. Of course, it's very meta, but all of my students are then going to go back and be responsible for 3, 5, 7 other people in their day-to-day work. So it was really wild, but again, stretching and a challenge that I met with a lot of intention. I don't know if I was always super successful at it, but I thought a lot about it. CHAD: Yeah, I think that was the shift that we saw on our team. And what I've heard from people is that enough is enough in several different categories of things. And like, we just can't keep on doing what we were doing before. It's not working, and it is unacceptable. People are angry too. So it's not just processing. It's anger and wanting to see action, wanting to take action. And yet, doing it in a world where we can't actually be together, I think, made it particularly challenging for some people and for managers to know how to meet their team members where they were. And people process things in different ways too, and people need different things. And at that point, we had hired people who had only ever been remote. So I think the connections that you have with people that you might've worked with in person you can lean on a lot in the beginning. But then you're working with someone or managing someone who you've never met in person. JEN: Yeah. It's a whole new ball game. And I think that the notion of community has gone through the wringer, not only in the worst, it's a rebirth almost. I think the notion of locally what's going on for you and then who can you see? Who can you have a barbecue with? All of those questions of like, who can I be with? Of course, the internet's great, but the internet has some major, major boundaries to it. And people see that at work, and they see that in training. CHAD: One of the things we're struggling with in that category now is there are people who live next to each other because we were historically in offices. And as it becomes more possible to get together with each other, and this is something that, as managers, we're trying to navigate, it actually has a huge potential for exclusion now that we have hired a bunch of people who are anywhere. If the teams that were in-person together but are now working remotely start getting in person again, even if it's just an outing at a park, who's not able to attend that, and how will they feel? And what expectations have we set with them? And then you have just sort of equity and inclusion issues around people we've hired in Brazil since we've gone remote. There's no way for them to come. JEN: Sure. CHAD: It's not fair. And navigating that as a team, I think we've been able to do that, but it hasn't been easy. JEN: I think sometimes the only way to see it is none of it will work. So if none of it will work, then cool. The bar's low. [laughter] Yeah, it's not going to be perfect. And all in person had its issues too. So then, if you just sort of bottom it out and say, cool, cool, cool, there's no one silver bullet answer here. So what that means is yes, as human beings, folks who are possibly able to meet up for coffee will resonate and glow and be psyched to be around some other people. So, how do we say "No," less often to that? Because that's great. That's really something to celebrate. And I'm sure if everybody was in that situation, they would try to take advantage of that too. But then to say, if you're not in that situation, here's another option. And then, every once in a while, we'll mix those options together and have like a rolling menu with it so that nothing gets too static and paralyzed and presumed. And it's in that flow state, which of course, is more fatiguing because you have decision fatigue, and you got to keep making decisions about it. But if you can just say, "Oh, well, we're going to decide that on a week to week basis or on a quarter to quarter." I probably have said this to you before in one of these other podcast conversations, but I just really think that life is a giant science experiment. So if that's true, then you can just say, "Hey, y'all, for Q3, we're going to try this. And at the end of Q3, we'll ask you how that went, and we'll either keep doing it, or we'll totally change it, or we'll increment it." Software people are really good at this because they know that not everything has to go from 2.0 to 3.0. You could go 2.1, 2.2, 2.3. There are incremental builders. So if you can leverage that metaphor even culturally or socially with the makeup of the team and the way you run things, I don't know; I kind of think that's the best you got. CHAD: Yeah. And I think we generally have the idea that we trust people and that we can provide the information. And people will generally use that information to make good decisions that are oriented towards fulfillment. So a really good example when it comes to managers is in an environment where if you're meeting in person with someone, one team member and you're their manager, and you're not meeting in person with another, that could influence negatively the other person's path to promotion or the relationship they have with you and just subtly bias you towards the person that you might be able to meet in person with. And so as a manager, making sure people know that, that that is a thing that can happen is a good way to manage that bias because I think generally, people don't want to let that happen, but they might not even realize it, so they can actively manage it. JEN: Well, it sounds like even in that thought, you are gently nudging people back towards intention and back towards just not sleepwalking through their work, that this is important for us, not only in the distance conversation here but also obviously for race, and for gender and for all kinds of different ways that humans are. We will never get it 100% right and yet intention, and taking a beat, and taking a breath before you move into conversations about promotions or whatever will help remind you hang on a second, remember there's invisible stuff inevitably going on based on who I am and where I came from. How do I make sure things are fair today? Or whatever the reminder needs to be. It sounds like that's...I don't know. It's good that you have that front of mind. CHAD: So that's one example of remote management. How much of before the pandemic were people who were coming and attending the workshops? Were they managing people remotely? And how much of your curriculum was specific to that, if any? JEN: My gut says maybe about a third were remote managers. They are definitely with bigger companies that I was seeing that. The small agencies based in Pittsburgh, you know, Austin, those places were pretty localized. But so what you get with a bigger company is also a bit more infrastructure that supports some of these cultural conversations. And we had it as part of the curriculum, but it wasn't very big, and maybe I would sort of be intentional. There are breakout groups and stuff like that. And I might think I'm going to pair these two together for their practice one-on-one because I know they're both remote managers. I am very intentional about a lot of the pairings and all that stuff, and so I would be thoughtful in that way. But now, on some level, in all these virtual workshops, everybody has an equal footing now. So everybody's kind of screwed, and everybody's also making it work. So that has been a very interesting thing to see. And I always laugh at this example, a woman who came early on, maybe like the eighth or ninth cohort, and she's a remote manager. And she would say, "Well, I don't have a water cooler. I don't have, like, I'm walking down the hall sensing somebody's upset or anything." But she would say, "This is going to sound weird, but I keep an eye on how fast they emoji something." So if you have a person who...You know this person in Slack. They're always on Slack, always so supportive, funny, have something to say, a little thumbs-up emoji, or whatever. But if one day they're at work for sure and they haven't said anything about something, she would learn to read the tea leaves like that and check-in. And I just thought that was so clever and very creative. And what she's alluding to is this level three listening that I teach, which is gut or instinct or intuition. And what she was tracking was basically a change in behavior. And that's pretty much what we're tracking when we're in the office too. There could be many reasons why somebody doesn't emoji something right away. Maybe your daughter just ran into the room. Maybe there's a doorbell. There are a million things. But at the same time, not to be too precious about it but to casually track that at least instinctively. She was doing a good job of meeting the moment as best she could. CHAD: Are there other ways in which what you've been doing has changed over the last year? What are managers concerned about or challenged by? JEN: Yeah. First of all, I always had name tags that allowed for pronouns. But this is now certainly part of the curriculum. When we start, I give some social norms and then some tech norms. And so I make the suggestion that in Zoom, after your name, you put your pronouns. And it's not a huge chunk because I really don't feel like I am the best to teach this, but I've added in a DEI component, diversity, equity, inclusion component. And we have some folks in the alumni community who are DEI consultants, so that's great. I always give them shout-outs and refer over if people are looking for that. I've noticed that people are...I'll say careful, but what I mean by careful is that they are aware of all of the stuff we're talking about, like race and social stuff. Depending on where your office was in the country, the election was sometimes really hard. I think about companies in Ohio or Pennsylvania or swing states where it was not obvious that everybody in the office was on the same page about that. And the way that that stuff comes up and is like this piece of baggage in the room that prevents literally like a website being made. We want to think no, that shouldn't enter. That's not relevant here. And yet people are careful about both trying to say, "Listen, bring who you are. You're accepted here." And also like, well, sometimes what you're suggesting you believe about the world is harmful. The whole Basecamp thing is a good example of that. And so I found the managers who come to my training to just be open to not only sharing their experiences with that but looking very much for some guidance on that from their peers and then from me. CHAD: That's sort of what I was saying about people felt like you needed to be changing the way that you were approaching things. It wasn't okay anymore for most people to say, "We shouldn't be having this conversation. It's not a work-related conversation." It affects people's work and their ability to work. It is a work issue. And you can't simply put everything aside. That's one angle of it, but we're not all equipped. We're not all educated. We're not all ready to be able to do that as managers. JEN: Totally. But with the amount of shit that we have had to handle for the last two years, short of somebody who's a social worker/priest, I don't know who was ready. I feel like a lot of what we're talking about is so resonant for me because all of this is so hard. And if you are alone doing hard things, it's impossible. But the reason that I run the manager trainings the way I do and the reason that I hold onto them after and I put them in a Slack community, they're now alumni of the program. And it's active; it depends on the day. But people have hard questions that they're wrestling with. People have jobs that they're promoting, that they're trying to get people to apply to. It's this active community that goes on afterwards. Because, honestly, Chad, I feel like a big input into me creating So You're Now a Manager and the community around it was my experience becoming a parent. I was one of the first ones of all my friends. I was the first one of my siblings, and my son was the first grandchild on both sides. And I was like, this is so lonely. All my friends are going out in Brooklyn for dinner. And I was 31. It's not like I was very young or anything, but that's New York. And so I had a moms' group. And man, that moms' group got me through those early days because we could all laugh at how hard it was. We could cry together. And when I looked at the transition that people go through from IC, individual contributor, to manager or some level of leadership, you get responsibility. You have to play the messenger sometimes, something you're not totally down with. You have sometimes competition with peers. You have to manage up sometimes. And then you have these people who come to you with requests: I want a new career path. I want more money. I want a different title. And the slog of that is very reminiscent, on some level, of parenting to me. So I thought, well, this is not going to be like, here's your book. Good luck being a manager, although books could be helpful. For me, it seemed like there was at least a certain template of a person in the world who could use community too. So I always say you'll be with me for two days or a month if it's virtual. But I can't possibly teach you everything you'll encounter. That said, we can get some critical skills under your belt. And then you can just continue to riff with this peer network. And that has been a very, I would say, unique thing about the manager training I run and something that is so fulfilling to me. I have a very tiny business. Those are, in weird ways, kind of my colleagues, the funny jokes they tell or those personalities. That was another thing that we had to let go of. In 2020, I was going to have the first reunion. CHAD: Oh yeah. We actually talked about that in the previous episode as an idea. JEN: Heartbreaking. Yeah, it was called Encore. Basically, it was a follow-up and open to anybody that has already taken SNYAM, So Now You're a Manager. I had people who pitched talks, and we had selected them. And yeah, we had to pull the plug on that. So my hope is that next year we can do that. And now we've got almost...actually; I think we just hit 300 people, so maybe 50 will come, I don't know. We'll see. But I like the idea of providing a space for these folks who were new managers when I knew them and when they came through me but have gained some skills themselves and could become thought leaders in this management space. And whenever the world is ready for it, I'm excited to put that together. CHAD: Yeah, that's awesome. That sense of community is one thing I've struggled with, to be honest. Because having done this for 18 years, there aren't many people who worked at the company that work there now anymore. [chuckles] We've grown too. So I no longer have the close personal relationship that I had with most people at the company before or close work relationships. And combined with as we've grown, it's harder...you have to be more of a leader. You have to put yourself aside. It's harder to always be a servant to others. And then I found that especially difficult last year. And it's part of why I needed to not be CEO anymore and to transition to the COO role. Because I couldn't be in a position where everyone was always looking to me continually to make...and as distributed as we are, one of our values is self-management. But continually always looking to me to be the one who always has an answer, who is the stable one, I needed a break from that. So it's been nice, the transition. JEN: I was going to say is it better? CHAD: [chuckles] So it's a little bit different than I expected. So what happened was we made that change. We made other changes, and that was all going well. And then, in February, the largest vaccine scheduling provider in the United States came to us and needed help scaling the infrastructure and all that stuff. JEN: Oh my God. That's exciting. CHAD: And so I, along with a crack team of other experienced thoughtboters, went and spent all of our time focused on that. It has pros and cons, which is right as I was transitioning into a new role; I completely got pulled away and started working full-time with that client for a very important cause, which is the reason why we did it and decided it was worth it. The silver lining is it put everyone else in a position where we went very quickly from Chad's no longer the CEO to Chad's not here right now. [chuckles] And that was unexpected. But I think that it had downsides, but it had upsides too in terms of really being in a position where people could come into their own, into their new roles and sort of a forcing function for some of the changes that we needed to make. JEN: You know, I'll give you major props on that, Chad. Because 18 years and especially, I think this about a lot of things, but especially business here, people get stuck. They really do. They get stuck, especially founders, CEOs. They don't know how to get out of something if they're tired. And there are not a lot of models for what that could look like. The biggest disservice someone could make to leading a company would be to not really be feeling it because that shit trickles down. And if you're tired or if it's not your thing anymore, really, the biggest gift you can give is to go get aligned somewhere else and then hand over the reins to what I keep thinking of as the next generation. I coach a lot of people, or I work with a lot of people who are in the middle, let's say, so they're not C-suite, and they're not newest managers, but they're sort of senior there. They're totally ready to go. I can't overstate that. [chuckles] Will they mess stuff up? Sure. So did you. Will they have questions? Absolutely. But the next generation of every company it's the most strategic thing that a CEO could do is to think, what happens if I'm not here? That allows you to take a freaking vacation, like take a month off. Or that allows you to meet such a huge civic call, which you're describing here, and step away. Or again, God forbid something happened, and you get very sick; it allows the company to be bigger than yourself. So I just commend you on even having the courage to step towards COO and then obviously also kind of redirect as needed this year. But I hope that if there are other CEOs listening or folks in the C-suite who are wiped, this is my gentle nudge to them to hand over the reins at some point. Because you'll get a paycheck, I'm sure you can figure that. CHAD: [chuckles] Being wiped was one small part of it. And I had Diana on who's the new CEO, and we talked about this. We had grown to a certain point. Also, to toot my own horn, I had done a really good job of building a team of managing directors who were really good at what they were doing. And I was no longer the best manager for them. I was no longer what they needed in order to continue to grow. I could do it, but I wasn't the best person for it. So that was the overriding reason to make the change, and being tired and needing to not always be the one that everyone was looking to was certainly a part of it. But yeah, it's been good. JEN: Yeah. I figured we would get there at some point, but we talked a little bit earlier about how I have this new product coming out in September. So the product is called Manager Weeklies, and it's basically...I got to figure out the exact noun for this. I guess this is the marketing moment. [chuckles] But it's basically a small notebook. The way I think of it is it helps you take a deep breath before your week starts. And so I'm not messing with your to-do lists. Everybody has different versions of that, Trello or wherever the heck you keep it. But before you start the week, it is so important to wonder where's my energy at? What's my perspective? What are the couple of priorities? What am I blocking? Just a couple of invitation questions there. And then the idea is that you then can do this on whatever, a Sunday night or Monday morning. And then the rest of the week has, I feel like I've said intention 50 times in this conversation but has intention in it. You can decline those three meetings because they're not the highest priority. You can make some space to actually do the work that comes out of the meetings that you're in. And what I have watched over the last maybe three years are my coaching clients who get themselves together at the beginning of the week who have some sort of practice about setting things up in a good way are the most successful. They get the promotions because they look like they know what they're doing because they do. So anyway, it's called Manager Weeklies. So it's a small notebook. Each notebook is for a quarter. And then, because I'm a coach, I also filled it with other good stuff. Like at the end, there are all kinds of prompts for ways to give praise to people on your team, ways to give feedback, ways to handle conflict, ways to say, "Yes, no, maybe." And then there's a Work Wheel tool at the very end. And so my hope is that people who just feel like they show up on a Monday already behind that they would find some help with that intention. And I feel like what you're saying is that self-awareness component that came through for you, Chad, to say, I'm not the best at this, and also, I'm a little fatigued and so, therefore, deep breath. Here's the strategy going forward. It wasn't reactive, but there was some thought behind it. And so we'll see this fall people get a chance to try that out. CHAD: That's awesome. I feel like it's getting back to your roots but also building on it. So for people who don't know, the Plucky Cards were actually the first way that I was introduced to you was someone showing me a pack of those cards. So, where can people find out more about that? JEN: The best way for people to find any information is just to subscribe to the newsletter. I send it once a month. It's usually a reflection on work, life, something going on there. So if you go to beplucky.com/newsletter, then you'll be first in the know. What's very funny, Chad, is I have a former coaching client who holds the record now. He was the first one to buy the first pack of cards. He was the first one to buy the second pack of cards. [laughs] And he was also the first one to do this Small Group ticket that I recently did as a little offshoot of Plucky. So anyway, in my mind, I always laugh, and I wonder, I wonder if he's going to grab the first pack of Manager Weeklies this fall. But you're right. They certainly plug and play with the cards very well where there's even space in the weekly template to say, what's the one-on-one topic for the week? So it could be a card that you pull, and you use, or it could just be something else going on in the world that you want to bring to all the one-on-ones. But I feel like there are a lot of things I'm not great at in the world, but the things I am good at are people. And then I listen to people over and over again through all of these experiences. And I try to hear what else do they need? What weird little thing can I invent that could help them with some of these things that they struggle with? And I'm also just really mindful of the fact that not everybody has the budget for coaching or for manager training. And I would love for Plucky to be a brand that even if you work for a nonprofit or if you don't have the money to pay for some of those more expensive things that you would have 35 bucks for a pack of cards or 20 bucks or whatever the pricing will be for the notebooks and that you can engage with my brand, even if you're not very wealthy. And I feel like as a person who works and serves an industry like tech, that is always really a priority for me to not only coach or work with the people with the most money. CHAD: Yeah. If I remember right, you designed the cards, right? JEN: Oh my God, I wish. No. CHAD: Oh, okay. JEN: For the first pack of cards I worked with, I don't know if you know him, Greg Storey. CHAD: Yeah. JEN: He's great. Greg Storey did my first deck of cards, and then he moved on, and he's doing other interesting things with his career. So I have a designer who helped me with the second deck of cards called the Manager Pack. So that's questions for managers of managers to bring to one-on-ones, and then the Manager Weeklies are coming out. I've been collaborating with a woman who runs a design little shop called YupGup in Delaware. So her name is Joni. So it is so wild, Chad. I wish that I had any design sense. But it's like, I make these things which look like a terrible PowerPoint. I'm like, here, then there will be a bullet. And then I give it to a designer like Joni at YupGup, and all of a sudden, she has a logo. And then she has some emojis and colors. And I'm like, this is how I felt when I was pregnant, and someone showed me a sonogram, and I was like, (gasps) there's a baby in there. CHAD: [laughs] JEN: This is how I felt when she showed me them, and it was so exciting. And I will never be good enough to even be talented at all to make these things myself. But I hold the idea, and then I find someone who wants to help me make that in the world. It's just magical. That is so fun for me. And so I just ordered them. Actually, I ordered 1,000 of them about three hours ago. And so they'll come in August, and I just know it will be very surreal when I open the box and look at them and think about how many people in the world and pens in the world will be used to set intention, to set up people's weeks and hopefully, make a softer and more fair and thoughtful place to work. CHAD: And one of the things I love about your business and products is that you know you're having an impact beyond that 1,000 notebooks that you put out in the world because each of those people manages 3, 4, 6, 7 people. And if you can make work better for those people, then you have a 7,000-person impact. JEN: Yeah. And it's funny you say that because I think that recently...I keep saying I'm about to go away for a month or just be out of work for a month as a break after this whole COVID time. Since starting Plucky eight years ago, I didn't really have a model. I am not a traditional business. And even though many people kept saying, "When are you going to hire? When are you going to build the team? When are you going to do all of that?" That is not the shape of Plucky medium-term or long-term. I'm not going to be a coach factory. I certainly could, but then I'd end up super burned out and not liking my job. And then I'd have a sad company, and it would be bad. So I don't want to do that. CHAD: And that's literally the opposite of Plucky. JEN: Right. I mean, in the name, right? So, where I have landed as a model is to look at what artists do. And you would never take an artist...I really like Lisa Congdon in Portland. She's a cool, cool artist. And I've heard her speak, and I like her a lot. And what would Lisa Congdon's team look like? She sure isn't hiring other artists to do the work that she's over-signed up for. You get Lisa. And so she has a shop, and then she has partnerships where she teaches at different universities. And as I move into the ninth year here, I'm thinking a lot about what's standing between me and Plucky's shape and what an artist like Lisa Congdon has going on? And honestly, fully transparently, I think it's that I need to own that Plucky is me. And it's so messy in marketing. Do you use the royal 'we'? We at Plucky? Who is we? And I think that there's some good growth in front of me this fall and next year to say, yeah, I'm Jen, and I run a company called Plucky. And I'm putting this stuff out in the world, and I hope to have ripple effects. And it won't be by hiring 100 people. It'll be just like you described, selling things to X people, and then those people's reports, those ripples will follow down. And I'm really grateful to have found myself in this place because I love coming to work every day. CHAD: Awesome. Well, even though you love coming to work every day, also enjoy your vacation. JEN: Oh my God. Thank you. CHAD: And your time off and your time to reflect. JEN: Yes, thank you so much. CHAD: You already mentioned the website, but again, mention that, and then are there other places that people can follow along or get in touch with you? JEN: Yes, sure. So the newsletter, like I said, is beplucky.com/newsletter. On Twitter, you can look at @BePlucky. I'm on LinkedIn, too, obviously for Plucky. And then I have basically a behind-the-scenes account on Instagram because it was too annoying...Like, what do you take pictures of, Chad, when you're a coach? You can't take pictures of confidential conversations. CHAD: [laughs] JEN: So Instagram, I was like, I don't know what to do with this anymore. So anyway, I just have a behind-the-scenes one over there, which is called bepluckster because somebody else had it. So yeah, so all those ways. And also, I just generally say that if you're a person listening to this podcast and you just wanted to say something to me or ask a question, you should always just email me. It's just hello@beplucky.com. I love just hearing from people. And I might not be able to send you a three-page essay back, but I really love just interacting. And if something moved you or made you think about something, whether that was something I said or Chad, you can always just shoot me a note and tell me what you're thinking. I am not precious about that. CHAD: Awesome. Likewise. So you can subscribe to the show and find notes for this episode at giantrobots.fm. If you have questions or comments, email us at hosts@giantrobots.fm. You can find me on Twitter @cpytel. This podcast is brought to you by thoughtbot and produced and edited by Mandy Moore. Thanks for listening. Thanks for joining us, Jen. JEN: Thank you. Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success. Special Guest: Jen Dary.

On today's episode, I'm talking to Jen Dary, a career coach for new managers.Jen is an entrepreneur and the founder of Plucky, a leadership coaching and consulting firm. Through her work with Plucky, Jen helps people move forward in their careers in new roles. While she never started out with plans to work in business, following her own interests led her to working first in non-profits and then to the human side of technology companies. She then took a huge risk to start her own firm, Plucky, to reach people on a broader scale. Now celebrating Plucky's eighth anniversary, Jen continues to listen and guide as she helps managers learn their new roles through her program So Now You're a Manager.We talk about:transitioning careers to find fulfilling workthe cancer diagnosis that deepened her appreciation for people doing their best worksetting up each week for successMy FREE and LIVE masterclass on how to Crush Your Imposter Syndrome so you can move forward in your career is back! Click here to save your seat in the live masterclass and let's starting building your career confidence!To get the latest tools to help you build your own career right now, check out these FREE resources at Madam Athlete:Negotiation: Grab your worksheet to prepare yourself for your next negotiation Goal-Setting Mini Course:  Get started in the FREE Goal-Setting mini-course today!Managing Perfectionism:  Download my 3 favorite exercises to fight off perfectionismBook Club:  Sign up here to join the book clubKeep an eye out for new content or let us know what you'd like to see next by following us on social:Instagram:  @theMadamAthleteFacebook:  @MadamAthleteTwitter:  @MadamAthlete

This episode originally played 23 Feb 2021. We'll be back in a few weeks with a new episode. In today's show, Kacie Lett Gordon deconstructs the notion of having it all in our current times — she's working through that for herself with a number of other women on her podcast Fuck it All (https://www.itallpodcast.com). We start out by talking about being a bit nervous about being on a podcast as a guest and a podcast as a host, external and internal roles, the difference between honesty and authenticity, and how different people get their energy in different ways (she gets hers with alone time while her husband gets it from being around people). We reach into many topics during this show, including how Kacie's mom was and is a role model for her, being a mother herself, how while she felt like she theoretically had it all she felt miserable (probably as a result of late-onset postpartum depression), the double standard of calling a woman bossy versus praising a man for the same behavior, good coffee in contrast to easy coffee, the importance of the mug, the power of curiosity, and, in her words, where part of the narrative of being a woman is "if you don't dislike yourself a little bit, then you're not humble." There's a ton of books that we talk about — non-fiction and fiction. You can find those in the show notes. We also talk about a mutual friend Jen Dary and Manager Training from Plucky (https://www.beplucky.com/pluckyevent_categories/manager-training/). Stay tuned after the outro music to hear Kacie wonder, Who am I? This episode was edited and mastered by Troy Lococo. Special Guest: Kacie Lett Gordon.

In today's show, Kacie Lett Gordon deconstructs the notion of having it all in our current times — she's working through that for herself with a number of other women on her podcast Fuck it All. We start out by talking about being a bit nervous about being on a podcast as a guest and a podcast as a host, external and internal roles, the difference between honesty and authenticity, and how different people get their energy in different ways (she gets hers with alone time while her husband gets it from being around people). We reach into many topics during this show, including how Kacie's mom was and is a role model for her, being a mother herself, how while she felt like she theoretically had it all she felt miserable (probably as a result of late-onset postpartum depression), the double standard of calling a woman bossy versus praising a man for the same behavior, good coffee in contrast to easy coffee, the importance of the mug, the power of curiosity, and, in her words, where part of the narrative of being a woman is "if you don't dislike yourself a little bit, then you're not humble." There's a ton of books that we talk about — non-fiction and fiction. You can find those in the show notes. We also talk about a mutual friend Jen Dary and her So Now You're a Manager program from Plucky. Stay tuned after the outro music to hear Kacie wonder, Who am I? This episode was edited and mastered by Troy Lococo. Special Guest: Kacie Lett Gordon.

Firing people is hard, especially when you have a small, close-knit team. But it's an absolutely essential part of running a successful business. Learning to let people go with grace and kindness is a skill that Jen Dary teaches people to do well. In this episode, Jen talks to Andi about the struggles of becoming a manager, leading with values, and how to fire people with kindness.

Deep breaths, y'all. What a time to be alive. Don't you wish you had a mentor or coach who you could vent to and process with? That's why we invited Jen Dary on to talk about what managers can be doing to help their teams through troubling times. We just love Jen Dary. We know you will, too. Be sure to check out her One-On-One packs (https://shop.beplucky.com/) and her workshops and training courses for new managers at BePlucky.com.

On this Businessology episode, Jason Blumer had the opportunity to talk with Jen Dary about what it looks like to coach clients through this economic disruption. Jen is the founder of Plucky, a leadership coaching and consulting firm based out of Berkley, CA. She shared with Jason her own personal transition and reframing her of goals through this season. As she has asked of herself and her clients “What is my COVID job right now?”, she has seen a new, more freeing frame of reference unfold.

For our full show notes: Visit our Episode Webpage This week, we're hearing from Jen Dary, Kate & Liz as they answer the question: Is there something that you’ve dreamed of doing for a long time? Why haven’t you done it? Listen to guests: Jen Dary from Episode 41Kate (Mom Deconstructed Co-Host)Liz (Your Other Mom Deconstructed Co-Host) MORE FROM OUR GUESTS: Jen Dary | Liz Sanicola | Kate Turza | Learn more about your ad choices. Visit megaphone.fm/adchoices

For our full show notes: Visit our Episode Webpage This week, we're hearing from Lisa Sugarman, Amanda Rowe, Alison Donaghey, Jen Dary, Carrie Sharpe, Heather Vickery & Katie Rössler as they answer the question: What do you want to teach your kids about living outside their comfort zones and trying new things? Listen to guests:  Lisa Sugarman from Episode 69Amanda Rowe from Episode 55Alison Donaghey from Episode 65Jen Dary from Episode 41Carrie Sharpe from Episode 07Heather Vickery from Episode 28Katie Rössler from Episode 49MORE FROM OUR GUESTS: Lisa Sugarman | Amanda Rowe | Alison Donaghey | Jen Dary | Carrie Sharpe | Heather Vickery | Katie Rössler | Learn more about your ad choices. Visit megaphone.fm/adchoices

For our full show notes: Visit our Episode Webpage This week, we're hearing from Katie Rössler, Amanda Rowe, Valerie Friedlander, Jen Dary, Stacey Porter and Heather Vickery as they answer the question: What limiting beliefs or thoughts do I need to release in order to become comfortable asking for help? Listen to guests: Katie Rössler from Episode 49Amanda Rowe from Episode 55Valerie Friedlander from Episode 22Jen Dary from Episode 41Stacey Porter from Episode 32Heather Vickery from Episode 28 MORE FROM OUR GUESTS: Katie Rössler| Amanda Rowe | Valerie Friedlander | Jen Dary | Stacey Porter | Heather Vickery | Learn more about your ad choices. Visit megaphone.fm/adchoices

This week we are deconstructing last week's episode with Jen Dary of Beplucky.com. If you haven't listened, be sure to download Episode 41, which is chock full of inspiring insights and positive perspectives despite facing an insane life challenge. Join us this week as we discuss our highs and lows, our words of the year and our hopes for the future. Listen as Liz and Kate discuss:High: February break bliss.Low: Imposing social norms on your children, is this stifling their creativity?Children being heartbroken by opinions of their peers.Books that we re-read over and over again.Our words for 2019: Trust & Explore.Superpowers we want our children to have.Power of sharing your story.EPISODE LINKS: Eat, Pray, Love By Elizabeth Gilbert Big Magic by Elizabeth Gilbert Sign up for our newsletter here. SPONSORS: Crate Joy Real Plans Patreon: This podcast is made possible by listeners, like you.  We believe that community is key to motherhood, we invite you to consider joining our Patreon community and supporting us with a monthly donation on our page: www.patreon.com/momdeconstructed.  If you would like to become one of our sponsors visit: www.momdeconstructed.com/advertisingand start the conversation! All our sponsor offers are available on our website.  To get all the discounts and perks go to www.momdeconstructed.com/sponsors MORE FROM JEN Jen’s Website Jen’s Merch Jen’s Upcoming 2019 So Now You’re a Manager Dates Follow Be Plucky on Twitter Follow Be Plucky on Facebook Follow Be Plucky on Instagram MORE FROM MOM DECONSTRUCTED: Support this podcast on Patreon. Leave a review on ITunes here. Sign up for our newsletter here. Follow Mom Deconstructed on Facebook. Follow Mom Deconstructed on Instagram. Follow Mom Deconstructed on Twitter. Learn more about your ad choices. Visit megaphone.fm/adchoices

This week we are talking with Jen Dary. Jen is a leadership coach and speaker; she travels across the US teaching workshops, including her popular course, So Now You’re a Manager, which trains new managers across the country for the complex work of herding humans. Jen lives in Berkeley, CA with her husband and two young sons. Listen as she shares her unique motherhood journey, what happened in her life to call on her peers for help, and how she hopes that her children take a page from her book and can talk to anyone regardless of status, race, or language barrier. Listen as Jen shares how she:Suffered from postpartum depression and how that led to her starting her business.Cherishes her friendships and community.Built her community after a move across the country (hint: she started it herself!).Publicly reached out for help when she was struggling.Plans on writing a memoir about her experience.Recognizes her experience has shaped her life and changed her priorities.Doesn’t let her experience define who she is.Loves the New Year and goal sets at the beginning of each year.Believes we all evolve, regardless of the weight of our “problems”.Incorporated the concept of Shabbat into her family’s monthly routine.Hopes to give her children a superpower.Has a strong relationship with her family, despite living far apart from one another.Finds spontaneity can help her stay present with her kids.Called up a friend’s mom to find out what her “secret” was to have her adult children want to have a close relationship with her. Quotables: “When in doubt, invite somebody over.  We are all waiting to be invited over to somebody’s house.” - Jen Dary “It’s extremely clarifying.  What are we even arguing over?” - Jen Dary “I had to give up any plans I had for his first year of life and let the family that flew in to help, let my husband help.” - Jen Dary “Don’t waste any time in your life being afraid.” - Jen Dary “There is so much we can’t control in life.  On some level, what you can control is your state of mind.” - Jen Dary “I find it really restorative to spend one on one time with one of my kids.” - Jen Dary   LINKS FROM SHOW: Preemie by Kasie Matthews Eat, Pray, Love by Elizabeth Gilbert Episode 32: Stacey Porter, A Story of Loss, and of Hope New Year’s Workbook: Susannah Conway MORE FROM JEN Jen’s Website Follow Jen on Twitter Follow Be Plucky on Twitter Follow Be Plucky on Facebook Follow Be Plucky on Instagram Learn more about your ad choices. Visit megaphone.fm/adchoices

Jen Dary is the founder of Plucky, a company that specializes in creating healthy dynamics at work through coaching, consulting, workshops, and education. On this episode of the Hustle she chats with Anthony about how to know if management is right for you, what challenges new and established leaders face every day, and strategies to help along the way. On this episode we discuss: What questions to ask before accepting a management role The most common challenges facing both high-level and new leaders Understanding how management might fit in your career path How to create and communicate vision to your team Dealing with creator grief: not making things anymore The role of trust in management relationships How to gauge and improve employee experience Giving yourself permission to experiment, learn, and find new tools Visit the Funsize website Subscribe to The Funsize Digest Read the article

This episode, I'm chatting to Jen Dary, a leadership coach, workshop organiser, writer and card-maker from California. Jen runs Plucky, a company focused on helping companies and their people create happier workplaces. We like that! We talk about the strange need for managers and leaders to spend time creating physical things, the challenges of moving into management and how much it can help to chat things over with someone who can't fire you. Jen is wicked fun, and a great guest. I hope you enjoy the chat as much as I did! Any thoughts, feedback or questions - just email me: hello@makegrow.co. You can also record a message in anchor if you want to be featured on a future episode. (I'm still working on sound quality - next episode won't sound like I'm in a bathroom or a record player, promise) --- Plucky: beplucky.com Jen on twitter: twitter.com/jenniferdary So Now You're A Manager: beplucky.com/manager --- Progression Pack: progressionpack.com Join the community: progressionpack.com/chat Me on twitter: twitter.com/jonnyburch

Covington talks to Jen Dary from altMBA20

Jen Dary is the founder of Plucky, an organization that works with companies and individuals to create healthy dynamics at work. She is a leadership coach and speaker; she travels across the US teaching workshops, including her popular course, So Now You’re a Manager, which trains new managers across the country for the complex work of herding humans. Jen lives in Berkeley, CA with her husband and two young sons. On today's episode we discuss one of the tricky challenges of being a first time manager - managing your former peers and friends. We also discuss Plucky Cards? What are those? Stay tuned to find out! Contact Links: https://www.beplucky.com https://www.beplucky.com/manager https://www.beplucky.com/shop twitter: @jenniferdary, @beplucky IG: @bepluckster Writing: >https://medium.com/@jenniferdary   Show Notes:   lluminature: Discover 180 Animals with your Magic Three Color Lens   Plucky Cards   Brene Brown Ted Talk: The Power of Vulnerability    Spaceman: An Astronaut's Unlikely Journey to Unlock the Secrets of the Universe   Podcast: How I Built This

Sherry talks with Jen Dary, who helps companies build better relationships among their co-workers through her company Plucky. They discuss Jen overcoming a brain tumor, the importance of play, and adult development. Want more content like this? Check out our book.   The post Episode 174: Jen Dary on Facing Work and Life with Pluckiness appeared first on ZenFounder.

Sherry talks with Jen Dary, who helps companies build better relationships among their co-workers through her company Plucky. They discuss Jen overcoming a brain tumor, the importance of play, and adult development. Want more content like this? Check out our book.

“What did you want to be when you were eight years old?” It's a powerful question that can open up all sorts of conversations and illuminate the way we work together and where we want to go with our career. But who feels comfortable asking this during a 1:1? We're managers, not Oprah—bosses with a big letter B. Plucky's Jen Dary has the solution. Drawing on four years of leadership coaching, she's created The Plucky 1:1 Starter Pack to help leaders and teams be more successful together. Listen in on her story, find out what she wanted to be as a kid and discover how she found her North Star.

"I have realized that it is taking these tough moments and these unbelievably unexpected things that happen to you - whether it is health related or job related or relationship related - and saying, I see that this is happening and I'm going to push off it as soon as I damn well can." Today Sarah sits down wth one of our Elevate Women speakers, Jen Dary of Plucky! Jen really is one of the coolest people we've ever met, and we can't wait for you to hear her story of building a business, taking risks, and how to take advantage of those huge, unexpected curveballs life throws your way. Spoiler alert: it's a brain tumor!

Launching the employee development movement: this week Paul and Rich talk to Jen Dary, the founder of Plucky, “a consulting firm that helps companies with their people.” They discuss the value of retention over hiring, how to reframe thinking about career paths, Jen’s “employee development” approach to human resources challenges for both people and companies, and a pivotal conversation while stuck in traffic on the Verrazano Bridge.

Jen Dary is many things. The entrepreneur behind Plucky, a company that helps businesses understand and improve themselves by working on their internal relationships. A wife. The mother of two young boys. A life-long people person. And on April 8 she became something else, a woman with a brain tumor. Listen in as Jen shares her journey with Carl and thanks the community for all of their love and support.