|
1 | 1 | --- |
2 | | -title: 'Using MDX' |
| 2 | +title: 'The naming gambit' |
3 | 3 | description: 'Lorem ipsum dolor sit amet' |
4 | 4 | pubDate: 'Jun 01 2024' |
5 | 5 | carouselImages: ['/blog/posts/gambito/10.png', '/blog/posts/gambito/11.png', '/blog/posts/gambito/17.png', '/blog/posts/gambito/18.png'] |
| 6 | +tags: ['clean code', 'naming'] |
6 | 7 | --- |
| 8 | +One thing is certain: |
7 | 9 |
|
8 | | -# Teste |
| 10 | +We may never be able to unlock all the secrets and possibilities that emerge from these two crossroads: Programming and chess. |
9 | 11 |
|
10 | | -alo alo. |
| 12 | +Both arts involve strategy, dexterity, sacrifice and resilience. There are many similarities, but there are also differences. |
11 | 13 |
|
12 | | -__testando__ |
13 | | -*testando* |
| 14 | +The decision to choose a move on the board is irreversible. It's made. But unlike chess, in programming you can undo, redo and, most importantly of all, adhere to clean code. |
14 | 15 |
|
15 | | -``` |
16 | | -console.log('alo') |
17 | | -``` |
| 16 | +But after all, what can be considered clean code? Uncle Bob has written an entire book on the subject, which I highly recommend you read! |
18 | 17 |
|
19 | | -## Teste |
| 18 | +In this series of posts I intend to cover some of the aspects of the famous Clean Code, bringing practical examples with a focus on the front end, but which can be applied to software development in general. |
20 | 19 |
|
21 | | -Aoba |
| 20 | +There's nothing better to start this topic than talking about one of the most difficult things in this area: giving things (good) names. |
22 | 21 |
|
23 | | -> Quote |
24 | | -> |
25 | | ->> Test |
| 22 | +Knowing that this is a pain point for many of us (devs), we can see it as a small sacrifice that will pay off in the long run. And both you in the future and your fellow developers will be very grateful for your initial sacrifice. |
26 | 23 |
|
27 | | -- Test |
| 24 | +Whether you're creating a CSS variable, a React component, a Redux state, a custom Hook or a simple utility function, giving it a meaningful name that is easily understood within its context is an arduous but fundamental task. |
28 | 25 |
|
29 | | -[Link](https://google.com) |
| 26 | +To finish with another chess analogy, remember: just as a Grandmaster can look at a board and instantly understand what is happening, a developer should be able to look at their code and immediately understand what it does. |
30 | 27 |
|
31 | | -- First item |
32 | | -- Second item |
33 | | -- Third item |
34 | | - - Indented item |
35 | | - - Indented item |
36 | | -- Fourth item |
| 28 | +White pieces move first in chess, and clear names move your code in the right direction from the start. |
0 commit comments