loading...

re: 5 reasons why Git based resume is awesome VIEW POST

TOP OF THREAD FULL DISCUSSION
re: I personally use markdown to represent my resume on GitHub. github.com/stephencorwin/resume/bl... This lets me also declare it as a dependency on ...
 

Thank you for sharing your approach, Stephen.

Markdown is more declarative, maintainable, and elegant way! And you create your own website with interactive user interface with React. You also have your portfolio in it, deploy script and linter. They are what I have to do build as my current goal.

I got great inspiration from your repository. Thanks again!

 

Thanks! When I was rebuilding it, I never did finished fleshing out the content of my portfolio -- it's a bit stale (4+ years old). I suppose that it is a side effect of no longer searching. Less motivation to update it once you have landed the job. ;)

Feel free to reach out if you have questions. GL on your job search!

Less motivation to update it once you have landed the job. ;)

Yeah exactly. However, it is even easy for me to update the resume via Git (and hopefully CI).

Feel free to reach out if you have questions. GL on your job search!

Thank you very much!

The resume is maintained via GitHub, but also published on npm. Whenever I make an update I can just bump the version number and npm publish. If the portfolio website is using @lastest in the package.json, redeploying should grab the latest version. You can also just run the command npm i --save @stephencorwin/resume@latest to force an update to the latest.

Oh, you publish your resume to NPM! I have never imagined it. I have just installed your latest resume on my PC :)
Why do you publish this to NPM?

It's scoped under my tag @stephencorwin so as to not be confused with others. Part of the reason to use both is so that we can have "source of truth" files that we generate other files from. We don't necessarily want to always publish the generated files on GitHub, but it does make sense to publish them on npm since the audience there intends to use them in projects.

Mainly though... It's because I use Zeit Now to host my projects and they do not recognize any "change" when deploying unless I either dockerize the container or version bump the dependency in my package.json.

This is in part due to aggressive caching.

Please note that you can use a GitHub repo directly as a dependency in your package.json though.

"@stephencorwin/resume": "git://github.com/stephencorwin/resume"
github.com/stephencorwin/stephenco...

Mainly though... It's because I use Zeit Now to host my projects and they do not recognize any "change" when deploying unless I either dockerize the container or version bump the dependency in my package.json.

Got it! Nice hack.

Code of Conduct Report abuse