Welcome to a special bonus featured episode from Compiler, a show made to simplify tech for tomorrow's IT leaders from our friends at Red Hat.

This episode is all about failure and how to approach it in healthy ways.

If there's anything guaranteed in coding, it's failing.

So I know you'll be able to relate to and hopefully learn from this episode about how to process failure effectively.

Take a listen. Hey, this is Kim.

I'm one of the producers for Compiler.

Before I bring in Brent and Angela, I wanted to talk to you about something a little personal.

It's about failure, specifically my biggest failure.

I've worked in digital media for a long time, so I decided to take a course in user experience or UX.

It was towards a certification, and one of the classes was introduction to Python.

Now, this class gave me quite a bit of trouble, and when I say that, I'm being pretty

generous because I didn't understand a single thing that was said to me.

I couldn't get the simplest commands to work.

I couldn't get anything to work. And ultimately, I fail the class. And I don't fail things.

Not often. Fast forward to now, I've been at Red Hat for, well, more than two years now.

It's full of smart people, people who do code every day, and I couldn't even get a Hello

World command to work. And while I'm good at my job, I always come back to that Python class.

How do I move forward from that shortcoming? How should I handle that type of failure? This is Compiler, an original

podcast from Red Hat. We're your host. I'm Angela Andrews.

And I'm Brent Seminoe.

We're here to break down questions from the tech industry, big, small, and sometimes strange.

Each episode, we get perspectives on where things are and where they're headed.

...