If it is a consistent feeling then may be you are ripe for change. However, if it comes in phases, then following works for me in exact order. Frankly, followin

If it is a consistent feeling then may be you are ripe for change. However, if it comes in phases, then following works for me in exact order. Frankly, following is more for "developer's block" but may be that's what you are going through. 1. Try something different, new. However, it should not be complex, at least not to start with. 1. If that doesn't hooks you, pick a small trivial, meaningless utility to write in whatever framework you are comfortable with. It is important not to overshoot - really just pick a "meaningless" and simple task. 1. If that doesn't work, pick some small utility from a blog/video where full code is available (many examples here - https://news.ycombinator.com/item?id=16591918 https://news.ycombinator.com/item?id=16591918). Write whole code again, copying line by line. As you start getting involved, stop copying and start thinking how you would write the next function, or what optimization you'd do for current function, etc. 1. If that also doesn't work, take a break. Don't think about programming at all in that break, that's important. 1. If that doesn't work either, start looking into other roles/domains and what might suit your background and strengths. As I mentioned earlier, may be you are ready for the change :)