TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Technology

    Retro Time // A Software Podcast

    The Retro Time Podcast is all about retrospectives. Join your hosts, Derek Seibert and Jeremy Miller, as they talk about software — from product design to software development to the soft skills you need to make it in the industry. Using their long careers to kick off the conversation, they’ll drop a few nuggets of wisdom each episode… 96.7% guaranteed.

    Advertise

    Copyright: © 2020 Retro Time. All Rights Reserved.

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    45. The Mindful Developer with Dagna Bieda Jan 06, 2022
    Show notes

    It’s a new year. We’re leaving 2021 in the dust, and we’re looking forward to 2022. We’re setting some personal goals, some career goals, and we’re trying to figure out how to balance life and work to avoid burnout.

    To kick the new year off right we’ve invited Dagna Bieda, from The Mindful Dev, on the show to talk about how to be more mindful about our career decisions. Dagna discusses taking a minute to think about where we’re going and to keep from running our career on autopilot or making important career decisions without putting too much thought into where it’s going to take you.

    Topics:
    • 02:50 – Na zdrowie!
    • 03:33 – Most of us are running our careers on autopilot.
    • 04:53 – We need to be more mindful about our career goals.
    • 05:42 – Is autopilot always bad?
    • 08:15 – How do we know when we’re burnt out?
    • 09:21 – Complacency in our career is a plateau.
    • 10:32 – Moving up requires pausing and thinking about where we’re going.
    • 12:24 – we need to rethink “Work-life balance”
    • 14:00 – Has WFH changed why we’re getting burnt out?
    • 15:02 – What is it we want vs what is it we’re expected to do?
    • 17:27 – Overworking is kind of a drug.
    • 25:14 – Nail down what will fulfill you.
    • 26:22 – What are signs of burnout or autopilot.
    • 28:10 – Reprogram how our brains handle work.
    • 33:26 – Our ancient ancestors focused on negativity to stay alive. We haven’t changed.
    • 34:22 – We’re just cavemen with smartphones.
    • 36:05 – The Texas Sharpshooter fallacy
    • 37:44 – It’s also our cultural upbringing.
    • 40:44 – We’re often communicating with assumptions that aren’t correct.
    • 41:36 – How do we avoid burnout?
    • 42:10 – Take ownership of your time.

    Helpful Links:
    • Find Dagna on LinkedIn
    • The Mindful Dev on YouTube
    • How Dagna works with her clients
    • themindfuldev.com

    About Dagna:
    Dagna is a Software Engineer turned Career Coach. Her clients have worked at big names like LinkedIn, Amazon, Google, Disney, as well as smaller businesses. She’s been coding for the past 10+ years. She’s been coaching for the past 2+ years, helping her clients advance in their careers and reach their full potential. Over the last two years, she’s seen a lot of her clients at, or near, burnout and running on autopilot. Today, Dagna is going to share some tips and warning signs to help you avoid burnout.

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Laury Ricquebourg on Unsplash

    The post 45. The Mindful Developer with Dagna Bieda appeared first on Retro Time.


    44. Feature (RED) Flags Dec 30, 2021
    Show notes

    Picture this: You’re asked to build a new feature quickly. Perhaps you’re expected to cut corners and ship a new feature quickly. You know doing it the right way will take longer than the time you’re given.

    It happens more often than we care to admit. What do you do? WHAT DO YOU DO?!

    Maybe there’s no right answer. It all seems to depend on the context. Some things that we can say for sure are to build a strong team culture, work closely with your team, understand where they’re coming from, and know as much about the software you’re building as you possibly can– the people, the processes, the politics, etc.

    Do these things and you’ll be pretty well equipped to weather any storm that may come your way.

    Topics:
    • 02:07 – We tend to focus on the newest, shiniest features
    • 02:28 – There is often pressure for us to push out the next features over fixes
    • 05:12 – We know there is a right way to build it, but we’re being pressured to rush.
    • 06:03 – Some features we know about in advance and others come up unexpectedly.
    • 07:31 – Can our direct supervisor help go to bat for us?
    • 08:36 – Should our MVP be the foundation for future features?
    • 09:35 – How can we work to influence other teams?
    • 10:04 – It’s all about the context of the situation
    • 10:22 – There should be non-negotiables that every team should discuss.
    • 11:11 – It’s hard to convince others with a feeling.
    • 12:03 – Do we have an opportunity to perform “a learning release” to prove the value?
    • 13:03 – What can we learn from Tom Greever? Can we move the burden of risks?
    • 14:31 – Who feels the pain when our predictions come true?
    • 15:53 – We have to prove ourselves for other teams to trust our opinions.
    • 16:54 – The entire team needs to collaborate and be on the same page.
    • 19:06 – We never know how “small” changes might have major impacts down the road.
    • 20:07 – How often do we have to strive for perfection over the “good enough”?
    • 22:05 – How do we agree on non-negotiable things?
    • 24:52 – Our team culture is a safety net when something goes wrong.
    • 29:59 – Who has the final say in any of this?
    • 31:38 – We are taught our culture by the way our leaders act.
    • 32:46 – How we handle this situation depends on the context.
    • 33:17 – We need to work on building empathy across our team.

    Helpful Links:
    • 02. The Coming Storm
    • 10. Interview: Tom Greever, Author of Articulating Design Decisions
    • Articulating Design Decisions
    • After Hours: “The Learning Release” by Ardi Karaj
    • 26. If you can’t convince ’em, rebrand!
    • 34. Not just team building, dream building with Brittany Summitt

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Dawid Małecki on Unsplash

    The post 44. Feature (RED) Flags appeared first on Retro Time.


    43. Manufacturing an estimate: Manufacturing vs Software Engineering Dec 09, 2021
    Show notes

    Are manufacturing and software engineering really all that different? What if there were more similarities than might seem on the surface?

    When we think about manufacturing, we often focus on the production: The assembly lines, the conveyor belts, the tools, and the safety equipment. But there’s a critical step that comes first. The design.

    Before anything can be mass produced, market research is conducted, digital designs are made, prototypes are produced, feedback is gathered.

    That’s not too dissimilar from software, is it?

    Now imagine you’re in the year 2364. Replicators can instantly manufacture anything you can imagine. Now manufacturing is just like software. ?#mindblown.

    Topics:
    • 00:44 – Derek and his dips
    • 02:40 – What is the manufacturing process like?
    • 03:20 – The people financing early software projects were already involved with big industrial projects.
    • 05:39 – All of our circumstances are different.
    • 06:33 – We always end up doing what we know.
    • 06:56 – What is different about software?
    • 08:44 – Pretty much all of software is similar to the design phase of manufacturing.
    • 09:56 – What’s different is how we deliver our products to people.
    • 11:19 – In software, we can change our products almost instantly.
    • 12:56 – How similar was early software development to manufacturing?
    • 14:25 – The internet changed everything.
    • 15:20 – How many people are still in charge that have been around since the days of disk drives and on-premise?
    • 17:34 – The medium has changed, but our brains didn’t all change at the same time.
    • 18:00 – Truly great software can be changed as quickly as possible. This is new.
    • 18:36 – what happens when we try to apply software principles to manufacturing?
    • 19:56 – How do we change the manufacturing mindset?
    • 22:37 – Understand every way your system can change.
    • 25:23 – As technology increases manufacturing becomes more like software.
    • 27:42 – Star Trek has already figured this out.
    • 28:17 – Because tachyons

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Remy Gieling on Unsplash

    The post 43. Manufacturing an estimate: Manufacturing vs Software Engineering appeared first on Retro Time.


    42. Avoid the Naughty List: It’s end-of-year review season! Dec 02, 2021
    Show notes

    There are a lot of things to look forward to at the end of the year: snow, holiday decorations, gift-giving, time off of work, and spending quality time with loved ones. What’s missing from this list? The dreaded end-of-year review!

    Let’s face it, not many of us look forward to our end-of-year reviews. There are probably a lot of things you’d rather be doing than having hard conversations with your supervisor or subordinates.

    But why are year-end reviews so difficult? Are we waiting until the end of the year to break the hard news that we didn’t hit our goals? Should we be setting concrete goals 12 months in advance in the first place? Are we measuring ourselves against the right KPIs? Is there a better way to do all of this? How do we set ourselves up for success?

    In this week’s episode, Derek and Jeremy discuss past experiences with end-of-year reviews and offer some advice on how to set yourself up to have a great review next year.

    Topics:
    • 01:37 – It’s End of Year Review Season!!
    • 03:30 – We’re often tied down to a priority we set 12 months ago.
    • 04:07 – If we’re caught off guard in reviews, it’s an indication we’re not communicating.
    • 04:52 – Going into reviews expecting anyone to complete all their goals is unrealistic.
    • 05:22 – Yearly reviews are a very waterfall approach to feedback.
    • 06:05 – We shouldn’t be waiting until December to talk about our priorities.
    • 06:18 – It’s often difficult for us to talk about a problem at the moment.
    • 06:47 – Are we keeping track of our work, checking in often, are we learning as we go?
    • 07:15 – What if our priorities change throughout the year as we learn new things?
    • 07:41 – We tend to fear not following through with what we said, even if things change.
    • 08:18 – This might be because of our company culture and incentives.
    • 09:31 – Do we have a culture of fear?
    • 09:55 – Toxic optimism is pervasive in most company cultures.
    • 10:59 – We should be judged on how we did our job and handled the challenges.
    • 13:41 – What if we’re judged by the principles by which our team works.
    • 14:59 – The larger the team the less control we have over our piece of the priorities.
    • 16:29 – If we’re not constantly checking in with our team and course correcting, how do we all end up aligned at the end of the year?
    • 17:07 – Write an insurance policy into next years priorities
    • 17:33 – What if all priorities are shared across the team?
    • 18:04 – Why do we feel like we need to have ownership over a large thing?
    • 20:53 – If we embrace new insights throughout the year, there shouldn’t be surprises at year-end.
    • 23:00 – Stop assuming things!
    • 25:04 – Set an expectation that when there is a problem your team communicates it with you ASAP.
    • 26:01 – Don’t simply promise deliverables, promise learnings so that you can deliver.

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    The post 42. Avoid the Naughty List: It’s end-of-year review season! appeared first on Retro Time.


    41. Level up your career via mentoring with Anand Safi Nov 18, 2021
    Show notes

    If you’re normal, the chances are good you’ve felt stuck at some point in your career. You may have been confused about a big decision at work or in life. You may have felt stuck at your current level without a clear path to move forward. You may have wanted insight into how to change concentrations, roles, or companies. Maybe all of this at once.

    Talking with someone who’s been through these same situations is a great way to get through it faster than you might if you stumbled through life on your own. But maybe you aren’t sure where to start.

    On the flip side, maybe you’ve gotten to a decent point and are looking to give back. Becoming a mentor is a rewarding way to give back, but it can also be enlightening and a learning experience for the mentor.

    This week, Derek and Jeremy talk with Anand Safi, a software engineering leader, mentor, and coach about how to find a great mentor, some tips and tricks on how to be a great mentor, some pitfalls to avoid, and how to spot a bad mentor/mentee relationship early.

    Topics:
    • 03:58 – What is mentoring?
    • 04:34 – what is coaching?
    • 06:32 – Mentoring is beneficial for both mentors and mentees
    • 07:17 – How does Pair Programming relate to mentoring?
    • 09:58 – What’s the difference between mentoring and coaching?
    • 14:07 – What to do when a mentor relationship isn’t working?
    • 18:09 – What’s the ideal dynamic between a mentor and mentee
    • 21:19 – Recurring vs on-off mentor sessions
    • 25:03 – find a mentor and stick with them
    • 26:26 – Sometimes we just need to talk through a problem
    • 30:51 – Keep an eye out for your team and ask if they need help.
    • 31:29 – What’s the culture in your office?
    • 33:19 – How to tell when a mentor relationship is not working
    • 36:43 – As a mentor, know when you’re not going to give the mentee what they want
    How do we know if we’ve found the wrong mentor?
    • 38:33 – 01 – Does your mentor genuinely care? Are they distracted or multi-tasking?
    • 39:50 – 02 – Are they constantly canceling or rescheduling?
    • 40:50 – 03 – Are they not giving you clear tasks or goals?
    Tips for being a great m
    • 42:41 – 01 – Practice to get internal clarity
    • 43:14 – 02 – Understand what you need help with
    • 43:41 – 03 – Have realistic outcome expectations
    • 45:18 – 04 – Look at average career histories to set expectations

    Helpful Links:
    • Find Anand on LinkedIn
    • linktr.ee/anandsafi
    • Find Anand on ADP List
    • Black Valley

    About Anand
    Anand is a Senior Engineering Leader for Mark43 – a public safety SaaS company. Over the past decade, Anand has progressed from starting as an aspiring engineer to becoming an engineering leader.
    Anand is also a Startup Advisor, Volunteer Board Member, and an established mentor outside of his role. He loves reading about engineering culture, team dynamics, and new advancements in tech.

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Adrià Crehuet Cano on Unsplash

    The post 41. Level up your career via mentoring with Anand Safi appeared first on Retro Time.


    40. Content Governance: This ain’t no democracy! with Chris Willis Nov 09, 2021
    Show notes

    Aside from you, your company’s most valuable asset is its brand. The brand is the thing that your customers think about when they think about your company’s products or services. The customer experience is a direct reflection of this sentiment. Often, the tools we build every day are the direct interface between our customers and our company’s brand.

    However, too often, the content that ends up in our software is inconsistent and sometimes total crap. We don’t often think about the correct error message copy when writing user stories. Or how the tone and voice of our help documentation will affect how our company’s brand will be perceived by the end-users. But the fact is, it matters. It matters a lot more than we might expect.

    This week, we chat with Chris Willis, content governance expert and CMO at Acrolinx. Acrolinx has built its business around powering content governance with AI to help its customers generate the perfect copy no matter who is writing it or what it’s for.

    But what can you do if you don’t have access to software to help manage how your teams write content? Chris shares some tips and advice on how we might b able to manage this important monumental task.

    Topics:
    • 02:50 – What is content governance?
    • 04:44 – The copy in your software relates directly to the brand and the user experience
    • 05:54 – How do we quantify “good copy”
    • 06:33 – What is the level of governance that allows us to be self-sufficient?
    • 07:51 – We’re moving towards a digital-first consumer relationship
    • 08:24 – Customer experience (CX) goes way beyond just software and websites
    • 08:52 – There are tons of touchpoints that need to be aligned as one voice
    • 10:55 – How do we turn brand into actionable and executable guidelines
    • 14:51 – Content that comes through the governance process drives business results
    • 22:04 – How do we manage all of this without AI?
    • 22:58 – If we’re active we look at the things that are incorrect about the copy
    • 25:26 – It often comes down to the culture of the organization
    • 26:23 – Create microcopy ahead of the software production process
    • 26:58 – If we don’t define guidance ahead of time people will write whatever they want
    • 27:55 – Can we tap into our team’s OCD? 28:19 – Separate art from the brand
    • 29:08 – We didn’t hire software engineers to write copy. It’s not their job.
    • 31:29 – Content guidelines can’t stay on a whiteboard. They need to be shared.
    • 35:17 – We need to educate our team on why
    • 37:57 – Proactive vs retroactive governance
    • 39:58 – Our content may change based on context

    Helpful Links:
    • Acrolinx
    • Content grows up. The Active Content Governance playbook
    • “Content is King” – Essay by Bill Gates 1996

    About Chris
    Chris Willis is Acrolinx’s Chief Marketing and Pipeline Officer, responsible for all aspects of the company’s marketing strategy. He brings over 20 years of experience growing companies in thetechnology sector. Before joining Acrolinx, Willis held leadership roles in marketing, creative, technical, and business development at companies including Perfecto, Pyxis Mobile, KPMG-CT, ModelGolf, and Cambridge Technology Group. In his spare time, Chris enjoys networking with other CMOsand keeps active by coaching CrossFit at Powdermill CrossFit in Acton, Massachusetts.

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Aditya Joshi on Unsplash

    The post 40. Content Governance: This ain’t no democracy! with Chris Willis appeared first on Retro Time.


    39. Let Change Be a Catalyst For Change Oct 28, 2021
    Show notes

    Change usually comes when we least expect it. Sometimes it can be for the better, but often it’s disruptive, unsettling, or just plain terrifying. Even though we can’t always control the change that is happening around us, how we react to it is something we have full control over.

    When change comes it’s important to take a step back, reflect on what’s really going on, and see how we might be able to benefit. Perhaps a coworker leaving will allow for space for your work to stand out more. Or maybe getting laid off could be a blessing in disguise.

    This week, Derek and Jeremy discuss change in the workplace and how to take a potentially bad situation and show it who’s boss.

    Topics:
    • 05:03 – Losing a close coworker can lead to real grief
    • 07:24 – Take a step back to reassess everything. What can you control?
    • 08:07 – We build close relationships with our coworkers. It’s traumatic when they quit
    • 09:10 – What is the silver lining in this change? Can this end up working out for you?
    • 10:24 – The way we handle the change can depend on the type of change
    • 11:08 – Learn to navigate a VUCA environment
    • 11:19 – Step outside the situation. Take a look “from the balcony”
    • 11:34 – Understand what you can control. Focus on that
    • 12:09 – Are you willing to take advantage of the opportunities?
    • 13:24 – Ask for what you want
    • 14:04 – We’re really at work to ensure we provide for ourselves and our families
    • 15:53 – Remember you are not your job title
    • 20:30 – Use change to inspire you to just do it
    • 21:28 – Make change a catalyst for you to change yourself
    • 23:14 – Embrace the life change Use a life-changing event to explore other interests
    • 25:43 – There are good changes and bad changes
    • 27:21 – There may be an expected benefit to a bad change
    • 28:29 – Whatever you do, don’t turn into the complainer
    • 32:57 – If you can’t affect change, maybe it’s time to get out

    Helpful Links:
    • What VUCA Really Means for You

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Annie Spratt on Unsplash

    The post 39. Let Change Be a Catalyst For Change appeared first on Retro Time.


    Get Hired: The Three-Legged Stool with Aimee Miller Oct 08, 2021
    Show notes

    Once you get the official offer letter, the fun is just beginning.

    There’s a good chance you’ve learned the hard skills, things like color theory, mapping techniques, best practices for writing code, etc. But there’s a good chance your boot camp, or even your traditional four-year program didn’t teach you about how to really excel in your career– how to be a great team player.

    This week, Aimee Miller joins the show to close out the Get Hired series where she’ll offer some insights into how UX designers and software engineers can work with their counterparts on the product team to build truly great software.

    Topics:
    • 02:59 – Communication comes first
    • 06:29 – Keep an eye out for when other people aren’t expressing themselves
    • 07:00 – Product Managers are part of your team. Not enemies
    • 07:58 – The three-legged stool
    • 08:40 – UXers need to have more empathy for their own team
    • 09:40 – Communication isn’t just one way
    • 10:39 – How do we get developers more involved upfront?
    • 11:46 – Trust is the foundation
    • 12:23 – Collaboration early saves meetings later
    • 13:20 – Product managers need expert opinions
    • 17:50 – We’re all just trying to solve problems
    • 19:29 – We often run on assumptions. Great product managers push back on those assumptions
    • 20:59 – Make it a part of team culture that you succeed or fail together.
    • 22:07 – Continue to learn what your team does and how you can support them
    • 26:28 – Never start developing something without the PM knowing.
    • 28:12 – We need to build trust and a partnership with our team

    Helpful Links:
    • The Role of Design in Business Strategy
    • Britney Spears Is Finally Free From Her Father’s Control After More Than 13 Years

    About Aimee
    With over 15 years of professional experience, in roles ranging from Graphic Designer to Product Manager, Aimee has acquired a versatile skill set. Her focus over the past 13 years has been Project and Product Management, where she has managed teams varying in size from 1-30+ team members on software applications, custom content management systems, and digital advertising projects.

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode Thumbnail by Chayene Rafaela on Unsplash

    The post Get Hired: The Three-Legged Stool with Aimee Miller appeared first on Retro Time.


    37. Is software a loser’s game? Sep 23, 2021
    Show notes

    A recent blog post by Tyler Hawkins highlighted how software is a loser’s game. The blog discusses the differences between a winner’s game and a loser’s game where the main difference is how the game is won. Professionals play winner’s games. Amateurs play loser’s games.

    In a winner’s game, the winner wins the game because of their skill. In a loser’s game, the winner wins not because of their skill, but because the loser had more errors. In a loser’s game, the winner simply had fewer errors than the loser.

    If software is a loser’s game, what can we learn from this idea? If losers lose the loser’s game because they had more unforced errors, the good news is that to win at the loser’s game we simply need to ensure we don’t make the same errors over and over again.

    Topics:
    • 03:31 – What is a loser’s game?
    • 04:12 – In a loser’s game you lose the game for yourself
    • 05:53 – In a loser’s game you lose the game for yourself
    • 07:21 – Often these are debatable things
    • 08:01 – Imagine if doctors were like software engineers
    • 08:58 – There are no official professional standards that everyone is held to
    • 10:28 – Standards bodies for software have gaps in where they have standards
    • 11:29 – Most of us have different standards
    • 13:04 – Continuously learn and change your ideas based on the context
    • 14:19 – Software is different from the other profession in that every app is different
    • 14:51 – What’s the difference between the expert and an amateur
    • 15:56 – These errors aren’t necessarily bad if we learn from them
    • 17:26 – Are certifications the answer?
    • 19:45 – The more we learn the more we fall into the hubris trap
    • 22:25 – We think we have the answers so we don’t evaluate all of our options
    • 23:13 – There are strategic and tactical unforced errors
    • 24:48 – Unforced errors in software often have cascading effects
    • 28:25 – Constancy, rigor, and restraint are what’s missing
    • 32:47 – The other end of the rigor is accountability
    • 34:14 – Keep receipts along the way
    • 37:10 – Maybe our team culture is to blame
    • 39:12 – Not improving team culture is an unforced error by the leadership team

    Helpful Links:
    • Software Engineering is a Loser’s Game
    • Accelerate: The Science of Lean Software and DevOps
    • tylerhawkins.info
    • The Loser’s Game by Charles Ellis
    • Niels Bohr Quote

    —–

    Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.

    If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.

    • Check out our website
    • Follow us on twitter
    • Find us on Facebook
    • Subscribe on Google Podcasts
    • Subscribe on Apple Podcasts
    • Subscribe on Spotify
    • Subscribe on Stitcher

    Episode thumbnail by Marianna Smiley on Unsplash

    The post 37. Is software a loser’s game? appeared first on Retro Time.


    Review Jam: Culture is the Key, Baby #FreeBritney Sep 21, 2021
    Show notes

    Like what you’re hearing?

    You’re in luck. There are more five-star review tunes to listen to.

    Really really like what you’re hearing?

    You could have a song of your own written by the one and only Derek Seibert. All you need to do is follow these simple steps:

    • Write a five-star review on Apple Podcasts or wherever you’re able to leave reviews.
    • Take a screenshot and email it to us at hello@retrotimepodcast.com.
    • Tell all your friends how much you love Retro Time (don’t worry, we trust you).
    • Roll down your windows and rock out to your very own song.

    The post Review Jam: Culture is the Key, Baby #FreeBritney appeared first on Retro Time.


    Previous 1 4 5 6 7 8 11 Next

    Related Podcasts

    Reply All

    1

    Reply All Games & Hobbies
    Inside VR & AR

    2

    Inside VR & AR Gadgets
    Note to Self

    3

    Note to Self News
    BrainStuff

    4

    BrainStuff Natural Sciences
    This Week in Tech (Audio)

    5

    This Week in Tech (Audio) News
    Hands-On Tech (Audio)

    6

    Hands-On Tech (Audio) Technology
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights