Adding an example would be useful to see how it renders.
Obviously a cool side-project. but I dont understand why anyone would want automate CV generation for "production use".
CVs are personal, and get updated once a year or so. Each life is different, each CV is different. So it does not easily scale across people.
As someone who is reviewing CVs, I review CVs from two aspects:
1. does the person have the skills I need, and
2. can the person communicate and do they have professional pride
Its much easier to get 1 & 2 across if you craft your CV. Think about what message you want to get across and work very hard to get that message across on one page. Expand with more detail in pages 2 and following.
As a hiring manager I am filtering roughly in this order:
1. has core skills I need, if yes, then
2. has used core skills I need in enough projects to likely meet our bar, if yes, then
3. are the relevant projects close enough to what we are building?
Later in the interview process, interviewers will look at the CV more closely to prepare for the interview.
Anyway, if anything I would only start with automating from page 2 and beyond.
Adding an example would be useful to see how it renders.
Obviously a cool side-project. but I dont understand why anyone would want automate CV generation for "production use".
CVs are personal, and get updated once a year or so. Each life is different, each CV is different. So it does not easily scale across people.
As someone who is reviewing CVs, I review CVs from two aspects:
1. does the person have the skills I need, and 2. can the person communicate and do they have professional pride
Its much easier to get 1 & 2 across if you craft your CV. Think about what message you want to get across and work very hard to get that message across on one page. Expand with more detail in pages 2 and following.
As a hiring manager I am filtering roughly in this order:
1. has core skills I need, if yes, then 2. has used core skills I need in enough projects to likely meet our bar, if yes, then 3. are the relevant projects close enough to what we are building?
Later in the interview process, interviewers will look at the CV more closely to prepare for the interview.
Anyway, if anything I would only start with automating from page 2 and beyond.
Interesting, I created two similar projects:
1. markdown resume:
- https://leftium.com/resume
- plain-text version is human-friendly: https://leftium.com/resume?text
- also renders OK on Github: https://github.com/Leftium/leftium.com/blob/main/src/routes/...
- PDF version is produced by printing from browser. (Try Cmd-P)
---
2. invoice generator
- Uses shell scripts instead of make
- Uses weasyprint instead of wkhtmltopdf
---
Some samples would be nice. Curious how the default output settings look.
Nice. Yours seems to be only for promoting your own resume, right? Mine's a tool for a user to control, customize, and create their own, locally.
Effectively the same. (If your project's resume.md had your details, would it prevent others from using it as a tool?)
Steps for a user to create their own resume (locally):
1. clone repo
2. update the resume.md file
3. run the server locally `npm run dev --open`
4. print from browser (as PDF)
- My version happens to contain a web server that serves the HTML resume (among other pages).
- You can also preview the results in real-time as you edit the MD file.
---
Compare to steps with your tool:
1. clone repo
2. update the resume.md file.
3. run `make`
(I omitted all the setup steps for the sake of comparing the major steps. I suppose if I added a makefile, the steps would be exactly the same.)
Yours is slick. I like it.
I'd like to try this out. Would be nice to have a few examples of pdfs and htmls generated in the repo itself.