The writing of this article is a mistake. I don't have anything terribly new to add above and beyond what others have already said, but suffice to say this is a bad article that provides us no insight or meaningful suggestions and demonstrates a lack of experience and understanding throughout the industry.
There is a function many (though not all) software teams need whereby someone understands customer needs, prioritizes them, and translates them into something that can be worked on by developers. We call that role "Product Manager". Do you strictly need an MBA who has some specific certifications to do that? No, of course not. A very strong UX researcher could potentially do it. A very strong engineering lead could potentially do it. But for many products, it requires a significant time investment in understanding the problem space, guiding a UX/UI research/design team iterating through solutions, and documenting it in such a way that a dev team could approach it.
As someone else commented, the article is just "Hiring bad leaders is bad".
Do you look back over these notes and find them useful? Perhaps it's my ADD or the
nature of the software products I create, but for the past 20 years of my career, I've never kept significant notes and never found myself missing them. I'm wondering if there's something I don't know that I don't know here.
Yeah, that's what I suspected. Not that Reddit hasn't been having shit moderation, but this looks like it makes sense to be flagged as spam. An overzealous misguided user who desperately looking to get involved. Intentions may have been good, but execution was poor.
IMO the better way to do the same thing would have been to write a post specific to each tool addressing how it could integrate with Lemmy.
I don't know who originally said it but "If you're not using a framework, you're building a framework". This repo even has the following caveat:
(2) These usually end up becoming a custom micro-framework, thereby questioning why you didn't use one of the established and tested libraries/frameworks in the first place.
That said, I don't hate it. For quite some time, I've taken the stance that a web development team needs an opinionated framework, but it's fine for it to be a bespoke creation rather than off-the-shelf. The biggest value of choosing React, Vue, Svelte, etc is, in my opinion, less about it doing the heavy lifting for you with the DOM and more about adopting an established valid opinion to guide the team's development.