I think reality is more complicated than a one size fits all approach. It's going to be specific to your org, your project, the stage it's at etc. To add to that, the right thing to do is often in flux.
Dedicated capacity is necessary, as is embedding. Not always at the same time or in that order. That's where only the information found inside the walls of your organisation can help you decide what is necessary to solve your problem.
Hahah. Reminds me of the time I used to work at a place where the software's demo company was called ISIS and that didn't used to be a big deal until ISIS itself became a thing. Part of our solution contained a web-portal we could up-sell to our clients that their end users could manage their accounts through etc. Anyway I remember one fun afternoon hacking graphics of ISIS the terrorist organization into the web-portal of the demo org and showing it around the office for laughs. It never made it to a customer site thankfully and it was pretty funny at the time but my boss told me to cut it out pretty quick just in-case hahaha.
sounds like the beginnings of either burnout, depression or both. I'm in a job that's not quite demanding enough at the moment and it caused me to fall into a depression. It's good to catch it in time to do something about it.
Same here. I would add if you experience what the OP does combined with looking around the house every day and seeing piles of unfolded washing and dirty dishes waiting for you that fill you with existential dread every time you look at them while you quietly ignore them and go back to whatever it is you're excited about at the moment then seek an evaluation.
I use containers in production and for local development dependencies but for exactly these reasons I run the application locally via the IDE like I always have, with the option to run it locally via Docker for the times I need to dip into making sure specific bits run there fine. So, I still have all those nice things.
My previous team lead hated JIRA and would frequently rail on it during our agile ceremonies. Me who likes coming up acronyms would refer to it as that "Janky Irritating React App" during our ceremonies as a result. Good times.
