Yeah, you can do that, if you legitimately want to. Or you can have a life away from the computer and go outside once in a while. So here's some different advice.
DO: Be good at your craft. Be able to go into an interview and discuss architecture or algorithms or whatever it is that you're interviewing for with the people you're going to be working with. Be able to talk about your thought process, so that even if maybe you don't remember the exact syntax of some API call or command-line utility, you can explain to the interviewer what you're thinking and why.
DON'T: Don't for a minute believe that you must be "passionate" about programming in order to enjoy it or to be good at it. Don't forget that you and your employer are engaged in a business relationship, and nothing more. Don't romanticize your job or define your self-worth by the fact that you work for FaceAppleGoogSnapZonFlix (or that you don't).
And don't work your ass to the bone chasing someone else's big idea.