It's perhaps not a terrible idea to host a simple "blog-type" site that goes through your journey and documents some things about your experience expertise, may

It's perhaps not a terrible idea to host a simple "blog-type" site that goes through your journey and documents some things about your experience expertise, maybe a blurb/portfolio and things of that nature. Many developer-types seem to have personal sites these days that cover that kind of stuff. I'm not a hiring manager, but I've led lots of interviews and this, IMO/E demonstrates competency in a few areas (this varies depending on how the site was deployed): - basic comprehension of "web stuff" - what "hosting" means in practice (registering a domain + setting up DNS, some sort of service/server to host your assets) - some means of deploying it It's often a good conversation starter too--you mention experience (maybe something on your "blog"), interviewer asks about it, conversation pivots to how you set the site up in the manner you did: "I chose $FRAMEWORK/simple static assets and hosted on $SERVICE as I felt this was a straightforward way to host a site, and I like how $OBJECTSTORE makes hosting easy opposed to setting up a server to just serve static assets." Personally, I like talking about that stuff so it's always a good talk when that comes up during a candidate interview. There's a lot of potential in those conversations, especially given a large portion of software-type jobs are web-related today. Also, regarding the comment above, this is likely helpful if you're a consultant where you can advertise your services more explicitly.