So if you're interested, please stay tuned.

First of all, the habits that I'm gonna list here apply to being a successful software engineer, not just a coder.

Software engineering is way beyond just coded, but that is a topic for a whole new video.

Let's get started.

When I first started working in the field, I had an extreme urge to start coded right when I was given a project of problem in future to implement because I felt that if I'm not coding, I'm just not being productive.

But the reality is that most likely the software you're gonna be built in is not gonna be built fully by you from scratch.

You're most likely going to be working on something that needs to fit in into the existent architecture.

Er and what successful software engineers do is that the first fully understand the scope of the problem and on Lee, Then once you fully understand what exactly you're sold and only then you should start coating.

This brings us to point to successful software Engineers are really good at documentation.

Most likely, you're not gonna be the only one working on the project.

There might be other engineers or designers, or did a scientist or product managers involved, and you need to make sure that whatever is in your head gets documented and then clearly communicated for others.

A successful software engineer will make sure to documents every stage off his or her thinking off how they will approach the problem.

What the solution off the problem is, what are the potential roadblocks to the solution of the problem?

And they will communicate this to all the stakeholders and parties involved in this project.

They will do that so that everyone is on the same page, and they will also do about to get feedback from everyone.

Most likely, you might have overlooked something and asking for feedback on being receptive to that.

Feedback from everyone else is super important.

The easiest way to get that feedback is to get everyone on the same page document everything for everyone and that share successful habit number three successful software engineers, right readable code, and they do so because they understand that they will probably not be the only person interacted with whatever they wrote.

Or maybe after they wrote it, there's gonna be someone else maintain it.

So they keep in mind the fact that someone will have to comment on.

Look at this thing that they wrote that they have never seen before and understand it.

Most importantly, your solution.

Your code must be readable because someone else my comment and want to understand it.

Successful Habit Number four is being good at cross functional work.

As a software engineer, you most likely will work with other functions, like Designer is so product managers or data scientists or people in operations you name it.

A successful software engineer empathizes with the other function that they work with and almost put themselves in that person's shoes so that they can effectively communicate with them.

They can delivered to them the exact information that they need.

So if I'm working with a designer, I will try to explain to them what exactly I'm building from like the design perspective.

If I'm working on a product face in future, that's what I'm gonna be focusing on in conversations with them versus the actual needed really off technical implementation.

If I'm working with the data scientist.

I need to effectively communicate with them about long game or data analysis.

We're just asking them the right question about how want to analyze the data comin from this new project or feature that was built.

So being good at cross functional work is really important as itself for engineer.

And this brings us to my next point communication.

If you think that as a software engineer, you can just sit in a corner, not interact with absolute anyone, you're definitely wrong.

Off course.

You should be set in your own boundaries and communication style.

But successful software engineers are effective communicators.

Successful software engineers make sure that they communicate clearly and effectively, especially if you work on a project that involves other stakeholders or you work with your teammates, other software engineers.

You need to make sure that you communicate with them and over communication.

A lot of times is much better than no communication, because when you communicate or over communicate, you make sure that everyone is on the same page.

You make sure that everyone is clear on what you're working on, and you make sure that no one is wondering all I wonder what nobody's working on.

I wonder if she completed that thing that I asked her to implements couple of days ago.

So communicated effectively, clearly and potentially over communicated is extremely important.

Also, by communicated with your teammates, you can potentially recognize whether you can help them out or you cannot block them and communicated in general, in your team, indoor work in your company just interacted with people can open up opportunities for you.

You might hear about something that another team is working on that fits in or helps out your products, your team or your projects, and that will open up opportunities and doors for you next up.

Recognizing opportunities, Successful software engineers recognized opportunities for improvement and impact.

And what I mean by that is that successful software engineers do not just focus on their projects or feature at hand that they're working on, but they're able to see and follow.

Beyond that, they're able to follow what their teammates are working on.

What their works focuses and why that is important is because when you're able to see that big picture as opposed to being very narrow focused on okay, this is what I'm working on, and this is the only thing I care about.

You were able to potentially recognize opportunities for impact and improvements.

Question why people are doing things a certain way.

You might learn new things that are relevant to you.

You might also potentially recognize what fools they haven't their systems and improve them.

Talking to people, asking people what they're working off thinking about how their work fits in with what you were doing.

Doing where your team is doing are great examples for recognizing opportunities.

And last but definitely not least, is the growth mindsets consistently learning, askin and being open to feedback.

Making sure you learn from your mistakes and reflection are all great examples off growth mindset.

Growth mindset is the difference between thinking that your skill is absolutely set and is defined by talent versus thinking that you can learn and grow and improve your skills.

And your growth is defiance by the amount of work you put in should be a successful software engineer as well as being successful in any profession.

Axe.

You must acquire the growth mindset.

Your skill is not fixed.

You're constantly improving unlearning, and you need to absolutely own that and recognize that successful software engineers are constantly learning constantly asking for a few back facts.

Feedback is also a huge thing.

If someone has given you feedback, do not be defensive about it.

That means that they really care for you to improve.

So you should be open to constantly learning and constantly recognizing what you could do Better.

Successful software engineers are open to learning, are constantly open to grow and are absolutely okay, recognizing that they might be wrong.

Guys, thank you so much for watching this video.

I hope you enjoyed it.

And I hope you weren't something you about habits of successful software engineers.

If you enjoyed it, please don't forget to like and subscribe.

There is a subscribe button down below and please leave your comments down below as well.

What do you think makes a successful software engineer?

I would be really curious to hear your thoughts.

Obviously, what I mentioned is just a couple of ones in the myriad of things that makes a successful software engineer.

But please share your thoughts.

And I hope you have a fantastic week.

Bye for now.