I do a little bit of a lot of things. Some of those things are code. I enjoy thinking about how the world and technology interact, and how technology affects the way people interact with each other.
Keff stated this in other comments, but I'll second it and back them up: you were a victim of bad leadership, not burnout. Let me qualify the rest of my response by clarifying - I'm not a professional dev. (maybe in the future) I'm in management in a non-tech sector. However, a lot of the same business lessons apply across the board. I've learned this through years of integrating with tech culture and writing a lot of code myself.
From the limited writeup given, I can offer these points.
As leaders, your former employers had a responsibility to understand and attempt to remove any blockages to your productivity. The job of a manager is to orchestrate work and to make it as smooth as possible for the people doing the work, and they weren't doing that.
The equipment and dev enviroment issue might have been bigger than just your request. There might have been constraints around security, available resources, budgeting concerns, etc. However, this should have been a communication point between you and your leaders. Their transparency could have been a portal to let you in on understanding and maybe even solving these issues.
When they switched domain focus, they probably picked up on your dissatisfaction. What they didn't do from what I read above, is talk to you about it. Instead they let a valuable resource go idle, with little to no direction on what was needed or expected. This is poor form on their part.
What lessons can you take away from the experience at the old company for yourself? Is there anything you did wrong or would have done differently? I'm not saying this is the case, but that self reflection can be very valuable moving forward.
Regarding your new position: You have to remember that the new company is not the old company. You might have some hesitation speaking up, but remember that you also have a unique history and thus unique experience that can contribute to the conversation. If they didn't want to hear what you have to say, they wouldn't have hired you. Be nice when you chime in, and maybe find a watercooler conversation where you can open up to your new leaders about your experience and history. If they don't understand and don't encourage you to be a part of your current team, you're still in the wrong place. BUT unless you speak up, they won't know where you stand. They could be interpreting your hesitation as something else, possibly incorrectly, and since you are new to the company they won't have any context to know otherwise.
Jeremy Friesen did a great job of outlining my thoughts on personal growth and how to analyze your current situation, so I'll say "Well done" to Jeremy and refer you to that comment. The only thing I can add to what Jeremy wrote is this: It will take a moment of courage for you to take the next steps to move past this problem, but it's worth it.
I'm at a point in my career that I'm tasked to lead leaders. I've learned a lot through trial and error (mostly error, no joke), and I've tried to study leadership whenever I can. For what it's worth, in my opinion, I wouldn't want to work for the founder of your old company from the standpoint of an employee, and I wouldn't hire them from the standpoint of a leader and manager. I think you dodged a bullet by leaving.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Keff stated this in other comments, but I'll second it and back them up: you were a victim of bad leadership, not burnout. Let me qualify the rest of my response by clarifying - I'm not a professional dev. (maybe in the future) I'm in management in a non-tech sector. However, a lot of the same business lessons apply across the board. I've learned this through years of integrating with tech culture and writing a lot of code myself.
From the limited writeup given, I can offer these points.
Jeremy Friesen did a great job of outlining my thoughts on personal growth and how to analyze your current situation, so I'll say "Well done" to Jeremy and refer you to that comment. The only thing I can add to what Jeremy wrote is this: It will take a moment of courage for you to take the next steps to move past this problem, but it's worth it.
I'm at a point in my career that I'm tasked to lead leaders. I've learned a lot through trial and error (mostly error, no joke), and I've tried to study leadership whenever I can. For what it's worth, in my opinion, I wouldn't want to work for the founder of your old company from the standpoint of an employee, and I wouldn't hire them from the standpoint of a leader and manager. I think you dodged a bullet by leaving.