# Reflection – Week 2 > Source: > Published: 2026-07-10 09:23:11+00:00 "**Shifting from Prompt Engineering to Infrastructure Orchestration**" Week 2 was a mix of excitement, curiosity, and a little bit of frustration. I learned a lot of new concepts, but I also realized that the best way to understand them is by actually trying them out. Reading or watching tutorials helps, but experimenting with the tools made everything click for me. One of the topics I enjoyed learning about was Claude Code. Before this week, I mainly thought of AI as something that answers questions or helps write content. Seeing how Claude can assist with coding, debugging, and understanding projects made me see it differently. It feels less like a search engine and more like someone you can work with while building something. That really changed how I think about using AI in development. Another interesting topic was Skills. I liked the idea that you can give an LLM specific skills so it behaves more like a specialist instead of a general assistant. It made me realize that the quality of the output doesn't only depend on the model itself, but also on how you guide it and what tools or skills you give it. That was something I hadn't really thought about before, and I can already see how useful it could be for different types of projects. I also learned about Subagents, which was a new concept for me. At first, I didn't really understand why you would need multiple agents instead of just asking one AI to do everything. But after learning more about it, I started to see the benefit. Having different agents focus on different tasks seems like a much cleaner and more organized way to work, especially for bigger projects. The biggest challenge I faced this week was running out of tokens while practicing. It happened a few times, and honestly, it was a little annoying because I would be in the middle of exploring an idea and suddenly had to stop. Even though it was frustrating, it also made me think more carefully about how I write prompts and how I use my conversations. I learned that being clear and intentional can make a big difference. Despite the challenges, there was one moment this week that I’m really proud of. I was working on setting up infrastructure, and seeing my Terraform files get generated automatically by the AI felt incredible. However, it didn't work perfectly right away and threw an error. Instead of panicking or blindly asking the AI to fix it, I took a step back, read the error output carefully, and figured out how to fix it myself. Actually understanding what went wrong and resolving it was a huge confidence booster. This week also changed my mindset a bit. I realized that it's okay not to understand everything immediately. Some of the concepts felt overwhelming at first, but after trying them myself, they became much easier to understand. I'm starting to feel more comfortable experimenting instead of worrying about getting everything right the first time. Going forward, one habit I want to build is working on more hands-on projects with Claude instead of only learning the theory. I think building small projects and experimenting with different features will help me remember what I've learned much better than just reading about them. I also want to keep challenging myself by trying new ideas, even if they don't work perfectly on the first attempt. Overall, Week 2 helped me see AI as more than just a tool for answering questions. I'm beginning to understand how it can become a real partner in learning and building projects. There were definitely some challenges along the way, but they were part of the learning experience, and I'm looking forward to seeing what I'll be able to build as I keep practicing.