I agree that interviews are important. I am not saying that they are not. If you read until the end, I say that write one article a week on top of preparing for your interviews is the way to go.
However, a lot of people hate technical interviews. Candidates are often under enormous pressure on the interview day. By writing about all your knowledge base and projects, candidates can refine how they communicate their knowledge and their projects.
To me, this is also additional practice for the interview as well as pitching yourself to get in the door. Many people might just need a foot in the door to be able to show their skills and experience to potential employers.
An intense environment of “testing” for knowledge on interviews don’t help candidates succeed. They need more. They need either help in communicating what they know or they need more help in getting real world experience necessary.
Writing can provide both:
- practice communicating ideas better
- connecting you to communities of developers who are also writing and sharing so that you can get leads to jobs and to projects that you might want to work on.
It’s very interesting you say “not just any project”, it must be “creation of value”. I absolutely agree with that. You get inspirations from projects in tutorial books and online training. But, you need to solve some real world problems with the projects that you work on.
Thanks for your comment, much appreciate it.