Skip to content

fix: typo in implementation details #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 30, 2024
Merged

fix: typo in implementation details #24

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f4c598b
fix: typo in implementation details
bitttttten Jul 29, 2024
0aadd35
fix: actually fix the typo
bitttttten Jul 29, 2024
d52dc7b
fix: and another one
bitttttten Jul 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion exercises/01.principles/02.solution.implementation-details/README.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ To that, I want to share a quote with you:

<callout-info class="important">The implementation may change but the intention stays the same.</callout-info>

You write tests to cement the intentions you have. Deciphering those intentions from ther source code alone can proof challenging and, at times, dangerous. Remember that the code you are working with _may not have been written by you_. It could've been a colleague who's now on vacation, or have left the company long before you joined. But you have to debug and fix the code right now. For that, you have to know what was the intention behind that code.
You write tests to cement the intentions you have. Deciphering those intentions from the source code alone can prove challenging and, at times, dangerous. Remember that the code you are working with _may not have been written by you_. It could've been a colleague who's now on vacation, or have left the company long before you joined. But you have to debug and fix the code right now. For that, you have to know what was the intention behind that code.

This is where automated tests can be a life-changing factor. They act as a partial documentation for the code, and make things like code refactoring (i.e. changing the implementation) _much_ easier.

Expand Down