Not myself, but I used to work for a company where there wasn't much of any front-end development experience (almost all were usual CS grad dotnetter/ex-java ty

Not myself, but I used to work for a company where there wasn't much of any front-end development experience (almost all were usual CS grad dotnetter/ex-java types), and quite unfortunately, and almost unbelievably, they made the wrong decision both ways, in a short space of time - they bought when they should have built and built when they should have bought (or used open-source packages). So, due to the lack of front-end exp (a while before I joined), they chose to buy the license for a moderately well-known UI component library to heavy-lift a big front-end rewrite. Well, due to same inexperience, there was no due diligence done and it turned out said component library had tonnes of bugs, wasn't easily extendable, had no real Typescript support, and on and on. The product suffered immensely for years, but dev leadership I think took on a sucken cost/hopeless mentality. Years later, just before I joined, they chose to try and do something about it and pivot (I suppose as some political recoil), deciding to have a go at creating their own UI components and gradually strangler-pattern the existing external UI library. However, leadership thought themselves and the other CS grad dotnetter/java types could "learn on the job", so they didn't hire ANY devs with real experience, i.e. JS, TS, React/Angular/whatever, build tools, general front-end best practices, anything! Fast-forward half a year and there is already even more bugs, a growing mountain of tech debt, etc. This is when i roughly joined, as their first developer with (back then) a couple years of f/e experience. Took me around a year to start turning around the general careless culture the business took towards it's f/e dev work, and argued for more learning, adoption of industry norms, craftsmanship, and all that jazz. It's all in my rear view mirror now, but wow was that an interesting time.