How do you keep your energy up to code in the evenings on your own project, after a full day of coding at the office?
How do you keep your energy up to code in the evenings on your own project, after a full day of coding at the office?
1. Get off work at 6 and get home at 6:30.
2. Eat something very simple (no carbs because it will make me sleepy)
3. Start working from 7:00
4. Work till 6:00am (that's 11 hours, which is 3 hours more than my day job)
5. Go to sleep at 6:00 and wake up at 10am and go to work
6. Minimize lunch time and take a nap.
This was possible because I was super motivated. If you're not excited enough about something that you would go through all this trouble, then it's probably not worth investing your time in. That's why I think you're asking the wrong question if you ask "how do you keep your energy?" You don't. You will be always tired and you will not have a balanced life while you do this. But at least you are doing something that means a lot to you, and that's the main factor that helps you keep going.
Of course it is not sustainable to keep going like this for years with no break. So you should take a break once in a while. In my case, at times I would feel very tired or start feeling like burning out. Then I would just take a couple of days off from doing ANY work. Go out and party, watch a movie, do all the "bad" things I would never normally do. I think most people who haven't tried this would say this doesn't work. But from my experience, just a couple of days of doing absolutely nothing is enough to get me back on track--that is, assuming that I am excited enough about the project to begin with.
So if this model doesn't work for you, it probably means you should find another project to work on.
Most of the times I would work like this for a 2~3 weeks to a couple of months without being exhausted. But when that does happen, I would take a break for as many days I want. Normally this break never lasts over 3-4 days. (Like I said, it is important that you are working on the right thing. Otherwise you will never pull this off. For example if the main motivation for your work is you're just looking for some easy way to create a side project that will give you good enough passive income, you are probably not passionate enough about the problem and will give up. In my case I truly believed in what i was working on so it didn't make sense to just go slow on it)
As for my day job performance, it didn't really suffer because most people don't really focus 100% at work anyway.
While I was going through this lifestyle, I tried my best to stay disciplined. For example, I would start working immediately after I arrive at work, with no web browsing. And no web browsing while I am working. If you stick to this principle, you'd be amazed how much you can get done in half the time you normally spend at work. Then with the extra time I have on my hand I would take a nap etc. so I don't get too physically tired.
I agree with the sentiment though-- you really do need the motivation to just DO it. I get good sleep, but I do work longer hours than most people, and I've done so for years. But I genuinely have been only getting healthier and less stressed over time. Work smarter, not harder-- and I've just been getting smarter about how to handle my time.
Depends on what your goals are of course. Quality of life is a big one for me, and that puts my health high on my priorities-- I can't enjoy my riches if I'm sick and dead. But sometimes it's "I can't enjoy my health if I don't have money to eat" so I get the flip side, cause I've been there in work-til-you-drop mode out of necessity.
https://olivergearing.com/wp-content/uploads/2013/03/Importa...
Your side project tasks probably mostly fall into the Q2 box, unless you're getting ready to launch or something then Q1, and your work projects will be spread all around.
Spend your office time according to the 'strategy' for each box (mostly Q1, some Q2), don't stay late at the office to work on some Q3 nonsense, don't work weekends on office related things.
Go home as early as possible, show up to work as late as possible. Use the extra hour in the morning/evening to get knock off a task on your side-project. Ask to work from home 1 or more days out of the week to cut out commuting time.
tl,dr; spend less time on office work and more time on personal work
A sibling comment says that lack of energy indicates low motivation and that you should find a new project. With due respect to the commenter, this is not useful advice. If you are interested in completing a project, you have enough motivation to do so - what you may not have is the right environment around you. So identify what's stopping you from working, and get rid of those road blocks. Some times they aren't obvious and can take some time to identify, but keep paying attention and eventually you will spot them.
Marty Lobdell has a good talk about this on Youtube: https://www.youtube.com/watch?v=IlU-zDU6aQ0&t=1s
I think for me the other thing is -- don't make it bigger than it is, like don't psych yourself out. Yes, it's hard to work from morning to night, but it's just hard, not impossible.
And I think being physically good--eating right, sleep enough, and exercising, yes it's tired advice but that's how you get "energy".
I drink 4 shots of espresso in the morning and 4 shots later in the evening. I used to drink 12 shots total (4 shots, 3x/day), but began to notice that I was suffering from adrenal fatigue where I could function even less if I didn't get the first dose in and each dose didn't last as long at keeping me wakeful, so I cut back to 2x/day.
Along with that, have a proper diet which may include certain supplements (Vitamin D, B12, fish oil), and make sure to get exercise in at least 3 times per week focused, and get up and walk around every so often, doing air squats or something, or simply take a walk around the block.
Surprisingly enough limiting the time you spend on writing code after work (to 1-2h a day) also helps. This way there's less pressure to have something finished each day (because it's impossible in such a narrow timeframe) and more time in-between coding sessions to think about the design.
Most of the time my after-hours code is much more thought through than what I create at work.