That Remote Life: An IT Manager’s Perspective / Chapter 1 Part 3

Wayne Armstrong • April 5, 2021
Connect with us

Chapter 1/PART 3: Routine

The backbone of every professional life is routine. It’s how we grow, it’s the lattice in which we weave in the planned and random events of our days, months and years. But routine is also, in many ways, the reason why we are not so agile with our lives.

The comfort that routine provides us is often subconscious and goes unnoticed, but to truly see it’s effect on your life, remove it, and watch how affected you are.

A mother’s wisdom is sometimes never clear, almost cryptic in ways and can seem rudimentary at first, but it’s designed to lay a seed of thought in which you use to come to your own understanding. It is an age-old way of giving advice and understanding without the complication of explaining, because in life some knowledge has to be arrived at and can’t be just given, and often the most valuable knowledge is the former.

Unlike my poor brother, I was lucky enough to never have to study in my room as a child, I was quite able to fail my tests without the effort (jk).

So the only reason why I was in my room when I was young was to simply sleep. I have trained my body and mind my whole life to feel sleepy or want to sleep if in my room long enough. The routine of going to bed had programmed me to feel sleepy.

In my adult life I have trained my mind and body to feel and act in certain ways in certain incidents based off the location I was or the activity I’m doing. The loss of the state of mind that commuting to work and then working through the day was the reason I could not function correctly when I was sitting at home, in front of the computer, where I normally end my days. The effect was startling and without being overly dramatic, it was shining a light on not only the issue I was having but the effect of routine on the rest of my life.

For my mother, it was a funny question to her because it didn’t matter what her location was, or where she worked, or how she dressed or the state of mind she was in, because she was our mother, it was “who” she was. And this is who I am. Thanks MA!

What in my life has the comfort of routine stopped me from doing? What will happen if other routines are taken away from us? Can I live without routine? Even worse, as I was going through this almost cathartic “episode”, I started in a new position as an expected leader. Here I saw the same and in some cases, worse effects in my company, my team, my extended family.

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts