A 4-week GitHub Copilot learning journey for development teams

For many development teams, the challenge is not only to start using AI tools but to do so in a practical and safe way during real delivery work. For a .NET team working with Visual Studio, GitHub Copilot, backend services, Windows-based applications, and Azure, the real value lies in AI becoming part of the normal engineering workflow.

This approach should be treated as the development of a core team capability, not as an informal learning exercise.

Week 1: Start with certainty and basic habits

In the first week, the main goal is to help the team feel comfortable with GitHub Copilot inside Visual Studio. Developers should try the most common ways to work with it: inline suggestions, chat, code explanations, and small code generation.

For a .NET team, this can be very practical. A developer can ask Copilot to explain what one service class is doing, generate a DTO, add XML comments, or summarise how one component is calling an Azure backend service.

This first week is important because the team starts learning that good prompting gives better results. Instead of asking vague questions, they should learn to provide a task, context, constraints, and the expected output. At the end of the week, people should already understand where Copilot is helping a lot, and where it still needs careful human review.

Week 2: Use Copilot in real engineering tasks

Once the team is comfortable, the second week should emphasise integration of Copilot into standard engineering activities. This phase is when GitHub Copilot starts providing measurable value.

For example, developers can use it to generate xUnit tests with moqs, spot potential root causes of bugs, improve logging, or support small refactoring work in existing .NET code. This is especially useful when the application communicates with backend APIs, local devices, file systems, or Azure services, where errors and edge cases are important.

The team should remember: Copilot accelerates initial drafts and narrows problems, but does not replace engineering judgment. Human validation stays critical, especially for correctness, resilience, and failure scenarios.

Week 3: Use Copilot on real feature work

In week three, the team should shift from practice to real feature work. This can mean changing several related files, adding a new field across models, validators, mappings, and tests, or updating logging in a component.

This is also the time to build a shared prompt library. Prompts for code explanation, test generation, debugging, refactoring, and PR review save time and create consistency. Over time, these patterns become part of the team’s playbook.

Week 4: Make it a team habit

The last week should make Copilot use repeatable and sustainable. The team should set clear guardrails for strong review, such as validation logic, concurrency, backend integration, sensitive code, configuration, or deployment scripts.

In addition, developers are advised to utilise Copilot for communication-related tasks, not just for coding. It can support the preparation of pull request summaries, test documentation, technical documentation, and brief change overviews.

How to track learning and success

To measure progress, the team should keep it simple. At the individual level, each developer can track how many days they used Copilot, how many real tasks it supported, how many tests it helped create, one prompt that worked well, and one bad suggestion they caught before accepting it.

At the team level, useful metrics can include the percentage of pull requests where Copilot helped, time saved on routine work, increased test coverage in the code touched, faster understanding of unfamiliar .NET modules, and growth of the shared prompt library.

In the end, success is not about how much code Copilot writes. Success is when the team delivers better .NET and Azure solutions faster, with a stronger understanding, stronger tests, and safer engineering decisions.

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Why Database Modernization Matters for AI

When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Azure Well-Architected AI workload Assessment

AI is everywhere, part of the IT solutions we build and run today. Having an AI service, a good model, and data is not enough. As for cloud, the real difference is how we build, manage and run the whole solution. Microsoft created the Azure Well-Architected Framework for AI Workloads exactly for this reason — to help teams design AI systems that are reliable, secure, and cost-efficient. The assessment has six main categories that we cover in the next section. Based on the results, we can gain a good understanding of the current AI workload estate and a list of actions to improve how you run and manage your AI workloads . Designing the AI Application The first step in building your AI application is to consider how you will structure it. Using containers for tasks like data processing or model inference helps maintain consistency across the system. This approach makes it easier to update, move, and manage different components. When you have multiple steps in your workflow, such as...

Cloud as a Story - Vunvulea Radu

Search This Blog