Jennifer Senior wrote a great piece back in 2006 about burnout [1] titled "Can’t Get No Satisfaction". It's worth reading the whole thing. Here are some fragments that stuck with me:
> we think of burnout as the gap between expectations and rewards
> happiness equals reality divided by expectations
> level of caring couldn’t be sustained in the absence of results
How have you been framing your side project? Is your side project intended to be a business? If so, what outputs is the business achieving (revenue, profit, your effective hourly wage as the owner operator)? Dispassionately, is it doing well enough commercially that it makes sense to continue to pursue this business?
In the case where this side project has not been achieving sufficient commercial results, and has been falling short of your expectations and the goals you set yourself, is it possible that your resistance to continuing working on the side project is because subconsciously your body has decided it is not a good use of additional time and energy?
It could be beneficial and healthy if you could give yourself a long break from thinking and focusing on your side project, to get your brain out of this habit of focusing on the side project and give it the opportunity to think and focus on some new things, or just to rest.
From my experience (not with side projects but with job related burnout) consider taking a holiday from it, get lots of sunlight and exercise, spend time with friends and family, pick up a new hobby or resume an old hobby that gives you some immediate enjoyment in the moment. It may take months for your habitual thinking patterns to adjust, but once your thinking patterns change you may have a very different perspective on the situation.
A couple things that help me when I hit this exact wall: shrink the surface area and make the loop tiny. Pick one ridiculously small, end‑to‑end deliverable (e.g., “add X toggle with a minimal UI, ship a changelog”) and set a 15‑minute “opening ritual” where the only goal is to open the editor and write a stub or one failing test. Energy often follows action, not the other way around. If solo inertia is heavy, swap in co‑working or lightweight pairing; or open a small, well‑scoped issue to invite contributions so you’re reviewing instead of starting cold.
Also worth reframing: is this a business or a craft project? If it’s not pulling its weight commercially, put it in maintenance mode with a clear cadence and let yourself step away guilt‑free for a month. Sunlight, movement, new inputs—your brain will reset its reward signals. When you come back, protect the fun: fewer plans, more shipping, tighter feedback loops.
1) "I even created detailed plans for easy to build features that users requested"
2) "I know exactly what to build and how to build it"
You seem to have a nice specification of what you want to build and how. Unfortunately, you feel burned out. Thus, one option is to try to leverage LLM by feeding your well-defined specifications and then revising them.
+1 to this. I've found AI to be a good tool for getting things started, and for handling more tedious features that would have required reading a lot of documentation. I wouldn't trust AI to build a whole feature on its own, but with you at the helm, you can use it to build a feature one piece at a time.
I use Perplexity with a free account.
Possibly by coding with another person, if you can find the right person who can meet you IRL to work on it.
If it is useful and has a following, open-sourcing might create some collaborative energy?
I think you're confusing plans and action, too. You don't actually know what it will take to add the features users ask for until you do it. Your detailed plans are probably taking the fun out of what you should be doing when you sit down to code.
I have a brilliant phrase for you, it's called a baggage without a handle. It's hard to carry it with you and it's a shame to throw it away.
I was in very very similar situation and just put the lights off. You can't trick your brain to do hard work for free. Why spend your time working on something that unsuccessful when you can work on something that you actually like?
I am 53 and have had a sideline for 18 years which makes about a 1/4 of an average salary.
I believe people are meant to have one job, unless poverty or circumstance is driving their financial needs.
If your sideline is not making money consider dropping it.
When you enjoy something like programming, and people giving you positive feedback, you don't sometimes consider the bigger questions. Am I happy? What am I doing with my life and relationships?
A sideline worked for me as it has made hundreds of thousands and changed my family's life.
If yours is a hobby, consider stopping it, and see if it comes back to you down the line.
You are a prime candidate for Structured Procrastination (https://structuredprocrastination.com/)
Some of my best work was done while procrastinating on my main hobby project!
I'm thinking you need a therapist more than you need HN. I've been in the software development business for 40 years and I've never once heard of anyone being afflicted with this problem. Maybe a therapist could also help you stop freezing up when you sit at your computer to work on your project?
What he's describing are fairly typical symptoms of depression, including the freezing. Not rare at all. I agree that he should seek some real assistance with it, but he's not at all some kind of outlier.
Mine is only an anecdote. I've been in this business for decades and I've never seen or even heard of anything like this. Even so, I think we agree a therapist would be really good for him to get over this patch.
Jennifer Senior wrote a great piece back in 2006 about burnout [1] titled "Can’t Get No Satisfaction". It's worth reading the whole thing. Here are some fragments that stuck with me:
> we think of burnout as the gap between expectations and rewards
> happiness equals reality divided by expectations
> level of caring couldn’t be sustained in the absence of results
How have you been framing your side project? Is your side project intended to be a business? If so, what outputs is the business achieving (revenue, profit, your effective hourly wage as the owner operator)? Dispassionately, is it doing well enough commercially that it makes sense to continue to pursue this business?
In the case where this side project has not been achieving sufficient commercial results, and has been falling short of your expectations and the goals you set yourself, is it possible that your resistance to continuing working on the side project is because subconsciously your body has decided it is not a good use of additional time and energy?
It could be beneficial and healthy if you could give yourself a long break from thinking and focusing on your side project, to get your brain out of this habit of focusing on the side project and give it the opportunity to think and focus on some new things, or just to rest.
From my experience (not with side projects but with job related burnout) consider taking a holiday from it, get lots of sunlight and exercise, spend time with friends and family, pick up a new hobby or resume an old hobby that gives you some immediate enjoyment in the moment. It may take months for your habitual thinking patterns to adjust, but once your thinking patterns change you may have a very different perspective on the situation.
[1] https://nymag.com/news/features/24757/
A couple things that help me when I hit this exact wall: shrink the surface area and make the loop tiny. Pick one ridiculously small, end‑to‑end deliverable (e.g., “add X toggle with a minimal UI, ship a changelog”) and set a 15‑minute “opening ritual” where the only goal is to open the editor and write a stub or one failing test. Energy often follows action, not the other way around. If solo inertia is heavy, swap in co‑working or lightweight pairing; or open a small, well‑scoped issue to invite contributions so you’re reviewing instead of starting cold.
Also worth reframing: is this a business or a craft project? If it’s not pulling its weight commercially, put it in maintenance mode with a clear cadence and let yourself step away guilt‑free for a month. Sunlight, movement, new inputs—your brain will reset its reward signals. When you come back, protect the fun: fewer plans, more shipping, tighter feedback loops.
1) "I even created detailed plans for easy to build features that users requested" 2) "I know exactly what to build and how to build it"
You seem to have a nice specification of what you want to build and how. Unfortunately, you feel burned out. Thus, one option is to try to leverage LLM by feeding your well-defined specifications and then revising them.
I believe this can help you make progress.
+1 to this. I've found AI to be a good tool for getting things started, and for handling more tedious features that would have required reading a lot of documentation. I wouldn't trust AI to build a whole feature on its own, but with you at the helm, you can use it to build a feature one piece at a time. I use Perplexity with a free account.
> How can I escape this cycle?
Possibly by coding with another person, if you can find the right person who can meet you IRL to work on it.
If it is useful and has a following, open-sourcing might create some collaborative energy?
I think you're confusing plans and action, too. You don't actually know what it will take to add the features users ask for until you do it. Your detailed plans are probably taking the fun out of what you should be doing when you sit down to code.
I have a brilliant phrase for you, it's called a baggage without a handle. It's hard to carry it with you and it's a shame to throw it away.
I was in very very similar situation and just put the lights off. You can't trick your brain to do hard work for free. Why spend your time working on something that unsuccessful when you can work on something that you actually like?
I am 53 and have had a sideline for 18 years which makes about a 1/4 of an average salary.
I believe people are meant to have one job, unless poverty or circumstance is driving their financial needs.
If your sideline is not making money consider dropping it.
When you enjoy something like programming, and people giving you positive feedback, you don't sometimes consider the bigger questions. Am I happy? What am I doing with my life and relationships?
A sideline worked for me as it has made hundreds of thousands and changed my family's life.
If yours is a hobby, consider stopping it, and see if it comes back to you down the line.
You are a prime candidate for Structured Procrastination (https://structuredprocrastination.com/) Some of my best work was done while procrastinating on my main hobby project!
I'm thinking you need a therapist more than you need HN. I've been in the software development business for 40 years and I've never once heard of anyone being afflicted with this problem. Maybe a therapist could also help you stop freezing up when you sit at your computer to work on your project?
What he's describing are fairly typical symptoms of depression, including the freezing. Not rare at all. I agree that he should seek some real assistance with it, but he's not at all some kind of outlier.
Mine is only an anecdote. I've been in this business for decades and I've never seen or even heard of anything like this. Even so, I think we agree a therapist would be really good for him to get over this patch.