From e011dba5eb6844117ee1e576935a9b7130f5faee Mon Sep 17 00:00:00 2001 From: Florent Dubost Date: Wed, 21 Aug 2024 15:24:18 +0200 Subject: [PATCH] Update _posts/2024-08-20-js-nation-react-summit-2024.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Théo Gianella <122352170+TGianella@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 85b27d041..344a5049b 100644 --- a/_posts/2024-08-20-js-nation-react-summit-2024.md +++ b/_posts/2024-08-20-js-nation-react-summit-2024.md @@ -22,7 +22,7 @@ Alex sums up his speech in 5 points: - **Accept imperfections** in your codebase: perfect is the enemy of good, shortcuts and exceptions can be taken if they are well documented. - **[Colocating 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. +- **Reusability** is not always the better choice vs **duplication**, you should find the right balance, abstraction should only come when a piece of code is proven to be a long term solution. - **Readability and understandability** of the code is very important for the future developers that will maintain your code: leave comments, break conditions with more than 3 members using intermediate variables, etc. - Use **Typescript** intensively and try to handle all the possible states of your data.