> As an engineer with more than 15 years professional experience, my definition of "junior shit" would be thinking you can hand-roll a foundation or framework

> As an engineer with more than 15 years professional experience, my definition of "junior shit" would be thinking you can hand-roll a foundation or framework better than something that already exists. You're not wrong, although to be fair, it isn't always about hand-rolling a framework. Sometimes it's just about experience and knowledge about which existing framework might best fit a given use case (without unnecessary bloat) as opposed to just choosing the latest "ooh shiny!" bloated buzzword framework to build upon purely because it's new and trendy this week. Although some use cases do call for the "bloated" framework, because feature requirements demand using a framework that provides those features. Again, experience and knowledge can inform whether this is necessarily the case, and one should obviously avoid hiring any applicant who does not see a valid need for the choice of framework/toolchain when it was chosen for good reason.