Lesson One: Embrace the DRY Principle

The DRY principle, which stands for "Don't Repeat Yourself," is a vital concept that distinguishes basic code from high-quality, maintainable code. Here are two essential questions to consider:

1. Am I repeating code? If you find yourself copy-pasting code snippets, you may need to rethink your approach. Strive to avoid redundancy in your code, as excessive repetition can complicate future updates. Look for similar code blocks and convert them into a function. This process will challenge you to think more systematically — a clear sign of your growth.
2. How can I reuse this code? This question pushes you further up the DRY ladder. If you frequently copy and modify code from previous projects, you're missing an opportunity to generalize your functions better. Over time, this habit will help you build a personal library of reusable tools. Consider packaging these for public use; it’s not as daunting as it seems!

In the video "4 Tips To Succeed As A Self Taught Developer," you’ll find strategies to enhance your coding journey and avoid common pitfalls.

Lesson Two: The Importance of Formatting and Linting

Using a code editor like Visual Studio Code? Two extensions you should incorporate are a formatter and a linter. What’s the difference?

• Formatter: This tool standardizes your code’s appearance by applying its own style rules, managing aspects such as indentation and line length. While you might not prefer the changes, getting accustomed to a formatter like Prettier can be beneficial.
• Linter: A linter evaluates your code's quality, including formatting. It’s advisable to separate formatting tasks from linting to avoid confusion. Linters can catch issues like unused variables and other coding standards.

Integrating both tools will significantly improve your coding experience. Your code will align with industry standards, making it easier to read and understand, especially when scanning forums or repositories.

If you’ve collaborated on projects or worked with existing code, you understand the importance of maintaining a consistent style. A formatter and linter establish a baseline standard across contributions, fostering collaboration.

The video "Self-Taught Programmers... We need to talk" delves into the challenges faced by self-taught developers and how to overcome them effectively.

Lesson Three: Leveraging GitHub Copilot

One of the most valuable tools I recommend is GitHub Copilot. Initially skeptical, I now consider it an essential investment for only $10 a month (or $8 if you opt for annual billing).

Copilot offers two primary features. First, it provides excellent code completion suggestions, which can even extend to writing website content. The recommendations are generated from both your previous code and external sources, and while you should verify them, they can be quite impressive.

The second feature is a chat-based tool that has significantly enhanced my development process. It eliminates the fear of asking "dumb questions" and allows me to seek help promptly, which has helped maintain my momentum.

Beyond seeking help, Copilot is a fantastic resource for reviewing your code after writing. You can ask it for suggestions on improving your code, similar to how you might seek advice from a colleague.

Finally, I’ve found it helpful to outline my code with comments before diving into writing. This method allows me to leverage Copilot more effectively.

Conclusion

I hope these insights assist you in advancing your coding journey. Whether it’s about writing cleaner and more efficient code, adopting tools to enhance code quality, or utilizing AI to facilitate your learning process, these lessons can make a significant difference.

What are some of your favorite tips or enlightening moments during your coding journey? What helped you overcome the mental hurdles of learning to code? Share your experiences in the comments!