When you learn math, there’s a clear, linear, progression. Arithmetic, then algebra, trigonometry right after, pre-calculus, calculus, and then infinite diverging paths of continued suffering. The body of knowledge that compromises cloud computing does not, unfortunately, work this way. Yet, many cloud computing courses, regardless of the certificate that acts as the end-goal, are structured like this. “First, we must learn IAM, then, RDS, after which comes EC2…” I am here to argue against this methodology. Breadth, not depth, of every relevant service, should, at the very least, be the starting point for the green learner of any cloud computing ecosystem. Why? Because cloud computing is not math.

This is not a blog post detailing why I am tired of the endless, never-ending, scroll that is “the algorithm”. This is a blog post detailing every method I have tried to remove technology from my sphere that has sought to monopolize my attention through design that promotes addiction. How you define “addiction” in this case is irrelevant, at least to me, because that is purely personal. That’s why this post is titled “How I Cut Addictive Technology Out Of My Life”.