From f4c598bd68be9f0391934c4a50ddf85f1e7f633b Mon Sep 17 00:00:00 2001 From: bitttttten Date: Mon, 29 Jul 2024 22:25:36 +0200 Subject: [PATCH 1/3] fix: typo in implementation details --- .../01.principles/02.solution.implementation-details/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exercises/01.principles/02.solution.implementation-details/README.mdx b/exercises/01.principles/02.solution.implementation-details/README.mdx index ce166ef..2c087da 100644 --- a/exercises/01.principles/02.solution.implementation-details/README.mdx +++ b/exercises/01.principles/02.solution.implementation-details/README.mdx @@ -33,7 +33,7 @@ To that, I want to share a quote with you: The implementation may change but the intention stays the same. -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 their 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. 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. From 0aadd354e281528135eb6e2a1801812501ded245 Mon Sep 17 00:00:00 2001 From: bitttttten Date: Mon, 29 Jul 2024 22:26:39 +0200 Subject: [PATCH 2/3] fix: actually fix the typo --- .../01.principles/02.solution.implementation-details/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exercises/01.principles/02.solution.implementation-details/README.mdx b/exercises/01.principles/02.solution.implementation-details/README.mdx index 2c087da..c8edb7f 100644 --- a/exercises/01.principles/02.solution.implementation-details/README.mdx +++ b/exercises/01.principles/02.solution.implementation-details/README.mdx @@ -33,7 +33,7 @@ To that, I want to share a quote with you: The implementation may change but the intention stays the same. -You write tests to cement the intentions you have. Deciphering those intentions from their 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 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. 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. From d52dc7bf65910bb7783e577fad5140672342f04f Mon Sep 17 00:00:00 2001 From: bitttttten Date: Mon, 29 Jul 2024 22:27:00 +0200 Subject: [PATCH 3/3] fix: and another one --- .../01.principles/02.solution.implementation-details/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exercises/01.principles/02.solution.implementation-details/README.mdx b/exercises/01.principles/02.solution.implementation-details/README.mdx index c8edb7f..eb2d515 100644 --- a/exercises/01.principles/02.solution.implementation-details/README.mdx +++ b/exercises/01.principles/02.solution.implementation-details/README.mdx @@ -33,7 +33,7 @@ To that, I want to share a quote with you: The implementation may change but the intention stays the same. -You write tests to cement the intentions you have. Deciphering those intentions from the 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.