diff --git a/src/pages/posts/crc-cards-as-training-material.mdx b/src/pages/posts/crc-cards-as-training-material.mdx
index aab9a11..7e4de80 100644
--- a/src/pages/posts/crc-cards-as-training-material.mdx
+++ b/src/pages/posts/crc-cards-as-training-material.mdx
@@ -11,6 +11,8 @@ CRC Card: **C**lass name, **R**esponsibilities, **C**ollaborators.
[CRC Cards](https://en.wikipedia.org/wiki/Class-responsibility-collaboration_card) are a teaching tool on how to design software. They were proposed by Kent Beck and Ward Cunningham, and, hell yeah it's useful.
+
+
When I'm talking with tech leaders, my goal is to sharpen our vision about the software we are working on. When developers implemente features, I often see responsability leaks: the feature works, but the component are hard to read, hard to reuse and we pile up technical debt too quickly.
CRC cards are a great tool to focus the discussion and to aknowledge the fact that the developer shared her global vision to each individual local component who must rely only on its local scope. Let's take an example of one discussion.
@@ -19,7 +21,7 @@ CRC cards are a great tool to focus the discussion and to aknowledge the fact th
Disclaimer: we're about to look at a very ugly code that is definetely doing too many things. The purpose of the discussion I have is to show to the tech lead that we really want to prevent this to happen and it is her mission to standardize it with her team.
-Let's say we have a `UserBookmarks` component. Its role is to display a list of bookmarks the user saved.
+Let's say we have a `UserBookmarks` component.
```tsx
interface Props {
@@ -60,10 +62,23 @@ export const UserBookmarks: FunctionComponent = ({ user }) => {
setIsLoading(false)
}
}
+
+ const tilesAnimation = gsap.to({
+ duration: 0.8,
+ opacity: 0.35,
+ yoyo: true,
+ repeat: -1,
+ stagger: 0.025,
+ })
return