From ea41ba249bed8908da58b26c3a672a9a797cd85a Mon Sep 17 00:00:00 2001 From: Florent Dubost Date: Mon, 19 Aug 2024 17:19:49 +0200 Subject: [PATCH] Etienne's review --- _posts/2024-08-20-js-nation-react-summit-2024.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) 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 8e492ce1..08dba0a8 100644 --- a/_posts/2024-08-20-js-nation-react-summit-2024.md +++ b/_posts/2024-08-20-js-nation-react-summit-2024.md @@ -23,7 +23,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. -- **Readability and understandability** of the code is very important for the future developers that will maintain your code, leaves comments, break conditions with more than 3 members using intermediate variables. +- **Readability and understandability** of the code is very important for the future developers that will maintain your code: leaves 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. At Bedrock, we've always tried to apply a maximum of [best practices](https://tech.bedrockstreaming.com/2021/09/06/web-best-practices.html) including some developped here by Alex, to ensure the maintainability of our web codebase. It seems to be working pretty good since this JS project is now 10 years old! @@ -46,10 +46,10 @@ Scott reveals that we can use the browser's native APIs to build certain UI comp He shows for example: -- how to build modals with [``](https://developer.mozilla.org/fr/docs/Web/HTML/Element/dialog) element, -- how to easily create animated transitions with [View Transition API](https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API) or with [`@starting-style`](https://developer.mozilla.org/en-US/docs/Web/CSS/@starting-style), -- how to create menu with [``](https://developer.mozilla.org/fr/docs/Web/HTML/Global_attributes/popover) element, -- how to build slideshows with [`scroll-snap`](https://developer.mozilla.org/fr/docs/Web/CSS/scroll-snap-align) CSS properties. +- How to build modals with [``](https://developer.mozilla.org/fr/docs/Web/HTML/Element/dialog) element +- How to easily create animated transitions with [View Transition API](https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API) or with [`@starting-style`](https://developer.mozilla.org/en-US/docs/Web/CSS/@starting-style) +- How to create menu with [``](https://developer.mozilla.org/fr/docs/Web/HTML/Global_attributes/popover) element +- How to build slideshows with [`scroll-snap`](https://developer.mozilla.org/fr/docs/Web/CSS/scroll-snap-align) CSS properties And much more besides, check out all Scott's tips on this [site](https://tolin.ski/talks/install-nothing).