Developing vs. Communicating
212 words.
In response to Caio Proiete’s How to be a better developer? (Which is, in turn, a response to Rodrigo DÃaz Concha’s How to be a better developer?)
Most of the tips are fine. But two of Caio Proiete’s recommendations for getting better are: “Write technical articles” and “Give technical presentations.”
I would argue that those two things will only help you become a better communicator, which is obviously a good skill to have, but I would consider it less in the development area and more in the analysis area. Ultimately, the only way to become a better developer is to develop software. Over and over again. For a long time. Only then will you become a better developer, young grasshopper.
Also: One of Rodrigo DÃaz Concha’s tips is “Forum Participation.” I’ve found that you have to take developer forums with a heavy dose of salt. Sometimes — okay, really, it’s most of the time — the solutions you find on forums are not that great. I can’t even count the number of times I’ve found shaky solutions on forums. Sometimes it’s corrected, sometimes not. Besides, forum participation is more of a communication and social networking thing. It might help you land a job somewhere, but become a better developer? I’m not convinced.
Sorry, new comments are disabled on older posts. This helps reduce spam. Active commenting almost always occurs within a day or two of new posts.