<?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 Alexander Claude on Medium]]></title>
        <description><![CDATA[Stories by Alexander Claude on Medium]]></description>
        <link>https://medium.com/@alexander.claude?source=rss-04522bd91580------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Alexander Claude on Medium</title>
            <link>https://medium.com/@alexander.claude?source=rss-04522bd91580------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:59:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexander.claude/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[The Road Less Traveled: From the Highway to the Cloud]]></title>
            <link>https://medium.com/@alexander.claude/the-road-less-traveled-from-the-highway-to-the-cloud-92583e80a17c?source=rss-04522bd91580------2</link>
            <guid isPermaLink="false">https://medium.com/p/92583e80a17c</guid>
            <dc:creator><![CDATA[Alexander Claude]]></dc:creator>
            <pubDate>Sat, 29 Nov 2025 12:43:22 GMT</pubDate>
            <atom:updated>2025-11-29T12:43:22.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*RVDIP85Agyn4WZa4dk-BeQ.jpeg" /><figcaption><strong>Trucker To Cloud Engineer.</strong></figcaption></figure><p><strong>The Road Less Traveled: From the Highway to the Cloud</strong></p><p>They say the best journeys often begin with an unexpected detour.<br>A few years ago, I found myself behind the wheel of an 18-wheeler, navigating America’s highways with a seemingly unusual combination of credentials in my back pocket: an Associate degree in Cybersecurity, along with CompTIA Security+, CompTIA CySA+, and AWS Solutions Architect certification. To the casual observer, it might seem like an odd place for someone with my technical background. But here’s what I’ve learned: sometimes, the path to your destination isn’t a straight line.<br>Life has a way of teaching us lessons when we least expect it. While most people see truck driving and cloud engineering as worlds apart, I see them as two sides of the same coin. Both require navigation, problem-solving, and the ability to keep moving forward even when the road gets challenging. Both demand precision, attention to detail, and an understanding that every decision matters.<br>However, I knew my journey wasn’t meant to end on the highway. My passion for technology, my investment in building my skills, and my vision for the future were calling me toward a different destination: becoming a Cloud Engineer.<br>That’s why I made a decision that would change everything: I enrolled in Cloud Engineering Academy with <a href="https://learn.cloudengineeracademy.io/">Soleyman</a>.</p><p>This blog is my chronicle of that transformation. It’s about the late nights studying AWS architectures after long drives. It’s about the determination to transition from the driver’s seat to the cloud infrastructure that powers our digital world. It’s about proving that no matter where you start, with the right skills, dedication, and support, you can architect your own future.<br>Whether you’re in a similar transition, curious about cloud engineering, or simply believe in the power of reinvention, I invite you to ride along with me. This is more than a career change; it’s a journey of transformation.<br><strong>Welcome aboard. The destination? The cloud.</strong></p><p><strong>WEEK ONE !! </strong>Week one at <strong>Cloud Engineering Academy </strong>introduced me to foundational concepts that set the stage for understanding how cloud computing works, along with essential networking principles.</p><p><strong>Cloud Fundamentals</strong></p><p><strong>a) What is Cloud Computing?</strong><br>Cloud computing is a way to use technology resources like servers, storage, and software over the internet instead of having everything stored and run on your personal computer or local servers. Think of it like using electricity from a power grid rather than generating your own power. You can access your data and applications from anywhere with an internet connection, making everything more flexible and convenient.</p><p><strong>b) Benefits of Cloud Computing</strong><br>Using cloud computing has many advantages:</p><ul><li><strong>Cost Savings:</strong> You don’t need to buy expensive hardware or maintain it. You pay only for what you use.</li><li><strong>Flexibility:</strong> You can quickly scale up or down based on your needs. Want more storage or computing power? It’s easy to get.</li><li><strong>Accessibility:</strong> Access your files and applications from any device, anywhere.</li><li><strong>Reliability:</strong> Cloud providers often have backup systems and security measures to protect your data.</li><li><strong>Collaboration:</strong> Multiple people can work on the same project at the same time, even if they’re in different locations.</li></ul><p><strong>c) Cloud Deployment Models</strong><br>There are different ways to set up cloud services:</p><p><strong>1. Public Cloud</strong></p><ul><li><strong>What it is:</strong> Cloud services offered over the internet to anyone who wants to use them. Examples include Amazon Web Services (AWS), Microsoft Azure, and Google Cloud.</li><li><strong>Significance:</strong> Cost-effective because you share resources with others. Good for small businesses or startups that want to save money and avoid managing hardware.</li></ul><p><strong>2. Private Cloud</strong></p><ul><li><strong>What it is:</strong> Cloud infrastructure used exclusively by one organization. It can be hosted on-site or by a third-party provider but is dedicated only to that organization.</li><li><strong>Significance:</strong> Provides higher security and control. Ideal for large companies or organizations with sensitive data, like banks or healthcare providers.</li></ul><p><strong>3. Hybrid Cloud</strong></p><ul><li><strong>What it is:</strong> A mix of public and private clouds. Data and applications can move between the two, depending on needs.</li><li><strong>Significance:</strong> Offers flexibility. You can keep sensitive data private but still use the cloud for less sensitive tasks, balancing cost, security, and performance.</li></ul><p><strong>4. Community Cloud</strong></p><ul><li><strong>What it is:</strong> Shared cloud used by a specific community of organizations with common goals or needs, like government agencies or research institutions.</li><li><strong>Significance:</strong> Enables collaboration among similar organizations with shared security and compliance requirements.</li></ul><p><strong>d) Software Development Cycle</strong><br>The Software Development Cycle is like a step-by-step plan that helps create computer programs or apps. Think of it as a recipe for making software that works well and meets people’s needs.</p><p><strong>The Main Steps:</strong></p><ol><li><strong>Planning</strong></li></ol><ul><li><strong>What happens:</strong> Decide what the software should do. Like making a shopping list before cooking.</li><li><strong>Why it’s important:</strong> Ensures everyone knows what the final product should be.</li></ul><p><strong>2. Design</strong></p><ul><li><strong>What happens:</strong> Draw or plan how the software will look and work. Like sketching a house before building it.</li><li><strong>Why it’s important:</strong> Helps everyone understand how the finished software will function.</li></ul><p><strong>3. Development</strong></p><ul><li><strong>What happens:</strong> The actual building process, where programmers write the code (instructions) for the software.</li><li><strong>Why it’s important:</strong> Turns the plans into a real, working program.</li></ul><p><strong>4. Testing</strong></p><ul><li><strong>What happens:</strong> Check if the software works correctly and fix any problems. Like proofreading an essay.</li><li><strong>Why it’s important:</strong> Ensures the software is reliable and easy to use.</li></ul><p><strong>5. Deployment</strong></p><ul><li><strong>What happens:</strong> Making the software available for people to use. Like opening a store to customers.</li><li><strong>Why it’s important:</strong> Users can start using the software for its intended purpose.</li></ul><p><strong>6. Maintenance</strong></p><ul><li><strong>What happens:</strong> Updating and fixing the software after it’s released. Like fixing a broken appliance.</li><li><strong>Why it’s important:</strong> Keeps the software working well over time and improves it based on user feedback.</li></ul><p><strong>Why a Cloud Engineer is Need During Software Development Cycle</strong></p><p><strong>1. Setting Up the Cloud Environment</strong><br>A Cloud Engineer creates and manages the cloud infrastructure (the online servers, storage, and networks) where the software will run. This is like building the foundation of a house before construction begins.Essentially, they enable the entire process to happen seamlessly in the cloud, supporting all stages of development and deployment.</p><p><strong>2. Ensuring Smooth Deployment</strong><br>They help deploy the software to the cloud quickly and efficiently, making sure everything works correctly online. Think of it as moving a house into its new location without any problems.</p><p><strong>3. Managing Resources</strong><br>They monitor and control the cloud resources used by the software, such as storage space and computing power. This ensures the application runs fast and costs are controlled.</p><p><strong>4. Security and Backup</strong><br>Cloud Engineers set up security measures to protect the software and data from unauthorized access. They also create backup systems in case something goes wrong, like insurance for your house.</p><p><strong>5. Scaling and Flexibility</strong><br>If the software becomes popular and needs more resources, the Cloud Engineer can quickly increase capacity. If usage drops, they can reduce resources to save costs. This flexibility is key to handling changing needs.</p><p><strong>6. Supporting Development and Testing</strong><br>During the design, development, and testing phases, the Cloud Engineer provides the necessary online environment, making it easier for developers to build and test the software without worrying about technical details.</p><p><strong><em>During my first week, I discovered some important ideas about how cloud computing works and why the internet and networking are so crucial. Here’s a breakdown of what I learned in simple terms:</em></strong></p><h3>1. How the Internet is Very Important in Cloud Computing</h3><p>Think of the internet as a giant highway that connects computers all around the world. Cloud computing relies heavily on this highway because it allows people to access data, applications, and services stored in the cloud from anywhere, at any time. Without the internet, cloud services wouldn’t be possible, because there’s no way to connect to these online resources.</p><h3>2. Networking Basics in Cloud Computing</h3><p>Networking is like the roads and traffic system that help data travel smoothly between computers and the cloud. Just like cars need roads to get from one place to another, data needs networks to move quickly and safely. Understanding how these networks work helps ensure that information reaches the right place without delays or problems.</p><h3>3. Virtualization</h3><p>Virtualization is a clever way of creating multiple pretend computers inside one real computer. Imagine having one physical computer but being able to run many different “virtual” computers on it. This helps save space and cost because instead of buying many physical machines, companies can use virtualization to do more with fewer computers.</p><h3>4. Important Networking Components in Cloud Computing</h3><p>Some of the key parts that make up the network in cloud computing include:</p><ul><li><strong>Routers:</strong> Devices that direct data traffic, like traffic police guiding cars on the road.</li><li><strong>Switches:</strong> Devices that connect different parts of a network, helping data find the right destination quickly.</li><li><strong>Firewalls:</strong> Security barriers that protect data from unwanted visitors, like security guards at a building entrance.</li><li><strong>Data Centers:</strong> Large facilities where many servers (powerful computers) are stored to host cloud services.</li></ul><p>The following are a series of tasks I completed to gain practical experience with some of the key concepts I have learned:</p><p><strong>Lab Work:</strong></p><p><strong>Task 1: Installation </strong>( I checked the version of curl on my macOS and then updated it to the latest available version).</p><p><strong>Task 2: Making GET Requests</strong></p><p>GET requests are fundamental for retrieving data from servers, which is essential for managing, monitoring, and interacting with cloud resources effectively.</p><p>To perform a GET request, I used the following simple command to obtain the HTML content from my favorite website.</p><p>curl https://google.com</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A2KTvDZaU1y1ty2cPnicmA.png" /></figure><p>After running the above command it fetched the results below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HtM8cOShFTMCJ4wcF1MRnA.png" /></figure><p>Based on the above screenshot, observe the message “The document has moved,” which signifies a redirection. After the redirection occurs, I used the following command( curl -L https://google.com ), which subsequently retrieves the website’s data page as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S7wIM8a01MvCt1l3HlIrhA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3_LpVXN5iYCcjeERX5n8wg.png" /></figure><ul><li>Saving the Output: To save the out to a file, I used the <strong>-o flag:</strong></li><li>curl -L https://google.com -o google.html</li><li>I used a text editor to view the saved HTML content.</li></ul><p><strong>Task 3: Analyzing HTTP Response Headers</strong></p><p>The objective is to build proficiency in using curl to analyze and review HTTP response headers.</p><p>To retrieve the HTTP headers from the response, I executed the command: curl -I https://google.com, which produced the following results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hVEOPPkEa_HaDglC-jU8Q.png" /></figure><h3>Understanding Common HTTP Status Codes:</h3><p>Understanding these common HTTP status codes enables one to:</p><ol><li><strong>Diagnosing and Troubleshooting Issues</strong>: Knowing these codes helps identify problems such as server errors, client errors, or redirects, enabling quicker resolution.</li><li><strong>Improving User Experience</strong>: Understanding status codes allows developers to handle different responses appropriately, providing users with clear and meaningful feedback.</li><li><strong>Enhancing Application Communication</strong>: Proper knowledge of status codes ensures smooth interaction between clients and servers, facilitating effective data exchange.</li><li><strong>Optimizing Website Performance and Security</strong>: Recognizing and managing status codes can help in optimizing resource loading, managing redirects efficiently, and maintaining security protocols.</li></ol><p>From the screenshot above we can see the following headers:</p><ul><li><strong>Content-Type: text/html</strong><br>Indicates that the body of the response contains HTML content.</li><li><strong>HTTP/2 200</strong></li><li><strong>HTTP/2:</strong> The version of the HTTP protocol being used.</li><li><strong>200:</strong> The status code meaning the request was successful, and the server is returning the requested content.</li><li><strong>Server — gws</strong></li><li>This specifies the server software handling the request. “gws” often refers to Google’s Web Server, indicating that the response is from a Google service or server.</li><li><strong>Content-length: 220</strong></li><li>The size of the response body in bytes. In this case, the HTML content returned is 220 bytes long.</li></ul><p>This response indicates a successful request (status 200) with HTML content, served by Google’s web server, with a content size of 220 bytes.</p><p>Another Task was to <strong>Trace Routes.</strong></p><p>Trace Routes enables one to:</p><ol><li><strong>Diagnosing Network Connectivity Issues:</strong> Trace routes help identify where a network connection is failing or experiencing delays, pinpointing problematic hops along the path.</li><li><strong>Mapping Network Paths:</strong> They visualize the route data takes from the source to the destination, providing insight into how networks are interconnected.</li><li><strong>Measuring Latency and Performance:</strong> Trace routes reveal the time taken for data to travel between points, helping assess network speed and responsiveness.</li><li><strong>Detecting Network Congestion or Bottlenecks:</strong> By analyzing delays at specific hops, trace routes can identify congested links or slow-performing network segments, aiding in optimization and troubleshooting.</li></ol><p>To execute a traceroute, I used the command: <strong>traceroute google.com </strong>, which generated the screenshot shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSApmsm2HJ-NDPnVF24B7w.png" /></figure><p><strong>Imagine sending a letter through a series of post offices to reach a friend.</strong> Each post office is like a “hop” in the network. When you run a traceroute to google.com, your computer sends small data packets that travel through multiple servers and networks (the post offices) before reaching Google.</p><p><strong>What you see in the traceroute output:</strong></p><ul><li><strong>Hops:</strong> Each line shows a “hop,” which is a step from one server to the next on the way to Google.</li><li><strong>Time:</strong> Next to each hop, you see the time it took for your data to reach that point and come back. Shorter times mean faster connections.</li><li><strong>Location or IP:</strong> Usually, it shows the IP address of each server the data passes through.</li></ul><p><strong>In simple terms:</strong></p><ul><li>The traceroute shows a path your data takes from your computer to Google.</li><li>It tells you how many steps it takes and how long each step takes.</li><li>If there’s a delay or if a step doesn’t respond, it might mean a problem or heavy traffic at that point.</li></ul><p><strong>Someone might wonder, “Why is this helpful?”</strong></p><ul><li>If Google isn’t loading quickly, traceroute can help find where the delay is happening.</li><li>If there’s a break in the path, you can see exactly where the connection is failing.</li></ul><p><strong>In summary :</strong></p><p>My passion for transitioning into cloud engineering stems from a strong desire to broaden my technical expertise and stay ahead in the rapidly evolving tech landscape. I understand that cloud technology plays a crucial role in enhancing efficiency, scalability, and data management across various industries. Building a solid foundation in cloud fundamentals is essential for developing innovative, secure, and scalable solutions that can drive progress in any industry.</p><p>I am aware that mastering complex topics like cloud architecture, security protocols, and deployment strategies will be challenging and require dedication. Although learning new skills and overcoming setbacks can be difficult, I am committed to continuous improvement through consistent practice.</p><p>Enrolling in the Cloud Engineering Academy is a significant step toward achieving my career aspirations. I look forward to gaining hands-on experience with cloud platforms, infrastructure management, and automation tools. This knowledge will empower me to contribute to digital transformation initiatives, explore new career opportunities, and support technological advancements across industries. This journey marks an exciting new chapter in my life, and I am fully committed to giving my best effort</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92583e80a17c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>