Sprint 2 Exercises: Your Complete Guide

Hey guys! Welcome to the Sprint 2 Exercises guide. This is a complete guide to help you crush it. We're gonna break down the exercises, why you're doing them, and how to get help if you get stuck. Think of this as your personal walkthrough. Let's get started, shall we?

What's the Deal with These Exercises?

So, what's the deal with these exercises, anyway? These challenges are all about sharpening your problem-solving skills. You're not just memorizing code; you're learning to think like a developer. You'll face real-world scenarios and figure out how to tackle them using code. These exercises are crucial for your growth, and they will give you the confidence to succeed in the field. This sprint is designed to push you to become a better programmer. Each challenge is a building block toward mastering more complex concepts. You'll build a solid foundation of problem-solving skills, and as you progress, you'll be able to tackle more complex tasks. Always remember to stay focused, review the material, and stay consistent with your practice.

Why Are Problem-Solving Skills Important?

• Real-world application: Coding isn't just about syntax; it's about solving problems that people face. These exercises mimic real-world problems. They're a stepping stone to building functional, user-friendly applications.
• Adaptability: The tech world is always evolving. Problem-solving skills make you adaptable, able to learn new languages, and keep up with changes.
• Job readiness: Employers want problem-solvers. Being able to break down a complex issue into manageable parts is a core skill for any developer.

Where to Find the Coursework?

The coursework can be found here: https://github.com/Migracode-Barcelona/Module-Data-Groups. Make sure you have access to the materials. This is where you'll get your assignments, instructions, and all the stuff you need to get the job done. This is the starting point for your sprint journey. The coursework repo contains the heart of your project, the blueprint you'll follow. It’s where you'll find the problems you're meant to solve, and the resources to help you do it. Make sure you can access the coursework.

Time Management: How Long Should This Take?

You've got about 6 hours to get through these exercises. Now, 6 hours might sound like a lot, but trust me, time flies when you're coding. So, let's break down how to make the most of those hours. Remember, these exercises are not just about completing the code; they're also about the learning process. Here's a quick guide to help you manage your time:

Breaking It Down:

• Understand the task: Take some time to carefully read and understand the requirements. Don't rush; make sure you know what you are expected to do. Rushing through the requirements will make you fail.
• Plan your approach: Before you write any code, plan how you'll approach the problem. Consider the steps involved and the tools you'll use.
• Code in chunks: Don't try to write everything at once. Write in small, manageable chunks, testing as you go.
• Regular breaks: Take short breaks to avoid burnout. Step away from your computer, stretch, or grab a snack.

Pro Tips for Time Management

• Prioritize tasks: Not all tasks are created equal. Identify the most critical tasks and focus on those first.
• Timeboxing: Allocate a specific amount of time for each task. When the time is up, move on, even if you haven’t finished.
• Avoid perfectionism: It's better to submit something that works than to spend all your time trying to make it perfect.

Getting Help: Don't Be Afraid to Ask!

Stuck? Don’t worry; we've all been there. Getting help is a crucial part of the learning process. The best developers aren’t the ones who know everything; they’re the ones who know how to find the answers. Asking questions will help you overcome any hurdles.

Where to Seek Assistance?

• Your class channel: Your class channel is your first line of support. Share your blockers with your classmates and instructors. Someone might have encountered the same issue and can help you. The class channel is a place where you can ask for help from your peers.
• CYF guide: The CYF guide on asking questions is an invaluable resource. Read it and learn how to ask questions effectively. It’s a skill that will serve you well throughout your career. Follow the CYF guide on asking questions to get the most helpful responses.

Effective Questioning

• Be specific: Describe the problem clearly. What are you trying to do, and what’s not working?
• Share your code: Include the relevant code snippets. This helps others understand the context.
• Show your attempts: Explain what you've tried and what you expect to happen. This helps others avoid suggesting things you’ve already done.
• Be patient: Wait for a response, and be respectful of others' time.

Resources

• Google and Stack Overflow: These are your best friends. Search for error messages and keywords to find solutions.
• Documentation: The documentation for the languages and tools you're using is a great source of information.
• Debugging tools: Learn to use debugging tools to find the root cause of the problems.

How to Submit Your Work: Step-by-Step

Alright, you've finished your code and are ready to submit it. Follow these steps to submit your coursework.

Submission Steps:

1. Checkout main: Start by making sure you're on the main branch. This is your starting point.
2. Create a branch: Create a branch from main called coursework/sprint-2. This branch is where you'll do your work. Use a descriptive name that reflects the task.
3. Make small commits: Make regular small commits in this branch with clear messages. Each commit should represent a logical unit of work. This makes it easier to track your progress and revert changes if needed. Make sure your commit messages are clear and concise.
4. Open a PR: When you're ready, open a Pull Request (PR) to your own main branch. This allows you to review your changes and make sure everything is in order. This is a crucial step for collaboration and code review.
5. Submit to the Google sheet: Submit the PR to the Google sheet. This is where your work gets officially submitted and graded.

Pro Tips for Submission

• Review your PR: Before submitting, review your PR to ensure you haven’t missed anything.
• Test your code: Make sure your code works as expected. Test it thoroughly to identify and fix any bugs.
• Read the submission guidelines: Make sure you follow all the submission guidelines. This ensures your work is correctly submitted.

Branching Strategy

• New branch for each sprint: Make a new branch for each sprint. This will keep your work organized and separate from other sprints.
• Clear commit messages: Use clear commit messages to describe your changes. This will make it easier to understand your code.
• Merge frequently: Merge your branch into the main branch frequently. This will help you keep your code up to date.

Conclusion: You Got This!

Well, that's it, guys! This guide covers everything you need to know about the Sprint 2 exercises. Remember, it’s okay to struggle. That’s how you learn. Use your resources, ask questions, and keep coding. You've got this, and we're here to help. Good luck, and happy coding!