diff --git a/CodeStyleAndFormatting/Introduction/CodeStyleAndFormattingIntroduction/task.md b/CodeStyleAndFormatting/Introduction/CodeStyleAndFormattingIntroduction/task.md index 230ada4..bfad2a4 100644 --- a/CodeStyleAndFormatting/Introduction/CodeStyleAndFormattingIntroduction/task.md +++ b/CodeStyleAndFormatting/Introduction/CodeStyleAndFormattingIntroduction/task.md @@ -1,4 +1,4 @@ -# Section 2: Code style and Formatting +Section 2: Code style and Formatting In this section, we will cover the following topics: - The concepts of code style and formatting diff --git a/CodeStyleAndFormatting/WhatIsFormatting/Quiz/task.md b/CodeStyleAndFormatting/WhatIsFormatting/Quiz/task.md index 344ab02..427c1c7 100644 --- a/CodeStyleAndFormatting/WhatIsFormatting/Quiz/task.md +++ b/CodeStyleAndFormatting/WhatIsFormatting/Quiz/task.md @@ -1 +1 @@ -# Task 2/4: What is the primary benefit of following consistent code formatting? +Task 2/4: What is the primary benefit of following consistent code formatting? diff --git a/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodePractice/task.md b/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodePractice/task.md index 9730320..94b996d 100644 --- a/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodePractice/task.md +++ b/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodePractice/task.md @@ -1,4 +1,4 @@ -# Task 3/4: Reformat the code +Task 3/4: Reformat the code ### Task diff --git a/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodeUsingIDEPractice/task.md b/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodeUsingIDEPractice/task.md index e65876f..41bd764 100644 --- a/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodeUsingIDEPractice/task.md +++ b/CodeStyleAndFormatting/WhatIsFormatting/ReformatTheCodeUsingIDEPractice/task.md @@ -1,4 +1,4 @@ -# Task 4/4: Reformat the code using IDE +Task 4/4: Reformat the code using IDE ### Theory diff --git a/CodeStyleAndFormatting/WhatIsFormatting/Theory/task.md b/CodeStyleAndFormatting/WhatIsFormatting/Theory/task.md index c555158..62a7e9b 100644 --- a/CodeStyleAndFormatting/WhatIsFormatting/Theory/task.md +++ b/CodeStyleAndFormatting/WhatIsFormatting/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/4: What is formatting? +Task 1/4: What is formatting? **_Code style_** is a set of guidelines used in a development team on how to write code. Usually, the code style depends on the programming language and developers’ preferences and includes rules about formatting, diff --git a/Conclusion/Conclusion/Conclusion/task.md b/Conclusion/Conclusion/Conclusion/task.md index 7cca5a3..71d4d9b 100644 --- a/Conclusion/Conclusion/Conclusion/task.md +++ b/Conclusion/Conclusion/Conclusion/task.md @@ -1,4 +1,4 @@ -# Section 8: Conclusion +Section 8: Conclusion Congratulations! 🎉 diff --git a/Conclusion/FeedbackSurvey/FeedbackSurvey/task.md b/Conclusion/FeedbackSurvey/FeedbackSurvey/task.md index 3960950..1d74d47 100644 --- a/Conclusion/FeedbackSurvey/FeedbackSurvey/task.md +++ b/Conclusion/FeedbackSurvey/FeedbackSurvey/task.md @@ -1,4 +1,4 @@ -# Feedback survey +Feedback survey Thank you for taking our Introduction to IDE Code Refactoring in Kotlin course! We would really appreciate it if you could take a few minutes to diff --git a/ExtractingCode/Introduction/ExtractingCodeIntroduction/task.md b/ExtractingCode/Introduction/ExtractingCodeIntroduction/task.md index a47f24d..0414468 100644 --- a/ExtractingCode/Introduction/ExtractingCodeIntroduction/task.md +++ b/ExtractingCode/Introduction/ExtractingCodeIntroduction/task.md @@ -1,4 +1,4 @@ -# Section 3: Extracting code +Section 3: Extracting code In this section, we will cover the following topics: - Long method code smell diff --git a/ExtractingCode/WhatIsExtractMethodRefactoring/ExtractDuplicatedCodePractice/task.md b/ExtractingCode/WhatIsExtractMethodRefactoring/ExtractDuplicatedCodePractice/task.md index 6fc746d..596756f 100644 --- a/ExtractingCode/WhatIsExtractMethodRefactoring/ExtractDuplicatedCodePractice/task.md +++ b/ExtractingCode/WhatIsExtractMethodRefactoring/ExtractDuplicatedCodePractice/task.md @@ -1,4 +1,4 @@ -# Task 2/2: Extract duplicated code +Task 2/2: Extract duplicated code ### Task diff --git a/ExtractingCode/WhatIsExtractMethodRefactoring/Theory/task.md b/ExtractingCode/WhatIsExtractMethodRefactoring/Theory/task.md index ef437ef..f972411 100644 --- a/ExtractingCode/WhatIsExtractMethodRefactoring/Theory/task.md +++ b/ExtractingCode/WhatIsExtractMethodRefactoring/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: What is Extract Method refactoring? +Task 1/2: What is Extract Method refactoring? As we mentioned before, **duplicated code can lead to undesirable effects**, such as when you fix a bug in one place but forget to fix it consistently in duplicates. diff --git a/ExtractingCode/WhatIsExtractVariableRefactoring/ExtractMagicConstantsPractice/task.md b/ExtractingCode/WhatIsExtractVariableRefactoring/ExtractMagicConstantsPractice/task.md index 0094d1d..5cbaab7 100644 --- a/ExtractingCode/WhatIsExtractVariableRefactoring/ExtractMagicConstantsPractice/task.md +++ b/ExtractingCode/WhatIsExtractVariableRefactoring/ExtractMagicConstantsPractice/task.md @@ -1,4 +1,4 @@ -# Task 2/2: Extract magic numbers +Task 2/2: Extract magic numbers ### Task diff --git a/ExtractingCode/WhatIsExtractVariableRefactoring/Theory/task.md b/ExtractingCode/WhatIsExtractVariableRefactoring/Theory/task.md index b26675f..1921a6b 100644 --- a/ExtractingCode/WhatIsExtractVariableRefactoring/Theory/task.md +++ b/ExtractingCode/WhatIsExtractVariableRefactoring/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: What is Extract Variable refactoring? +Task 1/2: What is Extract Variable refactoring? A *magic number* is a numerical value used in the code without a comment explaining its purpose. Using magic numbers in code is considered bad practice because it makes the code prone to errors and less maintainable and readable. diff --git a/InliningCode/InlineMethodRefactoring/InlineMethodAndVariablesPractice/task.md b/InliningCode/InlineMethodRefactoring/InlineMethodAndVariablesPractice/task.md index 7587a5c..e54b986 100644 --- a/InliningCode/InlineMethodRefactoring/InlineMethodAndVariablesPractice/task.md +++ b/InliningCode/InlineMethodRefactoring/InlineMethodAndVariablesPractice/task.md @@ -1,4 +1,4 @@ -# Task 2/2: Inline methods and variables +Task 2/2: Inline methods and variables ### Task diff --git a/InliningCode/InlineMethodRefactoring/Theory/task.md b/InliningCode/InlineMethodRefactoring/Theory/task.md index c065aec..9884782 100644 --- a/InliningCode/InlineMethodRefactoring/Theory/task.md +++ b/InliningCode/InlineMethodRefactoring/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: Inline Method refactoring +Task 1/2: Inline Method refactoring Apply the Inline Method refactoring when a method's behavior is simple and its purpose is clear, but it is called from only one place. If the method has become redundant or does not add significant value, it can be safely inlined. diff --git a/InliningCode/Introduction/InliningCodeIntroduction/task.md b/InliningCode/Introduction/InliningCodeIntroduction/task.md index 4c8659d..e04c695 100644 --- a/InliningCode/Introduction/InliningCodeIntroduction/task.md +++ b/InliningCode/Introduction/InliningCodeIntroduction/task.md @@ -1,4 +1,4 @@ -# Section 6: Inlining code +Section 6: Inlining code In this section, we will cover the following topics: - Inline Variable refactoring diff --git a/InliningCode/WhatIsInlineVariableRefactoring/InlineVariablesPractice/task.md b/InliningCode/WhatIsInlineVariableRefactoring/InlineVariablesPractice/task.md index 153b847..20ff7c2 100644 --- a/InliningCode/WhatIsInlineVariableRefactoring/InlineVariablesPractice/task.md +++ b/InliningCode/WhatIsInlineVariableRefactoring/InlineVariablesPractice/task.md @@ -1,4 +1,4 @@ -# Task 2/2: What is Inline Variable refactoring? +Task 2/2: What is Inline Variable refactoring? In this task, you need to identify unnecessary variables and inline them using the automatic Inline refactoring. diff --git a/InliningCode/WhatIsInlineVariableRefactoring/Theory/task.md b/InliningCode/WhatIsInlineVariableRefactoring/Theory/task.md index 05d09c1..059d040 100644 --- a/InliningCode/WhatIsInlineVariableRefactoring/Theory/task.md +++ b/InliningCode/WhatIsInlineVariableRefactoring/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: What is Inline Variable refactoring? +Task 1/2: What is Inline Variable refactoring? We apply the **Inline refactoring** to simplify code by removing an unnecessary method or variable declarations and directly replacing them with their respective expressions or values. diff --git a/MovingCode/CohesionAndCoupling/Quiz/task.md b/MovingCode/CohesionAndCoupling/Quiz/task.md index 5854ecd..c306cb2 100644 --- a/MovingCode/CohesionAndCoupling/Quiz/task.md +++ b/MovingCode/CohesionAndCoupling/Quiz/task.md @@ -1 +1 @@ -# Task: 2/2: In software design, what should be the ideal relationship between cohesion and coupling? +Task: 2/2: In software design, what should be the ideal relationship between cohesion and coupling? diff --git a/MovingCode/CohesionAndCoupling/Theory/task.md b/MovingCode/CohesionAndCoupling/Theory/task.md index 04ff8f2..47802ab 100644 --- a/MovingCode/CohesionAndCoupling/Theory/task.md +++ b/MovingCode/CohesionAndCoupling/Theory/task.md @@ -1,4 +1,4 @@ -# Task: 1/2: Cohesion and coupling +Task: 1/2: Cohesion and coupling _**Cohesion**_ and _**coupling**_ are fundamental concepts in software design, which determine how well the components of a system are organized and how they interact with each other. Move refactorings can play a crucial role in improving diff --git a/MovingCode/Introduction/MovingCodeIntroduction/task.md b/MovingCode/Introduction/MovingCodeIntroduction/task.md index c4cd7ab..6a361f4 100644 --- a/MovingCode/Introduction/MovingCodeIntroduction/task.md +++ b/MovingCode/Introduction/MovingCodeIntroduction/task.md @@ -1,4 +1,4 @@ -# Section 4: Moving code +Section 4: Moving code In this section, we will cover the following topics: diff --git a/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Quiz/task.md b/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Quiz/task.md index 5fb73cd..192845b 100644 --- a/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Quiz/task.md +++ b/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Quiz/task.md @@ -1 +1 @@ -# Task 2/2: Which of the following is a code smell? +Task 2/2: Which of the following is a code smell? diff --git a/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Theory/task.md b/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Theory/task.md index e54caad..20ecaaf 100644 --- a/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Theory/task.md +++ b/RefactoringAndItsPurpose/CommonCodeIssuesAndTheirImpactOnCodeQuality/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: Common code issues and their impact on code quality +Task 1/2: Common code issues and their impact on code quality Martin Fowler introduced the **_code smell_** term, which indicates that code might have some issues or shortcomings in its implementation. That doesn’t necessarily mean that code has bugs, but the smell makes code understanding, developing, and diff --git a/RefactoringAndItsPurpose/GettingFamiliarWithIDERefactoringFeatures/Theory/task.md b/RefactoringAndItsPurpose/GettingFamiliarWithIDERefactoringFeatures/Theory/task.md index 265352e..20d9d9b 100644 --- a/RefactoringAndItsPurpose/GettingFamiliarWithIDERefactoringFeatures/Theory/task.md +++ b/RefactoringAndItsPurpose/GettingFamiliarWithIDERefactoringFeatures/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/1: Getting familiar with IDE refactoring features +Task 1/1: Getting familiar with IDE refactoring features There are two places to explore available refactoring actions in the IDE: the **Refactor This** and **Search Everywhere** dialogs. diff --git a/RefactoringAndItsPurpose/Practice/RefactoringAndItsPurposePractice/task.md b/RefactoringAndItsPurpose/Practice/RefactoringAndItsPurposePractice/task.md index 73e6134..5113412 100644 --- a/RefactoringAndItsPurpose/Practice/RefactoringAndItsPurposePractice/task.md +++ b/RefactoringAndItsPurpose/Practice/RefactoringAndItsPurposePractice/task.md @@ -1,4 +1,4 @@ -# Task 1/1: Identify code issues and fix them +Task 1/1: Identify code issues and fix them ### Task diff --git a/RefactoringAndItsPurpose/RefactoringTechniques/Quiz/task.md b/RefactoringAndItsPurpose/RefactoringTechniques/Quiz/task.md index 0f3e654..c050d95 100644 --- a/RefactoringAndItsPurpose/RefactoringTechniques/Quiz/task.md +++ b/RefactoringAndItsPurpose/RefactoringTechniques/Quiz/task.md @@ -1 +1 @@ -# Task 2/2: What is the primary difference between "root-canal" refactoring and "floss" refactoring? +Task 2/2: What is the primary difference between "root-canal" refactoring and "floss" refactoring? diff --git a/RefactoringAndItsPurpose/RefactoringTechniques/Theory/task.md b/RefactoringAndItsPurpose/RefactoringTechniques/Theory/task.md index 67ef523..e896919 100644 --- a/RefactoringAndItsPurpose/RefactoringTechniques/Theory/task.md +++ b/RefactoringAndItsPurpose/RefactoringTechniques/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: Refactoring techniques +Task 1/2: Refactoring techniques Developers refactor code to achieve different goals. Sometimes refactoring is the goal in itself: for example, splitting one monolith project into several microservices. diff --git a/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Quiz/task.md b/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Quiz/task.md index 6d4ba74..35085cd 100644 --- a/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Quiz/task.md +++ b/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Quiz/task.md @@ -1 +1 @@ -# Task 2/2: What is the purpose of refactoring in software development? +Task 2/2: What is the purpose of refactoring in software development? diff --git a/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Theory/task.md b/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Theory/task.md index d9bee77..6a35dd4 100644 --- a/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Theory/task.md +++ b/RefactoringAndItsPurpose/WhatIsCodeRefactoring/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: What is code refactoring? +Task 1/2: What is code refactoring? **_Refactoring_** is a process of modifying source code without changing its behavior. For example, renaming a method or extracting a _magic constant_ into a separate variable. It improves code readability but doesn’t change what code does. diff --git a/RefactoringToDesignPatterns/DesignPatternsAndTheirRelationshipsWithRefactoring/Theory/task.md b/RefactoringToDesignPatterns/DesignPatternsAndTheirRelationshipsWithRefactoring/Theory/task.md index 35ea169..25f161a 100644 --- a/RefactoringToDesignPatterns/DesignPatternsAndTheirRelationshipsWithRefactoring/Theory/task.md +++ b/RefactoringToDesignPatterns/DesignPatternsAndTheirRelationshipsWithRefactoring/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/1: Design patterns and their relationship with refactoring +Task 1/1: Design patterns and their relationship with refactoring Design patterns are reusable solutions to common problems that software developers face during the design and implementation of their applications. diff --git a/RefactoringToDesignPatterns/FacadePatternTheory/Theory/task.md b/RefactoringToDesignPatterns/FacadePatternTheory/Theory/task.md index d05a3c4..e9ace32 100644 --- a/RefactoringToDesignPatterns/FacadePatternTheory/Theory/task.md +++ b/RefactoringToDesignPatterns/FacadePatternTheory/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/1: Facade Pattern – Theory +Task 1/1: Facade Pattern – Theory The **Facade** is a _structural pattern_ that provides a simplified interface to a complex system of classes, libraries, or APIs. diff --git a/RefactoringToDesignPatterns/FactoryMethodPatternTheory/Theory/task.md b/RefactoringToDesignPatterns/FactoryMethodPatternTheory/Theory/task.md index 609a739..fb333fe 100644 --- a/RefactoringToDesignPatterns/FactoryMethodPatternTheory/Theory/task.md +++ b/RefactoringToDesignPatterns/FactoryMethodPatternTheory/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/1: Factory Method Pattern – Theory +Task 1/1: Factory Method Pattern – Theory The **Factory Method** is a _creational design pattern_ that provides an interface for creating objects in a superclass, while allowing subclasses to alter the type of objects that will be created. diff --git a/RefactoringToDesignPatterns/Introduction/RefactoringToDesignPatternsIntroduction/task.md b/RefactoringToDesignPatterns/Introduction/RefactoringToDesignPatternsIntroduction/task.md index 7c3898e..252b49d 100644 --- a/RefactoringToDesignPatterns/Introduction/RefactoringToDesignPatternsIntroduction/task.md +++ b/RefactoringToDesignPatterns/Introduction/RefactoringToDesignPatternsIntroduction/task.md @@ -1,4 +1,4 @@ -# Section 7: Refactoring to Design Patterns +Section 7: Refactoring to Design Patterns In this section, we will dive into the fundamental concepts of design patterns and explore how refactorings can shape the structure of your software systems. diff --git a/RefactoringToDesignPatterns/StrategyPatternTheory/Theory/task.md b/RefactoringToDesignPatterns/StrategyPatternTheory/Theory/task.md index 6331f06..8e4b25d 100644 --- a/RefactoringToDesignPatterns/StrategyPatternTheory/Theory/task.md +++ b/RefactoringToDesignPatterns/StrategyPatternTheory/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/1: Strategy Pattern – Theory +Task 1/1: Strategy Pattern – Theory The **Strategy** is a _behavioral pattern_ that allows you to define a family of algorithms, encapsulate each algorithm, and make them interchangeable. diff --git a/RenamingCode/Introduction/RenamingCodeIntroduction/task.md b/RenamingCode/Introduction/RenamingCodeIntroduction/task.md index ce304a8..d815375 100644 --- a/RenamingCode/Introduction/RenamingCodeIntroduction/task.md +++ b/RenamingCode/Introduction/RenamingCodeIntroduction/task.md @@ -1,4 +1,4 @@ -# Section 3: Renaming code +Section 3: Renaming code In this section, we will cover the following topics: - Naming conventions and rules diff --git a/RenamingCode/NamingRules/Quiz/task.md b/RenamingCode/NamingRules/Quiz/task.md index 5846cec..c5a5233 100644 --- a/RenamingCode/NamingRules/Quiz/task.md +++ b/RenamingCode/NamingRules/Quiz/task.md @@ -1 +1 @@ -# Task 2/2: Which of the following is a characteristic of a good name? +Task 2/2: Which of the following is a characteristic of a good name? diff --git a/RenamingCode/NamingRules/Theory/task.md b/RenamingCode/NamingRules/Theory/task.md index 32436dc..ac2a40e 100644 --- a/RenamingCode/NamingRules/Theory/task.md +++ b/RenamingCode/NamingRules/Theory/task.md @@ -1,4 +1,4 @@ -# Task 1/2: Naming rules +Task 1/2: Naming rules Naming is one of the most important parts of code writing, as it significantly affects code understandability. A good name should be **descriptive** and **unambiguous** and clearly reflect what code does. diff --git a/RenamingCode/RenameRefactoringInIDE/FixTyposPractice/task.md b/RenamingCode/RenameRefactoringInIDE/FixTyposPractice/task.md index e776a51..9d6aaac 100644 --- a/RenamingCode/RenameRefactoringInIDE/FixTyposPractice/task.md +++ b/RenamingCode/RenameRefactoringInIDE/FixTyposPractice/task.md @@ -1,4 +1,4 @@ -# Task 3/3: Fix typos, change the code to comply with naming rules and camelCase convention +Task 3/3: Fix typos, change the code to comply with naming rules and camelCase convention ### Task diff --git a/RenamingCode/RenameRefactoringInIDE/Quiz/task.md b/RenamingCode/RenameRefactoringInIDE/Quiz/task.md index d340da1..a6a2342 100644 --- a/RenamingCode/RenameRefactoringInIDE/Quiz/task.md +++ b/RenamingCode/RenameRefactoringInIDE/Quiz/task.md @@ -1 +1 @@ -# Task 2/3: Which of the following code element names demonstrates good naming practice? +Task 2/3: Which of the following code element names demonstrates good naming practice? diff --git a/RenamingCode/RenameRefactoringInIDE/RenameRefactoringInIDE/task.md b/RenamingCode/RenameRefactoringInIDE/RenameRefactoringInIDE/task.md index 7b987ad..de3805e 100644 --- a/RenamingCode/RenameRefactoringInIDE/RenameRefactoringInIDE/task.md +++ b/RenamingCode/RenameRefactoringInIDE/RenameRefactoringInIDE/task.md @@ -1,4 +1,4 @@ -# Task 1/3: Rename refactoring in IDE +Task 1/3: Rename refactoring in IDE If you want to rename a code entity, you can click on the entity’s name and press the **&shortcut:RenameElement;** (macOS) or **Shift+F6** (Windows/Linux) shortcut.