<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>blog.bytester.net</title>
    <link>http://blog.bytester.net/</link>
    <description>Recent content on blog.bytester.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Feb 2024 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://blog.bytester.net/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Mobile Test</title>
      <link>http://blog.bytester.net/posts/mobile-test/</link>
      <pubDate>Tue, 27 Feb 2024 00:00:00 +0000</pubDate>
      
      <guid>http://blog.bytester.net/posts/mobile-test/</guid>
      <description>test from mobile testing whether content pushes from a mobile commit</description>
    </item>
    
    <item>
      <title>The Ownership Formula</title>
      <link>http://blog.bytester.net/posts/ownership-formula/</link>
      <pubDate>Wed, 02 Feb 2022 00:00:00 +0000</pubDate>
      
      <guid>http://blog.bytester.net/posts/ownership-formula/</guid>
      <description>Teams managing complex IT infrastructure are often made up of a combination of full time employees (FTE&#39;s) and contigent workers (a.k.a, contractors). Teams that have too many contractors and not enough FTE&#39;s are often ineffective. Teams that have too many FTE&#39;s and not enough contractors are effective but expensive. What is the right balance? I got to thinking whether or not I might be able to come up with an equation that could model the effectiveness of teams that are blended with FTE&#39;s and contractors and came up with a model which I&#39;ll explain as we go.</description>
    </item>
    
    <item>
      <title>The High Cost of Cloud Talent</title>
      <link>http://blog.bytester.net/posts/cloud-talent/</link>
      <pubDate>Mon, 31 Jan 2022 00:00:00 +0000</pubDate>
      
      <guid>http://blog.bytester.net/posts/cloud-talent/</guid>
      <description>Talented cloud engineers are expensive and it&#39;s getting worse during the Great Resignation. As more and more enterprise workloads move to cloud hosting it&#39;s approaching a tipping point where this has become a serious problem. In addition to being expensive, cloud talent is very hard to find as there aren&#39;t enough people out there with the skills to satisfy the demand. Therefore, it is obvious that our current trajectory is barely sustainable and we need to figure out how to curtial the future demand and fund the current demand.</description>
    </item>
    
    <item>
      <title>ITSM and Cloud</title>
      <link>http://blog.bytester.net/posts/itsm-and-cloud/</link>
      <pubDate>Tue, 11 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>http://blog.bytester.net/posts/itsm-and-cloud/</guid>
      <description>This document covers the basics of an IT service management (ITSM) solution for the purposes of incident management, change control, and inventory management. The objective is to prove that such a system is critical to a business and equally important for environments that traditionally shun these systems such as smaller organizations and organizations with cloud workloads.
 Introduction Change Control Concepts  Why Change Control is Necessary How to Implement a Basic Change Control System   Incident Management Concepts  Why Incident Management is Necessary How to Implement a Basic Incident Management System   Inventory - A Critical Requirement for Effective Change and Incident Management  Implementing a Basic Inventory System Physical Inventory Virtual and Cloud Inventory Asset Inventory For Cloud  Asset Inventory - Cloud Systems  Tag Challenges Regarding Modern Automated Systems Management  Infrastructre as Code Challenges CI/CD Challenges Conclusion       Asset Inventory - Logical Business Constructs   Conclusion References  Other References    Introduction Any system of sufficient complexity requires humans to compartmentalize.</description>
    </item>
    
    <item>
      <title>About This Blog</title>
      <link>http://blog.bytester.net/posts/about-blog/</link>
      <pubDate>Wed, 11 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>http://blog.bytester.net/posts/about-blog/</guid>
      <description>This blog is generated by Hugo and is stored on AWS as a static site on S3. All of the code mentioned here can be found on GitHub for those who want to follow along.
Background I had used Google Blogs quite some time ago but never really liked the interface or image management. Then for an internal documentation site at work we have been using Jekyll and I really liked the dead simple vi &amp;gt; git commit &amp;gt; see content workflow so I set out to do something similar for my personal site.</description>
    </item>
    
    <item>
      <title>About This Site</title>
      <link>http://blog.bytester.net/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://blog.bytester.net/about/</guid>
      <description>I&#39;m a technologist working with AWS/Azure in the Enterprise Cloud space that&#39;s performaed several roles such as operations engineer, operations manager, architect, and architecture manager.
Background I have a background as a sysadmin and network administrator that transitioned into a devops role managing infrastructure as code and CI/CD pipelines for a marketing company.
From there I transitioned to managing operations for a cloud governance product for a large company&#39;s internal business unit customers.</description>
    </item>
    
  </channel>
</rss>