> Are you in the habit of hiring people without experience? I hire people who I believe can produce quality code as part of a team. I've hired people with zero

> Are you in the habit of hiring people without experience? I hire people who I believe can produce quality code as part of a team. I've hired people with zero experience and with 35+ years of experience. I've probably hired somewhere around 200 people. I have no idea how many people I've interviewed. I have both hired people with decades of experience who turned out to be poor hires, and I've hired people without any experience who went on to make critical contributions to billion dollar projects. If your hiring criteria are "has experience with X" you are limiting the size of your hiring pool to people who are heavily invested in "X". That is probably not the most brilliant hiring strategy. For one it means you can never hire people who have newly graduated. > All frameworks will place limitations on how you express yourself. True, but some frameworks will more severely limit your future options and be harder to move away from. The more of you application is affected by the framework, the more expensive it is to move away from it. This is an important reason why the Go community tends to discourage creation and use of large frameworks. I can understand that you are defensive if you have spent years making this investment and someone suggests you have made a poor choice. But I think it would be time well spent to try to understand why many companies are moving away from the "big framework" approach. > I question your judgment [...] That's fine. > It would indicate, to me, your lack of experience in writing or reading code [...] You're free to make that assumption. Even though it makes you look a bit silly since you are making assumptions about something you lack data on.