Clearly you automate the heck out of everything you work on and I imagine you work a lot with bare metal. What challenges have you faced regarding automating bare metal resources? What tools have you used to help with those challenges? With different hardware vendors having widely varying interfaces for automating their products, how do you manage those interfaces to provide the same end-result across the board? Do you implement automated testing or CI of the physical provisioning process? If so, what does that look like?

It seems yarn is more focused on project sandboxing like bundler or virtualenv versus package management like rubygems or pip. This is made evident by design around yarn global * and lack of the same configurability currently present in the rival npm client. Is this inferred roadmap intentional? What are your thoughts on focusing upon the sandboxing problem versus an overall better client for npmjs.org?