1. It's Saturday morning.<p>2. You start coding in your side-project.<p>3. A couple of hours go by.<p>4. You feel like, "I'm tired. Let's do this tomorrow.".<p>5. You also would like to ship it ASAP too.<p>What do you do?
Firstly.<p>> 5. You also would like to ship it ASAP too.<p>Take that away from your mindset immediately! You can't do anything ASAP. I am a firm dis-believer of, "I can build it in a weekend".<p>Take a bit of paper and actually map out the project. Break it down into small pieces. Now start to work on the first piece, then take a break if needed. When you start again, work on the next.<p>Doing things this way, gives you multiple benefits:<p>1) allows your brain to focus on the task at hand. Otherwise it starts to focus on the entire project and thats when you short-circuit.<p>2) gives you a sense of accomplishment and you see your project go from start to finish.<p>3) allows you to easily come back to the project if you decide to take a long break from it.<p>It's also important that if you see things that you want to change. STOP! Take out another piece of paper and write down things for version 2. Now carry on with the work.<p>It's also worth mentioning, perhaps to keep some kind of journal with notes. So you can tell yourself things to investigate should you come across them in dealing with a problem.<p>Once you have finished and shipped version 1. You can then decide if you want to start again or wait until other things happen. Such as a community forming, you get stars on github, do a show HN. Whatever the ultimate goal is for the project.<p>Or you can decide to write another side project.<p>Ultimately, it's your time. Learn to use it well.<p>Btw, this is coming from someone who has built 40 side projects that easily could be their own SaaS start-ups thus far.
I do chores - it's a great tool for gauging how unwilling you are to code at the moment.<p>Yesterday my bathroom sink received some much needed care.<p>Also eventually you'll get so fed up with this that you'll gladly return to your side project.<p>Conversely guilting yourself into programming when you really don't want to is one way to abandon any after-hours work altogether.
Chop wood, carry water.<p>In other words, keep on keeping on. "A couple of hours" of focused work is actually fairly productive, more productive than most people get. It's like writing: do a little bit every day, pretty much no matter what, and it'll get done by accident.
1) Assess I'm feeling any one of HALT - Hungry, Angry, Lonely, Tired.<p>If I'm feeling hungry, I'll make myself a healthy meal. Tired? Take a 20 minute nap, then do some jumping jacks and listen to up-tempo music. Lonely? Call it quits for the day and go find social interaction. Angry? Either I need to re-examine my expectations for myself, Take a step back and get a better understanding of my tools, or stop using selenium and switch to <a href="https://www.cypress.io/" rel="nofollow">https://www.cypress.io/</a><p>----<p>> You also would like to ship it ASAP too.<p>Things take time. Either cut the scope of the project or work on accepting that things take time.
If it’s a side project, just stop and wait for when you feel like working again. For me, forcing myself to work on something that isn’t putting food on the table just builds resentment.
Write documentation. I know that sounds the same as "keep working on it", but it's surprising how often going through updating/fixing docs gets me unstuck. And if it doesn't, at least I've done something productive.<p>If the docs are fine, there are usually other things to improve or experiment with (file organization, build process, tests, editor plugins...etc).
Exercise. Bike, blade, or run. I go and rollerblade the Embarcedero.<p>You get some sun, you tire yourself out in a different way, your eyes get to focus more than two feet in front of you. There are people around but you don’t have to be social if you don’t want - moving at a different speed means you can still think on your mental problem.<p>Finally, you work up an appetite that sitting at a computer just doesn’t give you, and you can reward yourself with some nice noms that you feel you’ve earned and will give you the energy to return to code work.<p>Edit: I forgot to mention podcasts or audiobooks. If you want some external input for your mental stimulation you can do that at the same time!
><i>5. You also would like to ship it ASAP too.</i><p>I suspect number 5 is a stress factor. I believe stress can cause fatigue and/or procrastination.<p>Try to accept the situation. Take your time and enjoy the task.
I push myself when I don't want to do it. But also limit myself to the allocated time when motivation is aplenty. Especially the latter.<p>btw John Cleese is an amazing inspiration on how to be (consistently) creative <a href="https://genius.com/John-cleese-lecture-on-creativity-annotated" rel="nofollow">https://genius.com/John-cleese-lecture-on-creativity-annotat...</a>
Discipline is doing the thing you should be doing, even when you don't <i>feel</i> like doing it. It's also sometimes called perseverance. Discipline is a skill you can develop.<p>I've started two successful companies (one bootstrapped, one VC backed) and they both took an enormous amount of discipline and perseverance. I'm now on my third and it's pretty much the same, but many things are easier this time around.<p>So, what do I do when I don't feel like working anymore? I keep working. :-)
<i>what you're about to read is anecdotal, subjective, and comes from personal experience. Take what resonates with you.</i><p>Sometimes it is what it is, just accept it and do something else.<p>From my experience, the factors below highly impact this behavior:<p>1. Is the project too big to chew on?
2. Are your tasks very well defined and the finish line is clear?
3. Is the expected outcome for fun or you're hoping to make it big when it's done?
4. Is the project solving a problem you care about dearly or a general problem you're trying to solve to make a business out of it?
5. The project is very motivating, everything is going well but you're unaware that you're working on a very uninteresting task that's part of the project and you're chewing on it slowly as a result.<p>When you sit on the chair and you feel it's kicking you off to get up instead of sucking you in then probably there's a conflict of interest between what <i>you</i> think you should work on and what your brain is interested in working on.<p>Do consider the possibility that you're probably assigning yourself a boring project or a project that deep down you don't care about or it's too big and overwhelming.<p>As we gain more experience and pile up failures, it becomes more challenging to get on a project. From my experience, the best projects I worked on are ones that have no monetary value nor related to launching some sort of a business and I am working on them just because they have challenging and very interesting problems for my taste, or they solve a problem I face.
Go run a quick 5K. Or 3K. Or brisk walk around the block. Get the blood pumping.<p>Make a to do list of the tasks you are attempting to achieve today. Do one thing only today. When it is all too overwhelming, break it down into tiny self-evident steps. Micromanage your brain.<p>Not too much coffee.
Do something analog. Find something to do that is not with a computer until you get tired of that. Then build a balance chart, draw a circle, draw lines to quarter it, then lines between those. You should see a what looks like a wagon wheel. Each spoke is an aspect of your life. Label each spoke with the 8 important things in your life. This will show you the importance of keeping the spokes “8 things in balance. One spoke could be your job, another your side project, another your family, a hobby, social/friends, downtime, etc... the wheel represents you, giving to much time to a single spoke makes the wheel lopsided and it won’t turn. So as you devote your time to things, imagine which of the 8 is suffering and not getting your time. Try to devote equal time to each.<p>This is the best way I have found to get things done, and not get burned out/ or saying things like “my give a damn is busted.” It also gives you 7 other things to do when you feel like you do now. Then after you do one of the others see how you feel, go back to the one you didn’t feel like doing or do one of the other things until you feel like it.
What's the point of doing something you do for fun if you force yourself to do it? To me that is a contradiction and which is why I don't do side projects anymore since I started doing coding for full time.
1. Set a Pomodoro timer (25 minutes).<p>2. Tell myself "just work on the project/problem for just five more minutes."<p>3. <i></i>* Work and allow no interruptions <i></i>*<p>4. Pomodoro timer rings.<p>5. "Wow. I didn't notice time passing."<p>Almost always, the satisfaction of surpassing the 5 minute goal is enough encouragement to continue for a good long while.<p>Personally, this works as well (if not better than) changing my work venue.
Go for a long walk, until I'm so hu angry I could eat anything I pass that smells good. I stop and pick something out I want to eat and eat it. Then go lay outside in the shade and let my mind wander about how amazing and strange the universe is, and how thankful I am that I am experiencing life.
From my personal experience programming (for my own pleasure) has three phases just like any other addiction.<p>1) Expectations phase where I love opening my laptop, touching the keyboard etc. and I have some sketchy ideas what to do.<p>2) Extatic phase - where I am working for 16-18 hours solving problems I didn't expected I would be able to solve and writing a code that I later keep re-reading just to appreciate it's dense beauty.<p>3) Diminishing returns phase where I am still trying to get some kicks from it but it isn't coming anymore.<p>If you are in a phase 3 then it is clearly a time to stop, get sleep, do yoga, meditate, go for a run or get on a bike. Don't look at a laptop for a few days.
Time away from the keyboard makes you more effective at the keyboard.<p>Take a break, let your brain breathe. Do some other tasks, hobbies or chores and you'll find yourself thinking about code soon enough.
Sleep. Just finshed a long week. Slept from 9pm until 8am. When work is done: sleep. Eat. Exercise. Chores. Then "fun", if there is enough time sunday night.
Know why. To push myself i need to know why. Without it, i get distracted too easy. I’ve now returned back to the tried and tested way of writing down (in a personal wiki) my long term goals and how I plan to get there. And a personal notebook (updated every 1-2 days) shows me my near term tasks. I go thru the wiki frequently, cleaning up and rearranging things. This keeps my long term visions in check and gives me purpose and motivation to complete my tasks.
45 yr old developer here, been at this for a long time...<p>While it can be tempting to just push through, that can be dangerous. Sometimes that "meh" feeling is a symptom of burnout. Did you have a long week? Lots of hours? Put out some fires? Decompressing now will be better than fully burning out in a few months with some shoddily coded side project to show for it.<p>That said, it's also possible that you need to "chop wood, carry water" as mentioned by another poster, but if you do that, take a moment to look at your side project from another level. Are you slogging because of some architectural debt, or because you're just poking at the problem to see what works? Personally, I get bogged down when I haven't thought through the problem at a higher level. Sometimes I'll just write a series of steps to get from where I am, to where I need to be, and identify the thing I am dreading doing.<p>TL;DR: Sometimes you need a break, sometimes you need to step back and take a 10k foot view of what's bugging you, and sometimes you just need to push through. It depends ;)
Start with shipping from day one. Before any coding. If it's a web app create a new hello world project push it to a git repo. Get a cheap server from a hosting company deploy your hello world app to it. Point a real domain to it and install an ssl cert on it. Now you have an actual app running on the open web. From then on you can iterate by completing one endpoint/controller action at a time and immediately pushing that live and getting user feedback on it. Then on to the next one. One additional point is that you can get a generic domain name which will allow you to endlessly pivot your app without having to setup a new domain and hosting if you change your idea. This implies that you always have just one side project that will change over time and never work on multiple side projects.
If you're asking on ways to combat the urge to stop, I'd create a Trello board, and split it into the smallest pieces possible. Even if you have to stop, perhaps you can work on a 10-minute piece. Typically, those small wins keep me going.
If you feel like that constantly and it doesn't matter which side-project it is, you should consider that you may be going through a burnout. Only a long time away from the offending activities might restore your energy to do them again.
I tell myself: "Holy crap, look at how much money you're being paid. Do you remember the labor jobs you used to have?"<p>Then I think about some nice things I'd like to buy. This is usually enough to get me going.
No solution here but I have been struggling with this for a couple of weeks now (5ish) but just in general, not only for side projects.<p>Thus I am quite interested in this thread myself :)
I think it’s probably important to figure out WHY #4 happens. If this is something you’re passionate about, or something that you need to pay the bills soon, I would think that your motivation or excitement level wouldn’t wane so quickly.<p>After those couple hours, if you stop working on it, what do you do? Do you take a break and get back at it? Or do you follow through on waiting til tomorrow?
You need at least half day break from focused pursuits. After that channel energy into other focused pursuit<p>- playing guitar, piano etc<p>- studying math, EE, physics<p>- learn foreign language<p>- sports, yoga
Keep working on open source to court attention, avoid becoming homeless. Keep working after becoming homeless and most friends have left. Now considering crimes to get shelter via jail... felony would help employment via protected status. Unsure if I’m joking, as those are our society’s chosen incentivized paths.
I write code that generates music, controls external gear.<p><a href="https://lowveld.bandcamp.com" rel="nofollow">https://lowveld.bandcamp.com</a><p>Once I accomplish something that sounds good to me, I put it on and go back to my side project ;)
Use the pomodoro technique, it is ideal for this type so situation. It helps you get into the flow. Having a list of focused things you need to complete before you apply this technique is also a requirement.
Anyone have a good book/article for the exact topic?, What's on my mind is deepwork by cal newport<p>I'm working on my thesis but have a hard time to keep the motivation high