I am the ex Google Tech lead.

Today we're going to be covering the top seven highly effective habits of programmers.

It's coffee time now.

The funny thing is that programming is a sort of career that if you don't do it right, if you don't go in there with the right habits and the right skills, gonna mess yourself up pretty badly pretty seriously, they burn out.

They become very strange, and people started saying that they have Asperger's.

Maybe some of those people got to start YouTube channels.

Some of them burn out and become data scientists, and then others go off and become managers because they don't really know quite what they're doing.

So you need to go in here with the right habits, and I say happens because this is a long term game and it's not religious about having a few skills, a few techniques here and there, a few tips and tricks you need to craft the right habits, and those habits will mode you every day to have the right career trajectory.

I have been working in this industry for over 10 years, highly decorated, highly successful ex Google Tech lead, and I'm here to provide you my top seven habits now.

First of all, though, I do want to mention that we do have a brand new sponsor today, and when that I'm really happy to introduce to you, if you have heard of them already, that service is blink ist.

It's an app that summarizes books into 15 minutes for you.

It's a lot like heavy and friend.

Read an entire book for you and then giving you all of the highlights.

And let's face it, in today's age, it can be hard to find the time to sit down and read.

It's not easy with their social media blocks news.

So blinking is the only app that takes the best insights, all the need to know information from a book and condenses that into 15 minutes for you to read or listen to.

Personally, I think that many of the best books shouldn't take hours to plow through.

Their messages can be told in just 15 minutes or so, but author sometimes just go on and on about topic.

Blinkers is a very popular service.

Millions of people are already using it, in fact, and they have massive library ranging from self help books, health history and business books.

My favorite, actually, on my draft today I listen to the seven habits of highly effective people, and it's a great read, phenomenal book named the one of the most influential books of the 20th century.

And I was able to get through that just 15 minutes on my drive.

Using the blink is that the 1st 100 to check out blankets dot com slash tackle.

It will get a free one week trial, unlimited access, and then if you continue, you also get 25% off before membership.

And keep in mind that this seven day trial it's completely free.

No risk.

You don't have to pay in 18 so I would recommend you give it a try.

If you haven't already.

It's a great service.

Blink us dot com slash tech lead.

All right, so let's get into the tips here, and my first step for you to really understand here is that programming is a physically demanding activity.

I know that.

You think all you have to do is just sit down in the chair and it should be easy, but it's not quite like that.

In fact, if you were to just sit in your chair the whole time, your body with deteriorate so fast you would become a slouch.

You're back would become hunched over.

Your body would deteriorate into the shape of a chair.

You become incredibly unattractive.

Your eyes would dry out from staring at the computer screen so long your skin is not going to get enough sunshine.

Such that is going to become a pale and pasty.

And as you get deeper into program, you start moving into the basement into buildings without windows.

It just gets darker and darker for you until you eventually become like a window go.

So you need to understand that good exercise and good sleep are essential for any programmer.

And this is something that I make sure I get for myself every day.

If I were to go program for a long period of time, I'm going to make sure that I get my exercise in as well, and I also have a very good sleep routine.

Not only that, I make sure that when I sit down, I sit with my back straight such that I have a good posture because it's pretty funny.

If you're to go to some of these tech companies and see a bunch of programmers, they look really weird.

Their backs are all hunched over.

Their necks have elongated as the pure in deeper and deeper into that computer screen and their gaze.

Their eyes just seem to glaze over all the time.

I take a break every 30 minutes, and I also drink a ton of fluids such that my eyes don't get too dry.

And I think overall, people just need to drink a lot of fluids in general.

For my lunch breaks, I go out and make sure I get some sunshine on my skin.

You know, these are all good habits that you need to build up as a programmer.

To protect your physical body is kind of like a sports star.

Sports stars have to go to the gym home, their bodies build their muscles, make it perfect for their game, and it's no different for programmers.

Except programs are kind of on the opposite end of the scale, where their bodies are deteriorating, completely weak and almost falling apart, destroyed into the shape of a chair, and then they just have to try to protect their bodies and mode it back into, like, a normal baseline so that they don't appear too weird.

Now my second tip for you is have a get it done attitude.

This sort of kind of like getting 18% the work and just shipping a product.

You know, making sure that you're getting things out the door moving things along because programmers tend to have a tendency to just keep working on some strange little funding problem and just keep the bugging something for hours and hours.

It's not weird to hear programmers spent a whole week working on some small, stupid little bug and just trying to untangle some little puzzle in their head because it's just so fun.

And they just get stuck in this strange little loop that they're trying to figure out, you know, to be a really effective program, or you need to keep your eye on the goal and then reverse engineer what you need to do to get your project out the door to ship things.

A lot of people like to over romanticize the technology.

The little tools that they have.

The editors, this in tax coloring, arguing about Max versus Vin, getting their keyboard shortcuts all set up.

You know, I don't try to configure my environment such as very weird.

I like my environment actually to be pretty normal so that I could be productive at any machine because one of my goals is to be productive in the Apple store, such that if I'm out traveling remotely, I can go to any Apple store and start working right there.

I'm gonna feel right at home.

There is funny that as programmers have something called open source culture, where we're just going to start working on something that never really ships.

But there's no real end user.

There's no product.

We just work on some framework and then polish that framework over and over and at all sorts of functionality to it.

But there's no actual way to ship this and get money from it.

It never really ends up in the hands of users.

