Hey everyone! I'm trying to teach myself about Azure and AKS by building a project that involves creating an AKS cluster from scratch using Infrastructure as Code (IaC) tools like Terraform (which I know pretty well) and Pulumi (which is new to me). I started by exploring the console and taking notes, then jumped into writing the initial bootstrapping code with Powershell. Though I have some familiarity with Powershell, I'm still learning, and I've decided to incorporate Test-Driven Development (TDD) into the mix, which I understand in theory but have never practiced.
Fast forward several months, and it feels like my project is just growing and growing without end! I don't have a lot of spare time lately, but I've learned so much about Powershell and Pester in the process. I really enjoy it, but I'm struggling to limit the scope of my project. How can I effectively manage these rabbit holes when tackling personal projects like this? Any tips would be greatly appreciated!
1 Answer
One good approach is to create a roadmap for your project. Whenever you come across something new that seems interesting, take a moment to see if it fits into your current plans. If it doesn't, just jot it down for later instead of getting sidetracked right away. This way, you can maintain your focus and keep progressing without unnecessary distractions.
That's a solid idea! I’d love to know more about how to develop that roadmap, especially since it’s a learning project where everything feels uncertain. TDD is supposed to help guide your structure, but I find it's complicating things for me right now. Any more tips on handling support requirements would be awesome!