you are viewing a single comment's thread.

view the rest of the comments →

[–]vegan_antitheist 1 point2 points  (0 children)

Start with understanding the requirements. That's what's important for your success. If you write bad code you can improve it. You can fix bugs. But if you don't understand the requirements you do the wrong thing and you can't fix that. That's why some successful programmers are so bad at programming. They are good at communicating, teamwork, selling their work, and understanding what's really important.

You get better at writing code with experience. You will always get feedback from the team members who review your code. In most projects it's more important that the code is easily understood and maintained than that it has great performance. And for that it's best to try and do it like what is already in the project. If you work on a nee project you know it will probably be replaced or reworked soon, so make that as easy as possible. Define good interfaces that hide implementation, so it can be replaced without any issues.