Live data from Hacker News

Ask HN: Solo developer, what's your recipe to start working?

news.ycombinator.com

91–100 of 100 posts

Re: Ask HN: Solo developer, what's your recipe to start working?

#92

After many decades of fighting procrastination the most important thing I have learned is that you cannot analyze yourself out of procrastination. You cannot read articles to solve your procrastination problem. The only thing that works is to start the work. I wish there were something else I could tell you, but that's it. Just open the book, open the editor, open the document, whatever. Now, that said, you may be bu…

Agree wholeheartedly! During the years I've developed a habit to "prepare" the work for tomorrow. Imagine at the end of the day, you're about to work on this "quick and easy" task. How about just do a little of it (not enough to finish the task) and let your tomorrow-self do the rest?

My favorite technique when I'm super lazy, is to write a function with bunch of syntax errors. It forces myself to clear this shit up the next day. And boom, you start working without even knowing it

Re: Ask HN: Solo developer, what's your recipe to start working?

#93
Same thing happened to me recently. Exactly as you describe. Even the thing I dreamt about having time to work on while I was full-time employed was difficult to get started on. Unemployed solo developer procrastination can go on for months - and that's okay.

You should first accept that any time you have already wasted, was always going to be wasted, and thereby free yourself from regret.

While employed I was super productive on side-projects on weekends and after work, but when I had entire days to do as I please, all motivation came to an abrupt halt. I couldn't get back into flow. The motivation dissipated. Distractions took over. Projects felt like mountains to climb without being able to enter flow mode. Without flow its amazing how little you can actually get done in a day.

What worked for me eventually was getting back into flow via any means necessary - and not by working on the thing I most wanted to build.

Procrastination is the key to escaping procrastination.

Working on the thing that I want to turn into a successful business made me feel overwhelmed and stressed, and therefore led to procrastination.

The trick is to get back into a flow state, and then when in this state regularly, you shift across to the project that you should be working on. When in flow the feeling of "if I didn't need to sleep I could get anything done right now" is what you are after.

First, I like to get myself back in front on the computer, by doing some menial task. Like changing your vulnerable passwords in Chrome, or organizing your repos on Github, or cleaning up your bookmarks or browser profiles.

So now you are off the couch and doing stuff. These small, easy tasks, can generate a moderate flow.

Now, pick some small trivial thing that you want to fix or build. Like a bug in an open-source project that bothers you. Or a simple static website that does one silly thing that makes your life easier. Something that is going to help other people or involve collaborating with other people is a good idea - which is why a Github issue is a good. As a developer on a team, you often don't realize how much motivation you draw on from your colleagues. You grind on stuff to make your colleagues lives easier, to impress them, to push the shared company vision further, etc. Even just one other person impacted by what you are doing can be a huge boost in motivation. This is why 2 founders are better than 1 IMHO.

So once you are back into flowing, interrupt yourself to work a bit on the project you really want to work on. Don't say "okay now I am full focus on the real thing I want to do" - make it feel like a procrastination of the thing you are currently doing. Then bang - you have tricked your procrastinating mind.

Its good to take breaks from the thing you are working via other side projects - just the same as you did when you were working - but be careful to not stray too far into something too complex.

Other things that help:

- Podcasts - Listen to morning podcasts with people talking about coding.

- Twitter - Listen to tech conversations. Although Twitter is a big source of procrastination it can also be a good motivator and way to feel less isolated.

- Exercise - Runner's high is super powerful to get motivated - but it will give you a high that dissipates unless you adequately use it to enter flow. It can be counter-productive so don't waste time after a workout before you start coding.

- Alcohol (caution) - If you get stuck in "analysis paralysis" or really can't get going, alcohol is a great way to jump start things. Sometimes I will pour myself a beer, and without even drinking it, I feel this rush of motivation, and I get going on things I put off for ages. It is powerful at taking away mental roadblocks and unleashing great motivation, but the [Balmer Peak](https://xkcd.com/323/) is real! Motivation quickly tapers off. However, it is very dangerous in the long-term. Reliance can creep in quickly - but it can be useful as break yourself out of a rut.

Re: Ask HN: Solo developer, what's your recipe to start working?

#94

