From 0e50db2b11a657037240ff0a384b6be0b933e23f Mon Sep 17 00:00:00 2001 From: Florent Dubost Date: Mon, 19 Aug 2024 17:05:05 +0200 Subject: [PATCH] Update _posts/2024-08-20-js-nation-react-summit-2024.md Co-authored-by: Yoann Frommelt <44576727+yfrommelt@users.noreply.github.com> --- _posts/2024-08-20-js-nation-react-summit-2024.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-08-20-js-nation-react-summit-2024.md b/_posts/2024-08-20-js-nation-react-summit-2024.md index 9673c4b46..02a0d734a 100644 --- a/_posts/2024-08-20-js-nation-react-summit-2024.md +++ b/_posts/2024-08-20-js-nation-react-summit-2024.md @@ -20,7 +20,7 @@ One of my favourite types of presentation, with concrete things that you can the Alex sums up his speech in 5 points: -- **Accept imperfections** in your codebase: perfect is the ennemy of good, shortcuts and exceptions can be taken if they are well documented. +- **Accept imperfections** in your codebase: perfect is the enemy of good, shortcuts and exceptions can be taken if they are well documented. - **[Colocate code](https://alexmoldovan.dev/code-bites/colocation-is-king)** according to concerns is a way of improving readability and therefore maintainability and efficiency. - **Reusability** is not always the better choice vs **duplication**, you should find the right balance, abstraction should come when a piece of code is proven as a long term solution. - **Readability and understandability** of the code is very important for the future developpers that will maintain your code, leaves comments, break conditions with more than 3 members using intermediate variables.