<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>#Jinhendrix-Sore on Jinhendrix Documentation</title>
    <link>/tags/%23jinhendrix-sore/</link>
    <description>Recent content in #Jinhendrix-Sore on Jinhendrix Documentation</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/%23jinhendrix-sore/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DevOps Engineering</title>
      <link>/posts/devops-engineering/</link>
      <pubDate>Sat, 20 Dec 2025 00:00:00 +0000</pubDate>
      <guid>/posts/devops-engineering/</guid>
      <description>&lt;h3 id=&#34;devops-engineering--delivery-mentality&#34;&gt;DevOps Engineering — &lt;em&gt;Delivery Mentality&lt;/em&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Focus: &lt;strong&gt;Speed + reliability of change&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Strength: CI/CD, pipelines, collaboration between dev and ops&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Approach:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Automate builds, tests, deployments&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Reduce friction between teams&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Question asked:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;“How do we ship changes safely and faster?”&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Site Reliability Engineering</title>
      <link>/posts/site-reliability-engineering/</link>
      <pubDate>Sat, 20 Dec 2025 00:00:00 +0000</pubDate>
      <guid>/posts/site-reliability-engineering/</guid>
      <description>&lt;h3 id=&#34;site-reliability-engineering--reliability-by-design-mentality&#34;&gt;Site Reliability Engineering — &lt;em&gt;Reliability-by-Design Mentality&lt;/em&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Focus: &lt;strong&gt;System behavior over time&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Strength: Monitoring, automation, self-healing systems&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Approach:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Encode operational knowledge into code&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Measure, detect, and react automatically&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Minimize toil&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Question asked:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;“How do we make the system fix itself and page humans only for the unknown?”&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;1-overview&#34;&gt;&lt;strong&gt;1. Overview&lt;/strong&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Site Reliability Engineering (SRE) is a discipline that applies &lt;strong&gt;software engineering principles to infrastructure and operations&lt;/strong&gt;. The goal is to create &lt;strong&gt;reliable, scalable, and automated systems&lt;/strong&gt; by encoding operational knowledge into software.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Systems Administration</title>
      <link>/posts/systems-administration/</link>
      <pubDate>Sat, 20 Dec 2025 00:00:00 +0000</pubDate>
      <guid>/posts/systems-administration/</guid>
      <description>&lt;h3 id=&#34;systems-administration--operational-mentality&#34;&gt;Systems Administration — &lt;em&gt;Operational Mentality&lt;/em&gt;&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Focus: &lt;strong&gt;Keeping systems running&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Strength: Deep understanding of OS, networking, services, and failure modes&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Approach:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Manual intervention&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Scripts and cron jobs&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Human-driven detection and recovery&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Question asked:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;“How do I fix this when it breaks?”&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;1-introduction--purpose&#34;&gt;&lt;strong&gt;1. Introduction / Purpose&lt;/strong&gt;&lt;/h2&gt;&#xA;&lt;p&gt;This documentation provides comprehensive guidance for managing cloud infrastructure, Linux servers, and Windows Server environments.&lt;/p&gt;&#xA;&lt;p&gt;It is intended for IT staff, and Systems Administrators alike.&lt;/p&gt;&#xA;&lt;h2 id=&#34;2-environment-overview&#34;&gt;&lt;strong&gt;2. Environment Overview&lt;/strong&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Systems and IT infrastructure generally operate under three primary environments: &lt;strong&gt;Development&lt;/strong&gt;, &lt;strong&gt;Testing (Staging)&lt;/strong&gt;, and &lt;strong&gt;Production&lt;/strong&gt;. Each environment serves a specific role in the system lifecycle and must be managed not only for functionality, but also for &lt;strong&gt;cost efficiency, security, and operational stability&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
