Welcome back to my channel.

I hope you were doing fantastic.

I hope you have a great start of the day.

And today I wanted to share with you guys the things that I learned from being a software engineer.

And you want to make sure that you know what you were getting, Incheon.

You want to make sure that you learn from my lessons to do that, Make sure you watch this video until the end and stay tuned.

You guys know that I'm a huge fan of online learning.

And if you guys have been following my journey, which should have been, you must know that I started coding.

I started learning how to code in 2013 all through online platforms.

I was trying to absorb as much information as was their online as possible.

And for you guys, I have an amazing platform that I would recommend.

Today's video is sponsored by educative educated provides courses for you to learn programming.

I actually have been wanting to learn machine learning for awhile and look, they haven't amazing machine learning courts for software engineers with 85 lessons and eight quizzes, most importantly 115 challenges I love the platform is super interactive because that you get to learn and absorb things that you're learning hands on.

So Educative has an amazing coded interview course that they just released.

It's called Rock in the Code and Interview.

What is incredible about this course is that it actually provides you, teaches you 15 underlying patterns to solve coded interview problems.

Educative also provides you to try the platform free.

And for the 1st 50 users, I'm offering a 20% discount.

Used the code Yuba L U B A at the check out to get this discount, and you guys should try out and check out educated.

Now let's talk about the things that I learned through my career as a software.

So I have started my software engineer and during the six years ago, and I have both Internet companies as a software engineer as well as worked as a software engineer full time, and I compressed four main learnings for you guys.

First and foremost, you should embrace the struggle.

You know, hooting.

It's hard.

It's not gonna be all flowers and roses, and you will just see a problem and you will understand it right away and you off thio implementation and be off to just completing it immediately.

I mean, of course, that might be the case, but especially if you're in a workplace.

You're constantly, constantly faced with new problems with new challenges, with new things that you need to learn.

So I name it.

Embrace the struggle because you really need to be okay with that fueling that you might actually be struggling from time to time.

There must be things that you haven't learned yet and, you know, technology In the field of technology, the field of programming.

It's constantly, constantly being and innovated upon.

It's constantly changing, and you constantly feel like you need to learn and learn, learn and this thing you haven't seen yet.

And that thing is when you and you know, there have been times when I was literally, like, bang my head on the wall in the struggle, but I couldn't figure something out.

But one thing that you really need to keep in mind is that persistence.

Hard worth consistency is the key, and if you embrace that mind set up, you know you might struggle.

It might be hard you're gonna be fine, because through your persistence, your hard work and consistency will figure it out.

Another thing that I learned in my software engineering career is that you really need to have that hacker problem solver mindset.

You know, one thing that I've realized when I became a software engineer after studying chemical engineering is that there is never a formula for how something can be done, of course, their best practices and their recommendations.

But, you know, in the traditional engineering industry, you can take, let's say, ah, formula off like second law thermodynamics, for example.

And you know exactly that you apply this formula and you expect a certain results.

You expect certain concepts to be applicable, where is in programming and software engineering.

I found that, really, To embrace the mentality off, you need to get down and really understand things to the core.

You know, dig in, dig in, dig in reverse engineering.

You don't necessarily have to have that formula that would tell you exactly why the thing happens and another thing inside.

You know, every company usually has its own way of doing things.

Its own systems potentially stolen internal tools that they built from scratch, and you probably have never seen them before.

And for that, you also need to have that d bugger problems over mindset.

Because in my briefing side, you again have never interacted with before.

You need to be able to get down to the core of how they're being implemented, how they're being are detected so that you can, you know, go on with solving the tasks and building systems that you really need to build and, you know, asking for help.

It's totally fun.

But if you ask for help all the time without really trying to dig yourself first, then you might just miss on the opportunity to really understand things deeply and to be able to solve problems moving forward.

Another thing that I learned in my career is a software engineer is that collaboration with others is absolute.

He you know, you might think that Oh, I'm just gonna, you know, be super anti social.

I'm just gonna sit in my corner and just, you know, code.

And like no one's gonna bug me.

No one's gonna bother me.

No, you need to be a team player.

You need to be a good collaborator Because a lot of the times, besides just you, you know, in a company just has just few coding and implementing and building stuff.

There is gonna be probably a designer.

There's gonna be a product manager.

There is gonna be a probably other engineer is working on it to you need to make sure that you have great communication.

You need to make sure that everyone's on the same page.

With respect to where you're at, you need to be able to brainstorm with other people and collaborated with them on how to best solve the problem.

And, of course and collaboration, having a huge ego is not a good thing.

You need to be humble.

Need Thio listen to other people because I know a lot of the times learn something from them.

And I personally have learned that as a software engineer, a lot of the times you will need change arrived with people, and you need to be a great collaborator for that.

Oh, and you guys don't forget to check out educative the link is gonna be in the description used my code Luba L E v A.

For 20% for the 1st 50 people at the checkout.

They have amazing courses on program in an amazing course on Cody and interviews.

So check it out unless but not least something that I honestly wish companies or universities or whatever forces you were taken to become a software engineer would teach is project management.

Something that I learned is that a lot of people are not that great of a project management as the reason behind it.

You know, project management is not rocket science.

It's because people are not really taught how to do project manage management, and they're not really recognizing it as a real skill and something that they need to take the time to learn.

Especially in a big company.

You would be given a project, and as I sat in the point before, you will be collaborating with all these people.

But at the same time, you might also have other teams in the company that you might be collaborating with.

Our team side are touching the same code base, the same features, and you really need thio stay in touch with them about what you were doing and what's going on.

So I think project management is extremely key, to be honest now in any profession, but in software engineering as well, you need to make sure that you communicate with the stakeholders.

You're identified, the risks you need to make sure that everyone's in the loop and everyone knows what's going on.

And that is something that is not very hard.

You just need to take the time to learn it.

It's extremely important.

And if you guys are becoming or are software engineers, take the time to a learned project management, just like main pillars of how project management is done and you'll be all set.

Yes, I recently read, This book is just called Project Management for the unofficial Project Manager.

Sure it is.

And I thought this book really just hit the nail on all the points that are important for Project management as the software engineer or as really anyone else who works in a collaborative environment.

Yeah, I would recommend to read that book, so, yeah, project management is something that I would definitely recommend you get on That is it.

Guys, I hope you enjoyed this video.

Don't forget a little like and subscribe to this channel.

I hope you are learning from all the things that I have learned from my journey as a software engineer.

And you will take these things into consideration and into account.

And I'm very confident you're gonna be incredible in this profession.

And Stuart just gonna be amazing.

Persistent, hard working and just the best.

You're the best.

Have a great rest of the day and I hope to see you next time.

Bye for now.