Right! New people need onboarding, and more people means more communication overhead, so a late project often gets later.

Brooks's law says adding people to a late project makes it later, because of onboarding time and extra communication between team members.

Exactly! Coverage only shows which lines were executed, not that the tests checked the right behavior or every case.

100% coverage only means every line ran during some test. Tests can still miss edge cases or check the wrong results.

Correct! Refactoring improves the internal structure of code while keeping its external behavior the same.

It's refactoring: improving code's structure and readability without changing its behavior. Adding features is a separate task.

Yes! Git is a version control system that runs on your computer; GitHub is an online service for hosting and sharing Git repositories.

Git is a version control tool you can use alone and offline. GitHub is one of several services that host Git repositories online.

Correct! Big O describes how work grows as input grows: double the input, and the work roughly quadruples.

Big O describes growth, not exact time: O(n²) means the work grows with the square of the input size, regardless of the hardware.

Right! Technical debt is the future cost of choosing a quick solution now; like money debt, it grows "interest" if it isn't repaid.

That's technical debt: a shortcut that works now but makes future changes harder. It isn't necessarily a bug, since the code may work fine.

Exactly! Unit tests isolate a small piece of code, often using mocks or stubs, so failures point straight to the problem.

It's a unit test. Integration and end-to-end tests check how parts work together, which is slower but catches different problems.

Yes! The manifesto values working software over comprehensive documentation, while still seeing value in documentation.

The Agile Manifesto values working software more than comprehensive documentation, but it says documentation still has value. Agile teams plan constantly, in short cycles.

Correct! A garbage collector can only free objects nothing refers to, so forgotten references in caches or listeners still leak memory.

Yes, it can be a leak. Garbage collectors free only unreachable objects, so objects still referenced by mistake, e.g. in a cache, pile up.

Right! A monolith is simpler to build, test, and deploy; teams can split it into services later if they truly need to scale.

Many experts advise starting with a well-structured monolith. Microservices add network, deployment, and coordination costs that small teams rarely need early on.