내가 좋아할 만한 콘텐츠
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.
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.
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.
Do you have a journaling practice? I started mine one week ago and it has been an amazing experience.
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.
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.
What's a good metaphor for coding? I like "construction"
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.
Code is an iterative process. You learn, apply, make mistakes and repeat. It is hard, but worth if you keep going.
Requirements give you focus. You know what to do and why. Never be caught acting without purpose, but think deeply about your decisions.
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.
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.
Acknowledge that there is always room for improvement. But you need to keep moving forward.
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.
Requirements are key to quality code. They ensure your code is doing what it is supposed to do. They follow the pre-made guidelines.
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?
United States 트렌드
- 1. Bears 54.4K posts
- 2. Black Friday 467K posts
- 3. Nebraska 12.3K posts
- 4. Swift 55.5K posts
- 5. Sydney Brown 1,104 posts
- 6. Iowa 13.5K posts
- 7. Lane Kiffin 10.2K posts
- 8. Rhule 2,847 posts
- 9. Ben Johnson 2,971 posts
- 10. Black Ops 7 Blueprint 11.8K posts
- 11. Sumrall 3,702 posts
- 12. #CHIvsPHI 1,191 posts
- 13. Jalon Daniels N/A
- 14. #SoleRetriever N/A
- 15. Go Birds 11.7K posts
- 16. Egg Bowl 8,269 posts
- 17. Kansas 16K posts
- 18. #Huskers 1,348 posts
- 19. #kufball 1,017 posts
- 20. Mississippi State 5,510 posts
Something went wrong.
Something went wrong.