Lessons Learned from Writing Over 300k Lines of Infrastructure Code
All of the points are very valid and valuable. But by reading only this post, you will have basically no idea how to go ahead and do all these things. You have to scour the internet, and collect every blog post and video ever produced on the subject, and intone them all, and start experimenting, and just sort of create your own version of what these things are.<p>I&#x27;m going to interviews right now where people are trying to hire a &quot;Senior DevOps Engineer&quot;. They seem to think hiring this somewhat low-level employee will magically imbue their organization with DevOps principles, and suddenly everything will be cheaper and faster. I tell them it may take them 2 years to build a solid DevOps practice, assuming they do everything right, and they frown. Why can&#x27;t we just have the DevOps right now? To that I reply, go hire a company that specializes in DevOps. And again they frown.<p>I don&#x27;t think it should be this hard. I think we can consolidate all the important knowledge and pre-packaged work, collaboratively, to empower teams to actually get shit done quicker and better. I think we can make it so nobody ever has to go through the painful process of learning by trial and error ever again. And, of course, I think it should all be free. So I&#x27;ve started a wiki, and I hope I can convince a few more people to help contribute content.<p>GruntWork, I love what you&#x27;re doing, but I&#x27;m also hoping to make your business obsolete. :)