Interesting to see many comments here claiming that side projects don't matter when looking for a job. I've been actively applying for a full-time dev position for the past 3 months and the most common feedback I receive is "We need to see side projects, OSS contributions so we know how you code."
I have about 4+ years in DevOps and in support. I consider myself a programming generalist, which I thought would be enough to at least get a technical interview. Instead of working on a project that will most likely be left incomplete due to fatigue or loss of interest, I rather spend that time learning ways to improve my skills to make myself the best programmer I possibly can be.
I've been considering starting my own blog and write articles about lessons learned or an e-book to express my credibility. Does anyone have any opinions with developers who write blogs/publications in lieu of side projects or OSS contributions?
Thanks for the tip. This has actually been a bit difficult for me to accomplish. Most of the engineers are tight for time finishing their sprints, so all "mentoring" and feedback is usually done asynchronously via Slack or code reviews.
Thank you so much for replying! I actually have considered triplebyte, but I've read some mixed reviews about their coding challenges and interview process. The main thing that has discouraged me from applying is the 4-month wait to re-apply if you fail your first interview https://triplebyte.com/candidate_faq#scroll-link-14. Because of this constraint, I'm not sure my time is better spent working on a personal project that I can showcase my skills to a potential employer or study/practice to pass triplebyte's coding challenge.
Have you or someone you know used triplebyte? If so, what are your thoughts in their interviewing process?
I have about 4+ years in DevOps and in support. I consider myself a programming generalist, which I thought would be enough to at least get a technical interview. Instead of working on a project that will most likely be left incomplete due to fatigue or loss of interest, I rather spend that time learning ways to improve my skills to make myself the best programmer I possibly can be.
I've been considering starting my own blog and write articles about lessons learned or an e-book to express my credibility. Does anyone have any opinions with developers who write blogs/publications in lieu of side projects or OSS contributions?