[ogwh]

You need to stop building things you don't enjoy building and which you have little to no interest in actually using. After that take as much time as necessary for something to strike your interest, possibly in a totally different domain (e.g., embedded systems instead of CRUD crap).

Once you reach that point tinker a little, not a lot. When you feel resistance take a break, never force yourself. Don't force yourself to write code you don't enjoy writing, find ways around it, at least initially. You need to avoid reinforcing the association between code and pain until you have a buffer of good experiences in your new domain.

It might be (probably will be) necessary to find a new career path in the meantime.

Good luck.

[adamquek]

Great advice there. Yar, do something you really want to solve. Don't go through the motion of building for the sake of building.

Spend the time reading or watching how other find problems and solve them. Talk to people, especially people out of the field. See if they have interesting problems you may want to find a solution for.

And yes. Take a break. Actually, take a long break. You will find that you will regain your motivation, and work faster and longer when you come back.

[the_only_law]

> You need to stop building things you don't enjoy building and which you have little to no interest in actually using.

Easier said than done. The only people who want to hire me and are even willing to talk to me are in that category, because that’s what my resume says I’ve done.

In the meantime, I’m waiting to pounce on an exit from the field entirely.