Bryan Hyland

And I started there because all the research that I had done

was that this is one of the hardest languages to self-teach and I like a challenge.

There you go.

If it's a hard language, then it's probably going to be somewhat useful in multiple scenarios.

So, you know, fast forward to Rust coming up and I being a security minded person, I thought, OK, so this may be replacing C++ and C at some point where everything works.

will be shifting over in one way or another and those languages may go the way of COBOL or you know something like that so

knowing all of the languages in the systems realm would be helpful as a job, right?

For job opportunities.

So I just started to teach myself and dive in and fight that borrow checker, man.

Yeah, actually, I made a rule for myself.

I am not allowed to use unsafe anywhere in any of my code unless I absolutely know that the other end of it is going to be safe.

Correct.

Yeah.

And honestly, I found when I was learning Rust that it was actually...

lot easier than I thought it was going to be and it may have been because at this point I had like eight years of experience and you know anything between C C++ Java the web technologies so I found it easier and

With the exception of my bad habits.

And once I got over those bad habits and I started to embrace the way that Rust does it, all of my code actually comes out nice.

It actually looks prettier to me.

Not just safer, but it actually looks more...

well thought out when when i go look at my old stuff i'm like i should probably just delete this from public view but i kind of keep that stuff up as a as a way to remind myself and others that you can grow so that makes a ton of sense yeah it's funny too because