There are plenty of ghosts in woodworking, some will ruin the piece you're making, and some will ruin your day and send you to the hospital :) How long have yo

There are plenty of ghosts in woodworking, some will ruin the piece you're making, and some will ruin your day and send you to the hospital :) How long have you been at this? As in, is this frustration with the org / current tech stack, or is it maturity and moving past just pushing bits around? The JS ecosystem is notorious for what you describe - piles of busywork nonsense for its own sake, wheels regularly reinvented. I do some UI work, I manage to stave off 99% of the bull by using vanilla JS, vue, functional css and absolutely no build chains, no npm, no node. And for the love of all that is holy, keep JS out of the backend, only use it where you have to (ie, the browser). It sounds like your org isn't that well organized. Perhaps it's not a career change, but a place-of-work change that's in the cards? Making a living as a woodworker, a tradesperson or a farmer is -hard work-.