A lot of you know that I'm working as a software engineer and you have seen my day in the Life is a software engineer, a video which showcase the fund office, a lot of food and just doing different activities around the office, which left a lot of couldn't fusion.

Yeah, Sonny Gupta is onto something here because the reality is actually different.

So what do programmers actually do?

If you're curious to find out, please stay tuned.

San Francisco is getting really, really chilly, and I'm sitting here in my cozy apartment about to tell you a bit more about what programmers actually do.

Let's look at the weekend definition.

All the programmer computer programmer is a person that creates computer software, and what is computer software?

Computer software is a set of data or computer instructions that tell the computer what to do.

Let's stay for Wikipedia as an example, Wikipedia and needs software engineers to make sure that when you and I opened the same Article, two added it, we can actually collaborate on it, and this changes that you made one be erased when I click the safe or added button.

Wikipedia needs a set up software engineers to maintain its databases all over the world because, believe it or not, Wikipedia has around six million articles, so we need to make sure that all that can be maintained and bureau bust.

Wikipedia needs to make sure that the front end's off the website looks the way the designers have implemented, so it needs a set of front end engineers to do that.

Wikipedia also needs to make sure that when you I millions of people around the world's open millions and millions of articles, Wikipedia doesn't crash.

It's fast on its able to maintain that huge a load.

Software engineers solved problems and to solve a problem, acts they use coating as a tool.

So essentially software engineers are problem solvers.

And to solve a problem at the programmer needs to understand the problem, they need to understand the context around the problem.

They very much need to understand the constraints of the system surrounding the problem, and they're off course deeply need to understand why they're solving the problem they're solving.

It might go something like this.

I work as a software engineer at Airbnb on let's say air being being wants to develop the wish list feature to develop this wish list, feature I as a back an engineer would be responsible for all the underlying logic that you, the user do not see.

But that is how the system works.

So when you heart house on Airbnb, I need to make sure that this house is going to be associating with the wish list list that you as a user create and that this list in and of itself, it needs to be associating with my user accounts and that this list is going to be saved in the database.

The house will be saved in the list in the database and associate it with my accounts.

I need to make sure that when you unharmed the house it's going to be removed from my wish list and removed from association with my user accounts.

All that is what I as a back an engineer with you're responsible for a front end engineer will work closely with me because they need to know what is that.

Underlined logic for this future as well as with a designer will propose the designs off how it will actually look like on the platform.

And then all of us together will also work probably with the data scientists, because data scientist will actually analyze houses.

Successful was this feature should Shouldn't be something that we should keep on the platform.

So we would implement logging.

Thio track how popular the future is.

How many users use it?

Are they happy with it?

Is the button color?

All right, so all of us will work as a team on this.

I hope this shed some light on what programmers actually do.

And if you like this video, don't forget to like and subscribe.

Leave any commons down below.

Put the notification buttons on to know when the new content is common.

And I hope you guys have a wonderful, wonderful day.

Bye for now.