It never really gets you any money is just something that you just polish over and over and just keep doing that little thing over there and, you know, that's not really results oriented, I guess I would say, in fact, the viewer to work in industry.

You may find that it's quite opposite from open source culture, where a lot of the code is just duct tape, stringed up, hack together.

And then they just ship the product and make sure that the product looks good and that it's marketable.

But it's not about re factoring the code over and over again until it looks beautiful and perfect, and then you can upload it to open source, and everyone's going to celebrate how beautiful your little piece of code looks.

My third habit for you guys here is the concept of keep it simple consistency.

When she began to program, you're going to find that there are hundreds, if not millions, of ways to get things done.

You can write a piece of code in 100 different ways.

You can re factor a ton of different ways, and then things become unmanageable.

When you or other people are all doing things in a different way, and then you're trying to get that coat to interrupt with each other or you're trying to reach someone else's code.

You're reading some code that you had written a while back, and you may find that you're not able to re use code.

You may find portions of a programmer in many different ways.

You may find views that are duplicated, and then you have, like 5 10 20 copies of a certain view.

Programming is one of those fields that is dominated by extremely arrogant people.

What these people like to do is they'd liketo over engineer their code.

They like to show off how smart they are, and then they tried to make things so complicated and so twisted that nobody else can read the code, accept them and then they feel some sort of pride about that over time.

Is you getting experience?

You start to understand that all of this is working against you.

You need to keep code as simple and consistent as possible, and that's what's going to help you be able to avoid crashes.

Avoid bugs quickly, be able to read and understand your code or other people's coats.

Re factor things quickly, make changes deepa code faster and just going to help you ship your project much more quickly have been number four is to have a consistent way to get in the zone.

So the zone is one of the most productive times for a programmer when you're just coding and you're just swimming through that code and you lose track of time and before you know you've written an entire program and this is a period of time when you're not interrupted by anybody else and you can just have long stretches of time like, say, three hours or so, I would say where you can just sit down and get some solid coat in and then make sure to budget my personal time and to set expectations for people around me such that people understand that I need a specific, undisturbed period of time where I can be productive.

Program is just one of those fields where if you're interrupted every say, 10 20 minutes, you're just not going to be able to get making them because you need to build these larger abstractions mental blocks in your head, and it just takes a longer pair of time to get that stuff done.

Happened Number five always be learning.

Sharpening yourself did the other of your comforts.

Um, it's very easy, and we're coding to get stuck in a certain routine where you're just doing a certain small subset of an area, and you could just do that for a number of months or even years.

And over time, you may find, though, that you're not really learning anything more, and then you become outdated.

So you need to always be learning, and only that one of the key skills of programming is the ability to debug.

And this has less to do with the experience you have and more with.

If you can learn an environment, understand how another programmer system is put together and then diagnose that to figure out what the root cause of some issue.

Maybe my sixth habit for you is collaboration.

When I began programming, I did a lot of things on my own, and, you know, I wanted to be that lone hacker, the loan program, who just hide away.

But that's really not very effective, and this ought to comment for me to see some engineer go off into the woods.

A week or two later, they come back and they say they've just been stuck on something and they're not reaching out for help, and they just waste huge amounts of time for them, and it destroys their productivity.

This is why collaboration may be important is quite common that other people within your visited the or team may have some ideas.

Some clues about what could be causing some issue.

Not only that, programming is very much a team sport, right?

You're often interacting with many other people's coat.

If you're pulling in some framework, or if you're working within the company environment, you're most likely working with a whole bunch of other people.

And then your code needs to integrate with other people's coat.

It's really like a sports team, right?

So it's not really a solo activity, although on the outside it looks like you're just sitting there, programming all by yourself.

In reality, in that digital domain, you are a team player.

And then my last and seventh habit for ah, highly effective programmer is to understand that programming maybe a lonely activity, and you just need to get used to it.

You need to get used to spending large amounts of time on your own.

This career is not like being a doctor, where you're just talking with tons of people is not like being the cashier or a sales person or a manager or a consultant in programming.

It tends to be more of a solo activity.

So if all of your friends are out partying, not working, going to parties, talking with other people, you know that's fine for them, right?

Because maybe they're going to go out and become salespeople consultants.

Maybe they just don't really need to spend three hours by themselves in front of a computer.

Get in his own butt.

If your sound trained to be a programmer than you need to budget for that sort of experience for yourself, where you're just going to be by yourself spending three hours reading some documentation.

It's funny that programming maybe one of the loneliest careers.

I'm not sure of any other career where people spend this much time alone, right?

Like lawyers, for example, spend the law time dealing with people, musicians, teachers, even scientists are often dealing with their colleagues discussing research and things like that.

But programming programming.

You spend a lot of time in that digital world where you're oftentimes reading documentation, study a piece of code debugging something on by yourself.

And so what I'm trying to tell you is that there's going to be a time when other people are out in the world socializing as they're doing their job, and you're not going to be doing that right.

You're gonna be stuck at the computer debugging some piece of code that you've been trying to debunk for weeks.

And that's kind of where programming comes in.

You just need to have that proper expectation.

So any career has its highs and lows, its good points and this bad points and programming is just one of those careers I think demands a little bit more of your personal time.

Just you, not you and your friends.

Just you.

So just set those expectations budget for that and you'll be all set.

Let me know where you're top Happens are for programmers.

If you like the video, give elections abstract violence.

You Next time.