In my circles it is called Resume Driven Development. My favorite case was when someone moved a single component from ground into a lambda.. that called back

In my circles it is called Resume Driven Development. My favorite case was when someone moved a single component from ground into a lambda.. that called back down to a ground webservice anyway. But hey, they were able to add AWS Lambda to their resume, right? I came on board after the guy left, got props from the business by 'lowering our cloud spend' when I ripped the lambda back out.