After many decades of fighting procrastination the most important thing I have learned is that you cannot analyze yourself out of procrastination. You cannot read articles to solve your procrastination problem. The only thing that works is to start the work. I wish there were something else I could tell you, but that's it. Just open the book, open the editor, open the document, whatever. Now, that said, you may be bu…

> start the work

Not the work, but some work.

You want to procrastinate on something most similar to what you are doing. So if you are on YouTube, start coding. Then when you are coding, its just a matter of switching to coding that thing you should be doing.

Re: Ask HN: Solo developer, what's your recipe to start working?

#95

Absolutely make a formal schedule and stick to it as best you can. Schedule a day that you would want and be satisfied with. Separate work time and leisure time, otherwise as a solo dev you feel guilty for not working all the time, which makes it harder to start work. Don't expect yourself to "want" to start working all the time, because you won't. That's the mistake a lot of people make. Get started on small, easy t…

You workout on a full stomach?

Re: Ask HN: Solo developer, what's your recipe to start working?

#96
post #17

Have you experienced a vision of the person you might become, the work you could accomplish, the realized being you were meant to be? Are you a writer who doesn’t write, a painter who doesn’t paint, an entrepreneur who never starts a venture? Then you know what “Resistance” is. - The War of Art - by Steven Pressfield

This is dumb. You are not meant to be anyone. You do not become a person who you are currently not. You are you, always, and you change throughout your life. Now here, next there. There is no percentage bar to fill up. No 'ding, grats' at level 60.

The author is asking if you've ever felt like you're meant to do something. He's just talking about being conflicted about something you want. He's not saying that you're somehow pre-alloted a goal.

Re: Ask HN: Solo developer, what's your recipe to start working?

#97

Absolutely make a formal schedule and stick to it as best you can. Schedule a day that you would want and be satisfied with. Separate work time and leisure time, otherwise as a solo dev you feel guilty for not working all the time, which makes it harder to start work. Don't expect yourself to "want" to start working all the time, because you won't. That's the mistake a lot of people make. Get started on small, easy t…

I'm not sure this is the best advice. Providing more flexibility allows for the spontaneity of motivation that can help you escape a rut which is what the OP is asking.

This assumes that you can be instantly productive in the 3hr work blocks. If you can't get into a flow for the first hour, then you only have 2 hours, etc. And you start to look forward to your breaks.

Flow works best when you have open-ended working sessions. If you are making good progress - don't stop it for lunch. Grab something quick, and then have a larger dinner.

Re: Ask HN: Solo developer, what's your recipe to start working?

#98
I would highly recommend using mini habits to help get started.

Stephen Guise wrote a book Mini Habits that is quite short but to the point on how to implement these.

https://www.amazon.com/Mini-Habits-Smaller-Bigger-Results/dp...

Using the Pomodoro technique is another great strategy for those days where you really do not feel like doing any work.

Re: Ask HN: Solo developer, what's your recipe to start working?

#99

After many decades of fighting procrastination the most important thing I have learned is that you cannot analyze yourself out of procrastination. You cannot read articles to solve your procrastination problem. The only thing that works is to start the work. I wish there were something else I could tell you, but that's it. Just open the book, open the editor, open the document, whatever. Now, that said, you may be bu…

Agree wholeheartedly! During the years I've developed a habit to "prepare" the work for tomorrow. Imagine at the end of the day, you're about to work on this "quick and easy" task. How about just do a little of it (not enough to finish the task) and let your tomorrow-self do the rest? My favorite technique when I'm super lazy, is to write a function with bunch of syntax errors. It forces myself to clear this shit up…

Hah, picturing an IDE plugin that auto swaps a couple random keywords or characters after last save to always give you a fresh syntax error when getting started!

Whack-a-mole reverse linter, the next big thing...

Re: Ask HN: Solo developer, what's your recipe to start working?

#100
post #95

Absolutely make a formal schedule and stick to it as best you can. Schedule a day that you would want and be satisfied with. Separate work time and leisure time, otherwise as a solo dev you feel guilty for not working all the time, which makes it harder to start work. Don't expect yourself to "want" to start working all the time, because you won't. That's the mistake a lot of people make. Get started on small, easy t…

You workout on a full stomach?

Not OP but I do..
Post reply on HN