Update README.md

README.md

@@ -1,4 +1,58 @@
-
+<p>"At its essence,&nbsp;<a href="https://en.wikipedia.org/wiki/DevOps" target="_blank" rel="nofollow noopener"><strong>DevOps</strong></a>&nbsp;is a culture, a practice, a&nbsp;<a href="https://en.wikipedia.org/wiki/Philosophy" target="_blank" rel="nofollow noopener">philosophy</a>."</p>
+<p><strong>Introduction</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<p><strong>DevOps</strong>&nbsp;expertise is in high demand. Job postings with "DevOps" in a title or keyword are sprouting up everywhere. DevOps is an&nbsp;<strong>enterprise</strong>&nbsp;software development phrase emerging from combination of IT teams, process and products to enable the&nbsp;<a href="https://en.wikipedia.org/wiki/Continuous_delivery" target="_blank" rel="nofollow noopener"><strong>continuous delivery</strong></a>&nbsp;of value to end users. It is a firm bond between&nbsp;<strong>development</strong>&nbsp;and<strong>&nbsp;operations</strong>&nbsp;that emphasizes a shift in mindset, better collaboration, and tighter integration and aims to create a culture and environment where building, testing, and releasing&nbsp;<a href="https://en.wikipedia.org/wiki/Software" target="_blank" rel="nofollow noopener">software</a>&nbsp;can happen rapidly, often, and more reliably, so&nbsp;<a href="https://en.wikipedia.org/wiki/Organization" target="_blank" rel="nofollow noopener">organization</a>s can solve critical issues quickly, and better serve their customers and compete more effectively in the market.</p>
+<p>&nbsp;<strong>What is DevOps?</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<p>"A&nbsp;<strong>software development method</strong>&nbsp;formed out of a fundamental need that stresses communication, collaboration and integration between software developers and&nbsp;<a href="https://en.wikipedia.org/wiki/Information_technology" target="_blank" rel="nofollow noopener"><strong>IT</strong></a>professionals."&nbsp;<strong>DevOps</strong>&nbsp;could be explained simply as operations working together with&nbsp;<a href="https://en.wikipedia.org/wiki/Engineer" target="_blank" rel="nofollow noopener">engineer</a>s to get things done faster in an&nbsp;<a href="https://en.wikipedia.org/wiki/Automation" target="_blank" rel="nofollow noopener">automate</a>d and repeatable way.</p>
+<p>&nbsp;<a href="https://en.wikipedia.org/wiki/History" target="_blank" rel="nofollow noopener"><strong>History</strong></a><strong>&nbsp;of DevOps</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<p>At the 2008&nbsp;<strong>Agile&nbsp;</strong><a href="https://en.wikipedia.org/wiki/Toronto" target="_blank" rel="nofollow noopener"><strong>Toronto</strong></a><strong>&nbsp;conference</strong>, Andrew Shafer and&nbsp;<strong>Patrick Debois</strong>&nbsp;introduced the term in their talk on "<strong>Agile Infrastructure</strong>". Since 2009, the DevOps term has been steadily promoted based on a simple philosophy &mdash; business works best when efforts being coordinated and collaborative &mdash; and brought into more mainstream usage through a series of "<strong>DevOpsDays</strong>", which started in&nbsp;<a href="https://en.wikipedia.org/wiki/Belgium" target="_blank" rel="nofollow noopener">Belgium</a>&nbsp;and has now spread into&nbsp;<a href="https://en.wikipedia.org/wiki/World_Wide_Web" target="_blank" rel="nofollow noopener">Web</a>-enabled sphere to resolve the conflict between the software developers and the operations teams when it comes to getting great work done quickly. In recent years, more tangential DevOps initiatives have also evolved, such as&nbsp;<strong>OpsDev</strong>,&nbsp;<strong>WinOps</strong>, and&nbsp;<strong>BizDevOps</strong>&nbsp;to encourage the&nbsp;<a href="https://en.wikipedia.org/wiki/Communication" target="_blank" rel="nofollow noopener">communication</a>&nbsp;between software developers and IT Operations to increase the speed at which&nbsp;<a href="https://en.wikipedia.org/wiki/Application_software" target="_blank" rel="nofollow noopener">application</a>s being delivered.</p>
+<p>&nbsp;<strong>Benefits of DevOps</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<p><strong>The technical benefits include:</strong></p>
+<ul>
+<li>Continuous software delivery</li>
+<li>Less complexity to manage</li>
+<li>Faster resolution of problems</li>
+</ul>
+<p>&nbsp;<strong>The cultural benefits include:</strong></p>
+<ul>
+<li>More productive teams</li>
+<li>Higher employee engagement</li>
+<li>Greater professional development opportunities</li>
+</ul>
+<p>&nbsp;<strong>The business benefits include:</strong></p>
+<ul>
+<li>&nbsp;Faster&nbsp;<strong>delivery</strong>&nbsp;of features</li>
+<li>More stable operating environments</li>
+<li>Improved communication and collaboration</li>
+<li>More time to innovate (and not fix / keep up)</li>
+</ul>
+<p>&nbsp;<strong>Features of DevOps</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<ul>
+<li><strong>Source control:</strong>&nbsp;Software developers need to safely store their code and keep track of&nbsp;<a href="https://en.wikipedia.org/wiki/Source_code" target="_blank" rel="nofollow noopener">source-code</a>&nbsp;history and&nbsp;<a href="https://en.wikipedia.org/wiki/Software_versioning" target="_blank" rel="nofollow noopener">version</a>s. For this reason alone, source control is of critical importance.</li>
+<li><strong>Issue tracking system:</strong>&nbsp;An issue&nbsp;<strong>tracking&nbsp;</strong>system allows everyone involved to track current issues, estimates, and deadlines.</li>
+<li><strong>Build system:&nbsp;</strong>The build system supports&nbsp;<a href="https://en.wikipedia.org/wiki/Continuous_integration" target="_blank" rel="nofollow noopener"><strong>continuous integration</strong></a>&nbsp;by building the software, running unit and integration tests, deploying to the integration environment, and performing any other automated checks defined for new versions of the software.</li>
+<li><strong>Monitoring system:</strong>&nbsp;Monitoring systems continuously track all autonomous systems within the DevOps environment, notifying necessary maintenance staff if a system failure occurs.</li>
+<li><strong>Communications system:</strong>&nbsp;The constant exchange of&nbsp;<strong>information</strong>&nbsp;is important so email, wiki, and a real-time chat system being enabled for effective communication and collaboration among all members of the project team.</li>
+<li><strong>Integration environment:</strong>&nbsp;The integration environment hosts all the virtual machines that make up our DevOps environment</li>
+<li><strong>Code review system:</strong>&nbsp;To make sure software quality, every line of code being reviewed by a experienced developer. The practice of reviewing code also accelerates career growth and learning.</li>
+<li><strong>Documentation system:</strong>&nbsp;Regrettably,&nbsp;<a href="https://en.wikipedia.org/wiki/Documentation" target="_blank" rel="nofollow noopener">documentation</a>&nbsp;often remains an afterthought in production software projects. To ensure that documentation being written throughout the project, an automated system being developed to allow developers to write documentation easily, along with source code.</li>
+</ul>
+<p>&nbsp;<strong>DevOps Goals</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<ul>
+<li>Improve deployment frequency</li>
+<li>To make faster time to market</li>
+<li>Less failure rate to new releases</li>
+<li>Short lead time between fixes</li>
+<li>Improve mean time to recovery</li>
+</ul>
+<p>&nbsp;<strong>Is DevOps a good career?</strong></p>
+<p><strong>________________________________________________________________________________________________________________</strong></p>
+<p><strong>DevOps practitioners</strong>&nbsp;are among the highest paid IT professionals today, and the market demand for them is growing rapidly because organizations using DevOps practices are overwhelmingly high-functioning to deliver IT services that offer value to the business. According to a study on the application&nbsp;<a href="https://en.wikipedia.org/wiki/Economy" target="_blank" rel="nofollow noopener">economy</a>&nbsp;and the role of DevOps, 88% of enterprise IT organizations and&nbsp;<strong>LOB</strong>&nbsp;(<a href="https://en.wikipedia.org/wiki/Line_of_business" target="_blank" rel="nofollow noopener">line of business</a>) executives already have planned to adopt DevOps sometime within the next five years to accelerate delivery of apps and offer customers with higher-quality software. In the last two years, listings for DevOps jobs at&nbsp;<a href="https://en.wikipedia.org/wiki/Indeed" target="_blank" rel="nofollow noopener">Indeed.com</a>&nbsp;increased 75 percent. On&nbsp;<a href="https://en.wikipedia.org/wiki/LinkedIn" target="_blank" rel="nofollow noopener">LinkedIn.com</a>, mentions of DevOps as a skill increased 50 percent. In a recent survey by&nbsp;<a href="https://en.wikipedia.org/wiki/Puppet_(software)" target="_blank" rel="nofollow noopener"><strong>Puppet</strong></a><strong>labs</strong>, half of their 4,000-plus respondents (in more than&nbsp;<strong>90 countries</strong>) said their companies consider DevOps skills when hiring.</p>
 </br>
 <p><strong>60 Must Read Books To Take Your DevOps Skills To The Next Level</strong></p>
 <p><strong>________________________________________________________________________________________________________________</strong></p>