<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jesse Hunter on Medium]]></title>
        <description><![CDATA[Stories by Jesse Hunter on Medium]]></description>
        <link>https://medium.com/@jwhunter80?source=rss-6ace4a9531e4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Lx5GevhcU9fce3bx</url>
            <title>Stories by Jesse Hunter on Medium</title>
            <link>https://medium.com/@jwhunter80?source=rss-6ace4a9531e4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:26:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jwhunter80/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From the Driver’s Seat to the Cloud: Starting Over at 46: A Personal Journey Series]]></title>
            <link>https://medium.com/@jwhunter80/from-the-drivers-seat-to-the-cloud-starting-over-at-46-a-personal-journey-series-b9bf8f8e0b11?source=rss-6ace4a9531e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9bf8f8e0b11</guid>
            <category><![CDATA[cloud-engineer-academy]]></category>
            <category><![CDATA[aws-basics]]></category>
            <category><![CDATA[aws-cloud]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[starting-over-mid-40s]]></category>
            <dc:creator><![CDATA[Jesse Hunter]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 21:22:37 GMT</pubDate>
            <atom:updated>2026-09-03T21:22:37.649Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 2</h3><p>Last time, I told you how a 46-year-old truck driver decided he was done watching the white lines go by and started studying cloud engineering instead. If you’re just finding me now: no CS degree, just a laptop and a stubborn refusal to believe it’s too late to start over. I’m working through Cloud Engineer Academy under Soleyman Shahir, and this week the curriculum took me somewhere I didn’t expect to enjoy as much as I did: Git, GitHub, and the bones of how real systems are built.</p><h3>Git Isn’t Scary, It’s a Logbook</h3><p>Every trucker keeps a log. Where you’ve been, what time you left, what you were hauling. Git is that, but for code. It doesn’t erase your mistakes — it just records the moment you made them and gives you a clean way to go back.</p><p>The commands that clicked for me first:</p><ul><li>git init — start keeping a log for this project.</li><li>git add — pick up what you want to record.</li><li>git commit -m &quot;message&quot; — write the log entry.</li><li>git status and git log — check where you are and where you&#39;ve been.</li></ul><p>That’s it. That’s 90% of what I needed to stop being afraid of it.</p><h3>GitHub: The Truck Stop Everyone Passes Through</h3><p>If Git is your personal logbook, GitHub is the shared truck stop where everyone parks their logs so other people can see them, borrow from them, or help you fix something at 2 a.m. It’s not the same thing as Git — that distinction took me embarrassingly long to internalize — but they work together.</p><p>Creating my first repository felt like backing into a spot for the first time: nerve-wracking, then suddenly obvious. git remote add origin &lt;url&gt;, then git push, and there it was — my code, sitting in the world, attached to my name. I won&#39;t pretend that didn&#39;t feel good.</p><h3>Access Keys vs. Key Pairs: Two Different Locks</h3><p>This is where I almost drove off the road, metaphorically. The terms sound interchangeable and they are not.</p><p>An <strong>access key</strong> (like an AWS access key ID and secret access key) is closer to a fuel card — a pair of credentials that authenticate a program or a script to make API calls on your behalf. Whoever holds that pair can act as you, programmatically, so you guard it like cash.</p><p>A <strong>key pair</strong>, on the other hand, is the public/private key setup used mainly for SSH — logging into a server itself. Think of it as the physical key to your truck cab: one half stays with you (private key, never shared), the other half sits on the “vehicle” (public key, on the server). You don’t type a password to get in; the two halves have to match mathematically.</p><p>Same word, “key,” two completely different jobs. One authenticates a request. The other authenticates a login.</p><h3>Architecture and Trade-offs: There’s No Free Lunch Lane</h3><p>Every choice in cloud architecture is a trade-off, same as choosing a route: the interstate is faster but tolls you, the back roads are free but slower and you might hit every red light in town. More redundancy costs more money. More speed usually costs more complexity. Simpler systems are easier to maintain but harder to scale. Nobody hands you a perfect answer — you learn to ask “what am I optimizing for right now?” and accept what you give up to get it.</p><h3>Front End vs. Back End: The Dashboard and the Engine</h3><p>Front end is the dashboard — what the driver sees and touches: the buttons, the display, the website a user clicks through. Back end is the engine and drivetrain — the part doing the actual work out of sight: databases, servers, business logic. A beautiful dashboard means nothing if the engine underneath can’t deliver, and the reverse is just as true.</p><h3>Vertical vs. Horizontal Scaling: Bigger Truck or More Trucks</h3><p>When one server can’t keep up, you’ve got two options.</p><p><strong>Vertical scaling</strong> means upgrading the truck — more RAM, a faster CPU, a bigger engine on the same single machine. It’s simple, but there’s a ceiling, and eventually you’re paying luxury prices for marginal gains.</p><p><strong>Horizontal scaling</strong> means adding more trucks to the fleet — spinning up additional servers to share the load. It’s more complex to coordinate, but there’s no real ceiling, and if one truck breaks down, the freight still moves.</p><h3>Load Balancing: The Dispatcher</h3><p>None of those extra trucks matter without a dispatcher deciding who gets which load. That’s a <strong>load balancer</strong> — it sits in front of your fleet of servers and routes incoming traffic so no single one gets buried while others sit idle. Dispatch badly, and you’ve got one exhausted driver and nine parked trucks.</p><h3>High Availability: No Single Point of Failure</h3><p>The whole reason to scale horizontally and load balance in the first place is <strong>high availability</strong> — designing things so no single failure takes the whole operation down. In trucking terms: you don’t run one route through one mountain pass with no backup road. You build in redundancy so a landslide in one place doesn’t stop every delivery in the country.</p><h3>Where I’m At</h3><p>I’m still early. I’m still translating everything into things I already understand from twenty-plus years behind a wheel, because that’s the only way new information sticks for me. But it’s sticking. Git makes sense. GitHub makes sense. The shape of a scalable system makes sense.</p><p>Forty-six isn’t late. It’s just a different on-ramp.</p><p>Next time: I’m getting into actual AWS services and standing up my first real environment. See you down the road.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9bf8f8e0b11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From the Driver’s Seat to the Cloud: Starting Over at 46]]></title>
            <link>https://medium.com/@jwhunter80/from-the-drivers-seat-to-the-cloud-starting-over-at-46-4aa8f676c806?source=rss-6ace4a9531e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aa8f676c806</guid>
            <dc:creator><![CDATA[Jesse Hunter]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 16:43:08 GMT</pubDate>
            <atom:updated>2026-08-26T16:43:08.721Z</atom:updated>
            <content:encoded><![CDATA[<p>Documenting my cloud journey from week one.</p><p>I’ve spent years watching the world go by through a windshield. Millions of miles of highway, traffic, truck stops, and a lot of time alone with my thoughts. Somewhere along one of those long hauls, I started thinking about what it would take to build a life where I could work from home in central Texas.</p><p>That’s how I landed on cloud engineering. Not because I had some lifelong passion for computers, and not because I saw a flashy ad for a coding bootcamp. It was simpler than that: I wanted remote work. I wanted a career I could build from a desk instead of a cab, and DevOps and cloud engineering kept coming up as fields where people were making that switch — even people who didn’t start with a tech background.</p><p>So here I am. Forty-six years old, no computer science degree, no IT job history, just a decision and a laptop. I’m aiming for a junior DevOps or cloud engineering role, and I’ve picked AWS as the platform to focus on, since it seems to come up everywhere.</p><p>I won’t pretend this feels easy. Most days it doesn’t. I’ll open the course I’m taking through Cloud Engineer Academy from Soleyman Shahir and run into ten new terms in the first five minutes — things that everyone else in the comments section seems to already understand. There’s a particular kind of discouragement that comes from feeling like you’re decades behind people who’ve been doing this since they were teenagers. I catch myself wondering if I started too late, or if I’m fooling myself thinking a truck driver can become an engineer.</p><p>But I keep coming back to one thing: everybody who’s good at this was once a beginner staring at the same confusing terms I am. The only real difference between them and me is time and reps. I don’t have to understand everything today. I just have to understand a little more than I did yesterday.</p><p>I’m writing this at the very beginning, before I have any results to show for it — no certification, no job offer, no proof that this works out. I think that’s actually the point. Most of the career-change stories I’ve read online are told after the fact, once someone’s already landed the job, and it’s easy to make the struggle sound tidy in hindsight. I’d rather put this down honestly, from inside the mess, so if you’re reading this while you’re stuck at “I don’t even know where to start,” so far Cloud Engineer Academy is working pretty well for me.</p><p>My plan for now is simple: follow the courses, study AWS fundamentals, build small projects I can actually point to, and figure out the rest as I go. I don’t know yet how long the road is. But I know which direction I’m driving in.</p><p>If you’re further along this same road, or just starting it like me, I’d love to hear how you’re finding your way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aa8f676c806" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>