Gustavo Santos @codewithgustavo

Software Engineer | I tweet about how to be a better software engineer github.com/gefgu Brazil Joined December 2021

Tweets

610
Followers

77
Following

74
Likes

2K

Gustavo Santos @codewithgustavo

3 years ago

What did you think was the most lesson you learned in the past week? Mine: There's always room for improvement, but you need to keep going.

0 1 1 138 0

Gustavo Santos @codewithgustavo

3 years ago

Requirements = Expectations. When you define requirements and met them, you're proud of the result. You achieved what was expected. Not setting requirements for code means you will never be sure if the result is good.

0 0 1 100 0

Gustavo Santos @codewithgustavo

3 years ago

When you make a mistake, think about what caused it. Most mistakes are consequences of the system we choose to guide our lives. It's your responsibility to improve it.

0 0 0 67 0

Gustavo Santos @codewithgustavo

3 years ago

Do you have a journaling practice? I started mine one week ago and it has been an amazing experience.

0 0 0 65 0

Gustavo Santos @codewithgustavo

3 years ago

Most people don't understand the importance of software requirements. They spend hours debugging and refactoring problems that could have been solved by a well-thought process. Requirements are the first step to catching bugs before they happen.

0 0 1 45 0

Gustavo Santos @codewithgustavo

3 years ago

Software Requirements are an essential practice. This is how to get started: - Notice the problem/challenge. - Analyze what is causing it. - Specify what is necessary to solve it. - Validate your current solution and iterate on these steps.

0 0 0 32 0

Gustavo Santos @codewithgustavo

3 years ago

What's a good metaphor for coding? I like "construction"

1 0 0 51 0

Gustavo Santos @codewithgustavo

3 years ago

Spend at least 1 hour weekly improving your code process. You spend a lot of time coding, So why not make it more productive? - Read some programming textbooks. - Take a look at in-depth blog posts. - Design new techniques to improve your output.

0 0 1 31 0

Gustavo Santos @codewithgustavo

3 years ago

Code is an iterative process. You learn, apply, make mistakes and repeat. It is hard, but worth if you keep going.

0 0 0 22 0

Gustavo Santos @codewithgustavo

3 years ago

What are your key tips for building a personal brand?

1 0 1 497 0

Gustavo Santos @codewithgustavo

3 years ago

Requirements give you focus. You know what to do and why. Never be caught acting without purpose, but think deeply about your decisions.

0 0 0 26 0

Gustavo Santos @codewithgustavo

3 years ago

Communicate your code with purpose. Think about this before writing your PR description: - What does my code change? - How the changes are made? - Why the change was made? It's a good way to make meaningful commits.

0 0 0 26 0

Gustavo Santos @codewithgustavo

3 years ago

What's a good metric for code quality?

0 0 1 35 0

Gustavo Santos @codewithgustavo

3 years ago

After choosing a good development process, there is no going back. You will stick to it because it is much better than what you did before.

0 0 1 339 0

Gustavo Santos @codewithgustavo

3 years ago

Acknowledge that there is always room for improvement. But you need to keep moving forward.

0 0 1 18 0

Gustavo Santos @codewithgustavo

3 years ago

How do you plan your coding process?

0 0 0 21 0

Gustavo Santos @codewithgustavo

3 years ago

Most beginners don't have requirements for their code. It hurts their quality. A simple way to start is to ask yourself: "What the code I will write now should do?" In this way, you will know when you hit the target.

0 0 1 20 0

Gustavo Santos @codewithgustavo

3 years ago

Requirements are key to quality code. They ensure your code is doing what it is supposed to do. They follow the pre-made guidelines.

0 0 1 224 0

Gustavo Santos @codewithgustavo

3 years ago

How many code-related books did you read last year?

0 0 0 34 0

Gustavo Santos @codewithgustavo

3 years ago

How to make architectural choices for your code: - What do you want to do? - How are you going to do it? - Why are you going to do it this way? - What are the alternatives?