<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Future: leslie wilkey</title>
    <description>The latest articles on Future by leslie wilkey (@lesliewilk32223).</description>
    <link>https://future.forem.com/lesliewilk32223</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3577094%2F11e3e955-80ce-4783-9862-42b2dc6b6925.jpg</url>
      <title>Future: leslie wilkey</title>
      <link>https://future.forem.com/lesliewilk32223</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://future.forem.com/feed/lesliewilk32223"/>
    <language>en</language>
    <item>
      <title>From Minikube to EKS</title>
      <dc:creator>leslie wilkey</dc:creator>
      <pubDate>Tue, 21 Oct 2025 11:31:38 +0000</pubDate>
      <link>https://future.forem.com/lesliewilk32223/from-minikube-to-eks-nij</link>
      <guid>https://future.forem.com/lesliewilk32223/from-minikube-to-eks-nij</guid>
      <description>&lt;p&gt;Last week, I deployed three microservices to Kubernetes locally. This week, I deployed them to AWS EKS. What I thought would be a straightforward migration turned into a deep lesson about container platforms, cross-compilation, and production deployment patterns.&lt;/p&gt;

&lt;p&gt;Here's what actually happened when theory met reality.&lt;/p&gt;

&lt;p&gt;The Confidence Before the Crash&lt;br&gt;
After successfully deploying to Minikube, I felt ready. I had working Kubernetes manifests, healthy pods, and services communicating properly. Moving to EKS seemed like the natural next step - just point kubectl at a different cluster, right?&lt;/p&gt;

&lt;p&gt;I provisioned an EKS cluster, updated my kubeconfig, and confidently deployed all three services&lt;/p&gt;

</description>
      <category>education</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The Training Wheel Must Come Off</title>
      <dc:creator>leslie wilkey</dc:creator>
      <pubDate>Tue, 21 Oct 2025 09:13:55 +0000</pubDate>
      <link>https://future.forem.com/lesliewilk32223/the-training-wheel-must-come-off-4189</link>
      <guid>https://future.forem.com/lesliewilk32223/the-training-wheel-must-come-off-4189</guid>
      <description>&lt;p&gt;Like many that have come before me, I have landed in Tutorial Hell. When learning to program, Tutorial Hell is when you're stuck feeling unprepared, feeling that you need just one more video or article or tutorial. It is an insidious cycle. For me, I feel confident during a lecture or tutorial. I'm following the instructions, and I feel like I understand why we are doing each step. Then I feel like the rug is pulled out from under me when I go to start building on my own. So, I turn back to the tutorial, and the cycle continues.&lt;/p&gt;

&lt;p&gt;Why is this happening? And How do I get out?&lt;/p&gt;

&lt;p&gt;To use the training wheels metaphor: I ride my bike with the training wheels from point A to point B, and I feel great, so I take the training wheels off. When I start to ride I immediately fall over. This happens because the training wheels can help you practice the motions of riding a bike, but they remove the resistance, the need to balance. However, the skill of riding a bike is balancing. In other words, training wheels will allow you to practice the motions you need in order to practice and develop the skill of balancing on your bike, but they will prevent you from practicing the skill of balancing on your bike. This is contradiction of learning. You need something to practice the motions, but then you have to use the motions to struggle against a problem.&lt;/p&gt;

</description>
      <category>autonomy</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
