The We're in our final round, is that right?

We're in our final round, but I feel like the last round I asked multiple questions,

so I'm a little sweaty right now, So maybe we can keep it at that round maybe we can do like ring the bell there you didn't K. Oh me, but we can keep it this. That's debatable

That's okay, okay Mo. Are you sure because it's called five rounds. I have to deliver five rounds of

action. The fighter has to get off the stool and muster up the courage to just

show up and not get knocked out and that's that'll be a win. So, okay. I do have one. Let's do it.

Let's begin.

There's, there's, you've said it. I've heard other quote-unquote experts in their field say they just

success leaves clues, reverse engineer it and do it,

and you'll figure it out.

I think that's just such a wide brush stroke,

like, how does one actually reverse engineer

something effectively.

I feel like you do this so well because you'll take a concept,

then you'll break it down and you'll teach it whatever,

you gotta, but how does one do it effectively?

Are there like steps to it methodically?

How does that look like when you reverse engineer something?

Okay, when I hear the word effective, it also sounds a lot like efficient, right? Like you want to make as few missteps and it could be easy to sit there and watch somebody like me do it and say well that seems like the ideal way to do it.

But what we don't get to see is the many times in which I've struggled through trying to figure

it out, the pain, the frustration, and the reward for that pain and the practice of trying it

out many times in failing is efficiency.

...