I know how to do most all of it but...there's a lot to do and keep up with that other people are always actively doing/researching in a huge community in a monu

I know how to do most all of it but...there's a lot to do and keep up with that other people are always actively doing/researching in a huge community in a monumental way and have docs for it lying around that are quite comprehensive that allows a team to start working on well-tested code and methodologies together swimming in the same direction without huge debates or wacko decision making from a lone-wolf developer. To have some random first-guy on a team decide his/her own framework from scratch is the usual death knell or redo of the project and creates a bad environment of "my code is truth" type thing without docs or with some terrible ReadMe that's out of date. A mark of a project that is easier to work on (productive) has tons of StackOverflow related search results on the tech / stack / framework it's being used on and typically will have one of the giant tech companies actively investing in it.