2024-11-22 13:12:19 +00:00
3 changed files with 0 additions and 75 deletions
--- a/gemlog/the-end-of-something-and-the-start-of-something-else.gmi
+++ b/gemlog/the-end-of-something-and-the-start-of-something-else.gmi
@ -1,41 +0,0 @@
 Yesterday I turned in my (employee) badge and gun work iPhone and left the office I've occupied for nearly six years[1] for the last time.
 => https://social.lol/@jbowdre/113132004724346487 1: left the office I've occupied for nearly six years
 Working IT at the corporate level of a large conglomerate was certainly interesting. The sheer scale of the environment I helped to manage was staggering - thousands of virtual machines running on hundreds of hypervisor hosts at scores of sites around the globe. The corporation grew through acquisition so there was a constant influx of new businesses and sites, each bringing their own semi-unique technical debt to add to the corporation's. Wrangling that felt like such an uphill battle at times.
 That scale also gave me a lot of opportunities to grow and explore new skill trees. I joined the company in a Windows server + virtualization administrator kind of role, but was soon tasked with the implementation of VMware vRealize Automation (now "Broadcom VMware Aria vRealize vAutomation", or something) to streamline and automate the process of deploying new virtual servers. I had a lot of fun building that out, and wrote a number of blog posts[1] about the things I learned along the way.
 => https://runtimeterror.dev/tags/vra 1: a number of blog posts
 From there I shifted to a more DevOps-y role with an emphasis on automation, containerization, infrastructure-as-code, and other such modern approaches to help reduce toil. Some of my highlights:
 - I used Packer[1] to build hardened virtual machine templates and created a CI/CD pipeline[2] to automagically create freshly-updated templates every week.
 => https://www.packer.io/ 1: Packer
 => https://runtimeterror.dev/automate-packer-builds-github-actions/ 2: created a CI/CD pipeline
 - I built a solution to sync those templates out to the remote datacenters and smaller sites so they would be ready for consumption when needed.
 - I learned how to use SaltStack[1] for configuration management of Linux servers, and I created a *ton* of Salt content for maintaining a complex development environment.
 => https://docs.saltproject.io/en/master/topics/tutorials/walkthrough.html 1: SaltStack
 - I learned about using Terraform[1] for deploying and managing resources, and used that knowledge for managing an on-premise Vault Enterprise[2] cluster.
 => https://developer.hashicorp.com/terraform 1: Terraform
 => https://developer.hashicorp.com/vault 2: Vault Enterprise
 - I wrote a Go app to streamline connecting Okta organizations with the Org2Org integration[1]; a process which took hours to do when I first inherited the task took just minutes when I was done with it. (Oh, and I learned (and continue to learn) Go.)
 - I worked with development teams to containerize their firmware build tools which required very specific (no-longer-supported) Linux versions, and integrated those container images with their build pipelines to improve the performance, reliability, and security of the builds.
 => https://developer.okta.com/docs/guides/secure-oauth-between-orgs/main/ 1: connecting Okta organizations with the Org2Org integration
 I also made time to mentor some other admins and help them grow their skills. It was really rewarding to see them able to pick up and run with the things I shared with them, and I know they will continue to do great things.
 I can confidently (and proudly) say that I left the company much better than I found it, which is pretty cool.
 There were plenty of challenges and frustrations along the way, and the support scope often made it difficult to focus on the big-picture improvements I was working toward, but overall, this was a pretty good job in my book. I'm immensely grateful for the freedom and support my immediate management provided for me to explore new ideas and try new ways of enhancing efficiency across a a global enterprise.
 That all being said, I'm super-excited to start my new job[1] as a platform architect at a *much* smaller corporation on Monday. I'll be able to focus on building cool stuff to help ease development and operations headaches without being tasked with operations tasks of my own. I love solving problems and building solutions, and honestly this role sounds pretty much perfect for me. I can't wait to get started!
 => /i-got-a-new-job/ 1: my new job
 => https://srsbsns.lol/the-end-of-something-and-the-start-of-something-else/ 📡 Originally posted on srsbsns.lol 
