An interesting brief overview of why the author feels that a developer portfolio could be your secret weapon when applying for jobs.
The book also contains some key information that the author feels should be included in a portfolio - and some items that should be left out!
This book was ideal to dip my toes into the idea of developer portfolios and what would be useful to include in one. I look forward to doing some deeper research into this area.
This book delivers valuable insights in simple language & condensed format.
The book is free and took me around 1.5-2h to read. I would recommend it to any developer thinking about building a portfolio.
Author says that it is aimed at "junior devs" but I read late in my career and found it insightful.
The author also mentions that the "tips & suggestions" in the book are targeted at engineers seeking employment instead of freelance work. But in my opinion, a lot of what he mentions applies as good advice for both cases.
I agree with most of what was said in the book, I would only discuss the recommendation of "separating the blog from portfolio site". In my opinion a blog adds a nice dimension to the portfolio which again - will make the portfolio stand out. Especially if the blog posts are genuine, the occasional techie reviewing your application might find it appealing.
I wanna highlight first that this is a free e-book of under 70 pages. It focuses on junior front end developers, but it can be used as inspiration and guidance for anyone working in the IT field 💻 It serves its purpose well and I would recommend it to anyone as a starting point. Thanks for sharing it with us, here's the link for anyone interested: