A web developer is a programmer who especially, always busy with the development of the World Wild Web application using a client-server. This arti...
For further actions, you may consider blocking this person and/or reporting abuse
4. Don't Forget to Comment Your Code
I don't agree. Better is write code in the way that every other developer will understand in seconds. Believe me, it's possible.
P.S. Don't treat it as criticism, it's just an advice based on my experience.
Cheers
I'd say that both are important. Yes, writing a clear and understandable code is very important but sometimes comments are also helpful. You just have to find a good balance. It is important that comments aren't the majority of the code but having some comments in the code can really make life easier :)
Great article! Let me add one more tip:
Contribute to Open-Source Projects
This will allow you to challenge yourself by reading someone else's code, solving problems, fixing bugs in code you didn't write, adding features, etc.
Cheers
Great post. Experience is definitely the most important thing. The more you work, the faster you will come to perfection.
Cheers
Thank you. I will definitely take your advices to heart.🧑💻
Cheers
Thanks very much. 🙏
Cheers
I would recommend that you don't watch too many tutorial videos, and spend time coding, even if it's for an hour a day.
NICe article man! Awesome!
Cheers
8. Do not afraid to write test cases
Imho much better to write some test which was told many more details about your functions compared to comment.
What about both? Why to choose a single one?
Thinking that tests auto-document your code is obviously a silly move as tests are meant primarily for public functions/methods and check mainly I/Os while documentation aims to the implementation details, so they are not interchangeable.
I'm thinking about tests in the red/greed/refactor life cycle but other types of tests (performance tests, usability tests, E2E tests and so on) neither aim for implementation details.
Tests (either be TDD or code first, plus regression tests) document features from the point of view of what inputs can something receive and which outputs should it return in consequence.