Git Happens
Agile or Not?
Design Principles Showdown
Bug Hunters
Architecture Madness
100

You’ve modified several files and want Git to start tracking them for the next commit.

What is git add?

100

Working software is valued more than extensive documentation.

What is an Agile principle?

100

This principle says software should avoid unnecessary complexity and keep solutions straightforward.

What is KISS (Keep It Simple, Stupid)?


100

Testing a single function or method independently.

What is unit testing?

100

This architecture separates application logic, user interface, and data management into three components.

What is MVC?

200

You accidentally committed to the wrong branch and need to bring those changes into the correct one.

What is a merge?

200

A team works for three months before showing any progress to the customer.

What is NOT Agile?

200

This principle suggests developers should not implement features until they are actually needed.

What is YAGNI?

200

Testing whether multiple modules work correctly together.

What is integration testing?

200

This architecture organizes software into layers such as presentation, business logic, and data access.

What is layered architecture?

300

Two developers edit the same lines of a file and Git cannot automatically combine the changes.

What is a merge conflict?

300

A prioritized list of work items that the team pulls tasks from during sprint planning.

What is the product backlog?

300

This principle states that a class or module should only have one reason to change.

What is the Single Responsibility Principle?

300

Testing the entire application to ensure it meets system requirements.

What is system testing?

300

In this architecture, applications are built as many small independent services that communicate through APIs.

What is microservices architecture?

400

Your teammate pushed new code to GitHub and you need to bring those changes into your local repository.

What is git pull?

400

A short meeting where team members share progress and blockers.

What is the daily stand-up?

400

This design idea divides a program so different parts handle different responsibilities.

What is Separation of Concerns?

400

Testing performed by the customer to confirm the software meets their needs.

What is acceptance testing?

400

This architecture model involves clients requesting services or resources from a centralized server.

What is client-server architecture?

500

A developer saves a snapshot of the project history with a message describing the changes made.

What is a commit?

500

A meeting held after a sprint to discuss what went well and what should improve.

What is a sprint retrospective?

500

When developers simplify and restructure code to improve readability without changing functionality, they are applying this practice.

What is refactoring?

500

The process of confirming that the software was built correctly according to specifications.

What is verification?

500

This design goal aims to structure a system so its components closely reflect the real-world problem being solved.

This design goal aims to structure a system so its components closely reflect the real-world problem being solved.