this repo has no description
typo: crc cards
+2
-4
+2
-4
src/pages/posts/crc-cards-as-training-material.mdx
+2
-4
src/pages/posts/crc-cards-as-training-material.mdx
···
16
16
collaborators={["First collaborator", "second collaborator"]}
17
17
/>
18
18
19
-
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.
19
+
When I'm talking with tech leaders, my goal is to sharpen their vision about the software we are working on. When developers implement features, I often see responsability leaks: the feature works, but components are hard to read, hard to reuse and we pile up technical debt really quickly.
20
20
21
21
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.
22
22
23
23
## The horrible `UserBookmarks` component 😨
24
24
25
-
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.
26
-
27
-
As the code does too many things, it can be hard to follow this post, but, I'll try my best to take you with me on this journey.
25
+
> We're about to look at a very ugly code that is definetely doing too many things. The purpose of the discussion 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. As the code does too many things, it can be hard to follow this post, but, I'll try my best to take you with me on this journey.
28
26
29
27
Here is the `UserBookmarks` component:
30
28