In this summary, I list some of the things that have helped me. It reads fast, but applying them well can take a lifetime. Must read this before you start programming.
Take the code and break down big pieces of code into small functions.
If by the time you leave work, you haven’t solved the problem. Please turn off the computer and leave it for the next day. Don’t think about the pain anymore.
YAGNI principle: don’t codify more than you’ve been asked to. Don’t anticipate the future and create something that works as soon as possible. Code only the necessary parts to solve the current problem.
You don’t need to know everything, nor all the existing frameworks. The most significant thing is to have a good base. Know the language in depth before starting with a Framework and learn fundamental things like the SOLID principles or how to write clean code.
KISS: “Keep it simple, stupid” or “keep it stupid simple” is a design principle that states that most systems work best if they are kept simple rather than made complicated. And while this is logical, it is sometimes difficult to achieve.
Don’t overthink it.
If you’re with a problem or a bug too long, walk away, and come back to it later. Often, the best solutions to the problems occur to me from my office to the bathroom. Taking a walk away is also advisable when you are angry with a client or with a coworker, especially if you want to keep your job.
Learn to write useful tests and learn to do TDD. TDD is a software development process that relies on the repetition of a concise development cycle: Write a test, run all tests and see if the new one fails, write some code, run tests, refactor code, repeat.
Solve the problem first and then write the code. Don’t start coding without knowing what to do.
Don’t memorize code, instead understand the logic.
If you copy and paste a stack overflow solution, make sure you understand it. Learn to use Stack Overflow in the right way.
If you want to learn something, practice. Make examples and make them work because read about something is not enough.
Study other people’s code and let others study your code from time to time. Pair programming and code reviews are a good idea.
Don’t Reinvent The Wheel.
Your code is the best documentation.
Know how to google stuff. For this, you need to have experience and read a lot to know what to look for.
Your code will need to be maintained by yourself in the future or by others, so write the code with the reader in mind, not trying to be the smartest person. Make it read like you’re reading a story.
The best way to resolve an error with google is to copy-paste it.
Never give up; in the end, in one way or another, you’ll resolve it. There are bad days, but they’ll pass.
Rest, Rest, and Rest. The best way to solve a problem is to have a restful mind and finally, patience and love what you do.