--- a/gemlog/the-end-of-something-and-the-start-of-something-else.yaml
+++ b/gemlog/the-end-of-something-and-the-start-of-something-else.yaml
@ -1,4 +0,0 @@
 id: "urn:uuid:ed610853-b8e1-4ed3-86d2-17eb73344a1c"
 title: "The end of something, and the start of something else"
 published: "2024-09-15T01:28:42.263992Z"
 updated: "2024-09-15T01:28:42.263992Z"
--- a/markdown/the-end-of-something-and-the-start-of-something-else.md
+++ b/markdown/the-end-of-something-and-the-start-of-something-else.md
@ -1,30 +0,0 @@
 ---
 title: "The end of something, and the start of something else"
 published: "2024-09-15T01:28:42.263992Z"
 updated: "2024-09-15T01:28:42.263992Z"
 ---
 Yesterday I turned in my (employee) badge and gun work iPhone and [left the office I've occupied for nearly six years](https://social.lol/@jbowdre/113132004724346487) for the last time.
 Working IT at the corporate level of a large conglomerate was certainly interesting. The sheer scale of the environment I helped to manage was staggering - thousands of virtual machines running on hundreds of hypervisor hosts at scores of sites around the globe. The corporation grew through acquisition so there was a constant influx of new businesses and sites, each bringing their own semi-unique technical debt to add to the corporation's. Wrangling that felt like such an uphill battle at times.
 That scale also gave me a lot of opportunities to grow and explore new skill trees. I joined the company in a Windows server + virtualization administrator kind of role, but was soon tasked with the implementation of VMware vRealize Automation (now "Broadcom VMware Aria vRealize vAutomation", or something) to streamline and automate the process of deploying new virtual servers. I had a lot of fun building that out, and wrote [a number of blog posts](https://runtimeterror.dev/tags/vra) about the things I learned along the way.
 From there I shifted to a more DevOps-y role with an emphasis on automation, containerization, infrastructure-as-code, and other such modern approaches to help reduce toil. Some of my highlights:
 - I used [Packer](https://www.packer.io/) to build hardened virtual machine templates and [created a CI/CD pipeline](https://runtimeterror.dev/automate-packer-builds-github-actions/) to automagically create freshly-updated templates every week.
 - I built a solution to sync those templates out to the remote datacenters and smaller sites so they would be ready for consumption when needed.
 - I learned how to use [SaltStack](https://docs.saltproject.io/en/master/topics/tutorials/walkthrough.html) for configuration management of Linux servers, and I created a *ton* of Salt content for maintaining a complex development environment.
 - I learned about using [Terraform](https://developer.hashicorp.com/terraform) for deploying and managing resources, and used that knowledge for managing an on-premise [Vault Enterprise](https://developer.hashicorp.com/vault) cluster.
 - I wrote a Go app to streamline [connecting Okta organizations with the Org2Org integration](https://developer.okta.com/docs/guides/secure-oauth-between-orgs/main/); a process which took hours to do when I first inherited the task took just minutes when I was done with it. (Oh, and I learned (and continue to learn) Go.)
 - I worked with development teams to containerize their firmware build tools which required very specific (no-longer-supported) Linux versions, and integrated those container images with their build pipelines to improve the performance, reliability, and security of the builds.
 I also made time to mentor some other admins and help them grow their skills. It was really rewarding to see them able to pick up and run with the things I shared with them, and I know they will continue to do great things.
 I can confidently (and proudly) say that I left the company much better than I found it, which is pretty cool.
 There were plenty of challenges and frustrations along the way, and the support scope often made it difficult to focus on the big-picture improvements I was working toward, but overall, this was a pretty good job in my book. I'm immensely grateful for the freedom and support my immediate management provided for me to explore new ideas and try new ways of enhancing efficiency across a a global enterprise.
 That all being said, I'm super-excited to start [my new job](/i-got-a-new-job/) as a platform architect at a *much* smaller corporation on Monday. I'll be able to focus on building cool stuff to help ease development and operations headaches without being tasked with operations tasks of my own. I love solving problems and building solutions, and honestly this role sounds pretty much perfect for me. I can't wait to get started!
 => https://srsbsns.lol/the-end-of-something-and-the-start-of-something-else/ 📡 Originally posted on srsbsns.lol