| Thanks for this comment; it's made me think a bit. I read somewhere that "burnout is inverse of purpose" - as in, do I feel purpose in what I'm doing? which I think ties in a little bit with "is the problem space interesting" a problem is only worth solving if there's a reason to solve it, which sort of becomes what my issue is about. I think I've come to the same conclusion that while I'm annoyed, it's not at the success or the size of the company; I think there's just been a change in how the relationship between the team and the product exists. Much like what you've touched on, I've realized the fun and spark isn't there. What used to be "Go physically watch the customer interact with the product; what's a pain point we can fix?" has become "Here's a list of 40 demands that the customer wants yesterday" and that makes it not worthwhile for me. Neither fun nor interesting. I'm going to dabble with spending time doing my own side projects that I can get the "purpose" from, and see if I can achieve both the paycheck and the purpose by balancing that time effectively. If it doesn't work out for either of us; then it's no worry, I was half in the mind to change jobs anyway. But thanks for helping me put this into more thoughts and words. It's helpful to experiment with the ideas but I think you're correct; the tech stack has nothing to do with it (for me, at this moment). (am jealous of working with Clojure though; that always looks fun.) |