The parent was commenting on a broken framework, something that should be an anathema in any shipping product, and around spending (wasting) time determining th

The parent was commenting on a broken framework, something that should be an anathema in any shipping product, and around spending (wasting) time determining that the API itself was faulty. Replacing the faulty API call took two hours. But to follow onto to your point, it's also the case that the younger programmers can need a decade or more to make enough mistakes; to variously learn what the older programmers already know about various fundamentals of the programming and product-creation business. And to extend your point, it's been my experience that having a team of younger programmers is just as big a headache and as big a mistake as having a team comprised entirely of older programmers. A mix works better, as the younger folks teach the older folks and they bring knowledge of new technologies and volumes of enthusiasm, and the older folks can teach the younger programmers about temperance, testing, productization and business in general.