12 ms·

Rustdoc résumé

122 points by 1f60c 5y ago

thrwyoilarticle 5y ago
Opinion: LaTeX resumes/CVs don't make any sense. If, in your job, you were trying to express technical information, you wouldn't use LaTeX. You might use it for a paper or a book where you have a lot of content or multiple issues that you want to look consistent. But a resume is a single, small document with multiple different sections that have different formatting requirements. In your job, you probably share information in markdown or rst. If you're looking to signal - and let's be honest, with LaTeX you are - why not use those? Bonus: ATS systems and recruiters won't bork your input.
- tyingq 5y ago
  Assuming the LaTeX resume would be shared with a recruiter as a pdf, is there really any difference? I could render the markdown with the Computer Modern font and many people would assume LaTeX.
  - JustFinishedBSG 5y ago
    > I could render the markdown with the Computer Modern font You really shouldn't though. Computer Modern is a pretty ugly font. At least use something like New Computer Modern if you really need a Scoth Roman font with maths.
  - Sharlin 5y ago
    As an aside, in 2021 Computer Modern looks really dated, especially for content that’s predominantly text rather than math. There are much better, more Unicode-friendly, and more typographically complete LaTeX fonts available.
    - est31 5y ago
      Which fonts would you recommend?
      - Sharlin 5y ago
        Recently I've been using `mathpazo` which is Palatino extended with matching math symbols (if math is needed; if not, just use plain `palatino`). Specifically, I use `mathpazo` with smallcaps and old-style figures enabled: \usepackage[sc,osf]{mathpazo}
        Sharlin 5y ago
        (And yes, I realize that the original Palatino actually predates Computer Modern :D)
- unquietcode 5y ago
  Counter-opinion: your resume will likely be viewed as a PDF or printed on a piece of paper and taken into an interview session, so all that really matters it how it looks on a standard size page for the region in which you're applying.
  - xyzzy_plugh 5y ago
    I find most resumes are slurped into a database, losing all formatting, then rendered real shitty on greenhouse or something. I send a PDF and plaintext, but I prefer just sending plaintext usually.
  - thrwyoilarticle 5y ago
    That's if it gets viewed at all. I have sat with an interviewer correcting all the information that their ATS misread. Apple's ATS did not properly ingest my PDF LaTeX CV.
- paulgb 5y ago
  LaTeX has good typography. I'd rather look at a LaTeX resume with a decent template than an MS Word one. Plus, with LaTeX you can use version control. Markdown doesn't give you the level of control most people want in their resume layout. Edit: also, I agree that Computer Modern can come off as signaling (although, in quant finance, I found it to be a useful and positive signal). But using other fonts it doesn't have the same connotations and just looks a bit more polished.
  - deleted 5y ago
    [deleted]
- JustFinishedBSG 5y ago
  > If, in your job, you were trying to express technical information, you wouldn't use LaTeX. I would, and do, use TeX. Hell I'd use LaTeX for everything if I could.
  - bradrn 5y ago
    Completely agreed. Except for the very very few cases where Word is better (e.g. printing out lots of pictures), I make a point of using LaTeX whenever possible. It’s just so much less painful than anything else.
    - thrwyoilarticle 5y ago
      This you? https://github.com/bradrn/brassica/blob/master/README.md https://github.com/bradrn/brassica/blob/master/README.md
      - bradrn 5y ago
        Yes, that’s me. Why do you ask?
        thrwyoilarticle 5y ago
        Doesn't look like LaTeX
        bradrn 5y ago
        OK, perhaps I should have added a qualifier to my previous statement: when making offline documents, I use LaTeX whenever possible. Generally speaking, PDFs in a web browser aren’t particularly nice to read, so LaTeX doesn’t work so well with online documents. As for your specific example: if the entire project is already on GitHub, of course the sensible decision is to use Markdown, since that’s GitHub’s native format. (And if Markdown isn’t enough, then I’ll fall back to LaTeX: e.g. documentation for [0].) For non-web documents, however, I always use LaTeX in all but a small number of situations. [0] https://github.com/bradrn/Conkey https://github.com/bradrn/Conkey
- bobbylarrybobby 5y ago
  Does anybody really care what you use to generate your resume? LaTeX produces nice looking PDF output, is semantic (\cvitem{...}) and is modularized (if you're using OpenCV, you can change the layout with one line).
  - Communitivity 5y ago
    I've been meaning to use OpenCV, as I need to sharpen up my resume again (every 3 years). Do you have any resources you would recommend? I've used OverLeaf [1] and a tweaked Shawn Pan's 'Resume for a Software Engineer' template [2] in the past. [1] https://www.overleaf.com/ https://www.overleaf.com/ [2] https://www.overleaf.com/latex/examples/resume-template-for-software-engineer/fvsqzcybnwdn https://www.overleaf.com/latex/examples/resume-template-for-...
  - OJFord 5y ago
    There's a LaTeX curriculum vitae template called 'OpenCV'? That's brilliant. I use LaTeX for mine, not because of some misguided sense of street cred, but just because I want it version controlled. I'm sure there are some nice pandoc templates for styling markdown CVs, but AwesomeCV for LaTeX CVs was what I came across, and has worked fine (roughly, it's abandonware that I've tweaked/fixed a bit but nobody's PRs get merged) since. My CV doesn't say 'proudly generated with heart emojis in LaTeX', or anything like that, it's just the tool I happened to use.
  - bobbylarrybobby 5y ago
    Edit: whoops, it's moderncv, not openvc.
    - exdsq 5y ago
      Ha! I was about to ask if you meant you could changing your CV around with computer vision Edit: Wait... OpenVC? ;)
- pow_pp_-1_v 5y ago
  I am building a LaTex resume. Why? Because I hate working on my resume and doing it with markup and other stuff makes it a bit more... bearable? Yeah, I know, I am weird.
- actually_a_dog 5y ago
  You can skip doing all that formatting work yourself by using a good template. If you choose a 1-column layout, ATS probably won't bork it any more than any other PDF, too. Here are a bunch of templates that range from decent-looking to beautiful: https://www.overleaf.com/gallery/tagged/cv https://www.overleaf.com/gallery/tagged/cv
- Communitivity 5y ago
  I agree on your main point, in a weaker wording: 'LaTeX resumes/CVs rarely make sense', but not for the reason you gave, and I disagree with not using LaTeX in general for technical information. The reason I think LaTeX resumes/CVs rarely make sense is that there are a number of HR departments that require them in MS Word format (often this is a SharePoint house and yes, I think that bizarre, but that is what I've found). LaTeX can be converted to Word doc, but in my experience always requires tweaking. For sharing technical work, I think it depends on your audience. A connected team with a decent wiki or document generation pipline authoring informal technical how-tos or status intended for the team only? Then some flavor of markdown (I prefer Creole) can make perfect sense. Authoring anything for team external use should use a well defined community standard (rustdoc, rst, etc.) if what's being documented is specific to that community (Rust code, Python code, etc.). Authoring anything of a more technical nature (papers, how-tos to be delivered to a client, CONOPS) should be authored in a pipeline that starts with a text based format, so that you can put it under good version control (opinionated, but SharePoint/Word do not count for that for me). I prefer LaTeX for that format. Some prefer Docbook, some DITA, and I've even seen a TOML version. This gets you version control, document section re-use, and fine-grained control over document layout. Note I said should. Some potential barriers to that are: * Skillsets - the rest of the team does not know Docbook, DITA, or LaTeX and may be resistant to learn. This will make it a hard sell to management. * Time - The project does not have the budget or scope to change how documentation is being done, according to management. In reality, this pipeline will save time in editing, and improve quality delivered to the client or end customer. * NIH/NIMBY - Not Invented Here and it's more obstinate brother, Not In My Backyard. If your shop has always done it a certain way, then the team may be resistant to changing. Especially if the way it has been done is reflective of a Windows world (MS Word, MS PowerPoint). If management is part of this problem, move. Only partially kidding, but a good document pipeline will be a hard sell. What do you do if you cannot sell a good document pipeline? You could version control your MS Word documents in Git through conversion[1], but this means you might lose some of the little tweaks your manager did to improve quality/put their stamp on the doc. Another option is that MS Word has track changes, and you may be stuck with a combination of track changes and SharePoint/Confluence versioning. Another option, which I've never tried, is to unzip the MS .docx file into a folder (each .docx file is a zip of a bunch of files, most them text), git version control that folder, and re-zip it up when needed. Not sure how well git diffs will work in this situation though. My guess it probably not well, but maybe better than nothing. [1] https://blog.front-matter.io/mfenner/using-microsoft-word-with-git https://blog.front-matter.io/mfenner/using-microsoft-word-wi...
- wycy 5y ago
  Having my resume in LaTeX offers a nice perk I haven't seen mentioned in the replies yet: under each section you can put a ton of different bullet points all commented out, and simply uncomment the most relevant ones for each job you're applying to.
  - c618b9b695c4 5y ago
    I do the same. It is nice because I not only add a bullet point, but I can also keep in-line comments to remind me what the project was years down the road. %\item{Built internal dashboard for foo} % this was that awful project for <person> where they changed the requirements at the last second and yada yada...
- globular-toast 5y ago
  > If, in your job, you were trying to express technical information, you wouldn't use LaTeX. If it was for print then yes, I would. But a CV isn't technical information so I'm not sure what your point is here. Have you considered that LaTeX might be the only typesetting tool I know? Why would I learn another piece of software just to typeset my CV?
  - thrwyoilarticle 5y ago
    Well I think a CV is technical information and I do know more than one typesetting tool.
smokey_circles 5y ago
Tangential question: I've used both Manjaro and Arch and Manjaro is far away my favorite distribution, because (to me at least) it's Arch for the lazy. I ran Arch for years before Manjaro and so maybe that's the reason, but I don't believe Manjaro abstracts you away from nuts and bolts layer as much as Ubuntu does? INB4 the ubuntu comment: I know, I know. You can still do a lot of fiddling under the hood, it's just not in a manner i'd describe as "the linux way". There are a lot of helper layers that break if you try to subvert them, but i will admit that update-alternatives is the only example coming to mind now
- SkyMarshal 5y ago
  I recently spent some time evaluating a bunch of different systems for migrating away from Ubuntu, including several Arch-based ones. I was the most impressed with Manjaro, it seems very well polished. From Gnome 40 on Wayland, to the the default ZFS shell with custom Powerline prompt, to the GUI desktop layout switcher which even includes the tiling PoP Shell as an option. The Manjaro team has done an excellent job at assembling a configuration that is simultaneously power-user-focused but also user-friendly.
  - smokey_circles 5y ago
    Absolutely! I just wish there'd be some more love on architect. But maybe I need to learn more about the default installer, I couldn't get it to run on LVM and/or LUKS
    - SkyMarshal 5y ago
      The default installer offers an option to encrypt the disk, meaning LUKS + LVM. (iirc, LUKS requires LVM, but correct me if I'm wrong). The only main shortcoming of the installer is, in 2021 it really needs to also offer btrfs as an option for automatic installation. Basically four options for automatic install: Ext4, btrfs, LUKS+Ext4, and LUKS+btrfs. Having recently migrated to ZFS, and quickly become accustomed to the immense flexibility of datasets/subvolumes, snapshotting, and checksumming, I can't imagine using anything other than ZFS or btrfs now. And btrfs is standard on Fedora 34 and Garuda, probably some other distros too.
kosolam 5y ago
Nice! Rust as first language. You must be something special. I suggest employers to check this guy out.
- Communitivity 5y ago
  Going to drop a link to Paul Graham's Hierarchy of Disagreement diagram here [1]. I've upvoted you to give you the benefit of the doubt, because your comment could be taken as either positive, or negative. Based on the other comments in your profile I think you genuinely intended a positive meaning for your complement. [1] https://en.wikipedia.org/wiki/File:Graham%27s_Hierarchy_of_Disagreement.svg https://en.wikipedia.org/wiki/File:Graham%27s_Hierarchy_of_D...
  - kosolam 5y ago
    Hey! Thanks! Indeed the comment is meant to be a compliment to this guy. I truly believe that if he managed the learning curve of Rust in addition with that being his first programming language, it means that he is quite strong and has potential to bring value to his future employer.
fecak 5y ago
Professional resume writer here. Quick review. We don't use first person voice on resumes. We use 'implied first person' (no 'I'). So "Former emergency response driver..." Mentioning a Twitter handle is only useful if your Twitter has things you'd want people to see. The professional experience section (Modules here) should be in reverse chronological order - so most recent first. It would be useful to say something that you did while working for RustMinded and maybe tell the reader who the company is. So it might look like: Software Developer, Rustminded $DATE_- present RustMinded is a Belgian startup dedicated to the promotion of the Rust language. As others have said, I don't really get the fascination with LaTeX. I get a lot of incoming resumes from my tech clients that are written in LaTeX. It feels more like "I built it using LaTeX to try and impress you" than "it's the best tool for the job". The project sections are mostly OK other than some language issues.
- foldr 5y ago
  Grammar nitpick: first person is not a voice.
  - bradrn 5y ago
    Furthermore, I’d describe GP’s comment as encouraging ‘pro-drop’ rather than any ‘voice’. (Though I suspect the technical details of syntactic terminology are somewhat irrelevant for résumé-writing.)
    - deleted 5y ago
      [deleted]
    - foldr 5y ago
      I'm afraid pro drop isn't technically right either, for a couple of reasons :D First, English doesn't have pro drop. Second, there's more than just the subject missing in "Former emergency response driver...". If you read it as elliptical of a sentence, then the sentence is something like "I am a former emergency response driver...". If English had pro drop, pro drop would give you "Am a former emergency response driver..."
follownotrend 5y ago
To OP - I think the resume is a clever format, and riding a language's popularity is a great way of putting yourself out there, especially as a junior. To others, the "Traits" section -- how much impact does this really matter to the hiring managers? You're hired for what you know, but you're fired for who you are. Is it worth it to expand on these "traits", or is it a fluff area that can be replaced with something more meaningful?
- onei 5y ago
  For hiring software devs, I don't care about soft skills on a CV. If I'm concerned, I'll pull that thread in an interview. I'd much rather see those traits demonstrated rather than claim you have them and fall short of my expectations. Recently, I've also seen people put progress bars for soft skills on a CV, as if they're close to mastering the skill or at least levelling up. It normally takes up a lot of space and is virtually meaningless.
  - exdsq 5y ago
    Was once hiring for a IT Support role and someone applied with a star-based system for their skills. I still to this day do not know what 4.5 Stars in "Cables" could ever possibly mean.
- minxomat 5y ago
  For soft skills, saying "can do X" isn't useful. The only written example that I'd even consider is you demonstrating X as part of a written sample (STAR answer), or BQ during an interview.
actually_a_dog 5y ago
My impression: this is cute, but confusing. I don't like having to mentally translate things like "modules" and "constants" into headings that would appear in a resume.
paulgb 5y ago
As usual with quirky resumes, I think a lot of people are missing the point. Nobody is suggesting that we all start using rustdoc for our resumes. It's a fun, different way of presenting a resume. The fact that it made it to the front page of HN means it worked at what it was intended to do: be seen by a bunch of prospective employers and stand out.
- PragmaticPulp 5y ago
  > Nobody is suggesting that we all start using rustdoc for our resumes. Maybe nobody is suggesting it, but these clever resume formats tend to inspire a lot of copycats in my experience. When infographic resumes went through waves of popularity on social media I started receiving a lot of poorly constructed infographic-style resumes. Most of them came from junior candidates who thought they were going to stand above the crowd and impress us with their ingenuity. Maybe 1 out of every 10 was actually well-designed. The rest were just needlessly cryptic and failed to deliver the information I actually needed to see in a resume format. For example, I don’t want to see that someone rates themselves as 4/5 stars in Python. I need to see some text that explains their Python experience. After reading 50 resumes in a row, the last thing I want to do is parse my way through non-standard resume formats. This Rustdoc resume comes close to looking like a normal resume, which is good, but I would strongly suggest the author add a link at the beginning to a regular PDF resume that can be downloaded and shared. The full resume should expand on the normal resume points, such as explaining their role and responsibilities at their current job and adding dates to employment ranges.
  - chc 5y ago
    Like 90% of the job interviews I've been to have asked me something along the lines of "rate yourself on a scale of 1-10 on these technologies," so maybe you don't want to see 4/5 stars in Python, but it does seem to be a pretty common wish.
    - teddyh 5y ago
      The interviewer asking the question and the person reading the résumé are not looking for the same information, and may often be entirely different people.
dwenzek 5y ago
I'm missing the integration tests ;-)
jaimie 5y ago
I really like your header. As someone that makes hiring decisions, starting by showing your curiosity and reasoning as clearly as the Linux example, then immediately casting your mentorship and current position as an opportunity shows that you will be an engaged coworker that can push things to the next level. The resume itself showing that creative thinking. It's not so much the way the content is presented, as much as the content itself!
pkolaczk 5y ago
If the resume has a good content, the only rule IMHO is it needs to be easy to read. It doesn't matter if you use LaTeX, Rustdoc, MS Word, Libre Office, HTML or markdown as long as I can quickly get all the information I want. When I dealt with hiring for my team, I've never paid any attention to the formatting. Making formatting stand out from other resumes did not increase the chances for the resume to be picked and moved to the next stage. It did decrease them though, if crazy formatting made it harder to read. Using Rustdoc might be "clever", but I don't find this resume very readable honestly. It took me some time to figure out what modules or structs mean in this context. Don't do this. Recruiters have really little time and they often get hundreds of resumes. If they can't get the essential information quickly enough, they'll just throw it out. What makes an outstanding resume is in the content and how well it matches the job requirements. If I'm looking for a database engine expert and I get 999 resumes which all mention building websites in JS or machine learning models in Python, but one mentions experience on Linux kernel performance work (proven by accepted patches), which one do you think I'd choose?

122 points by 1f60c 5y ago

Opinion: LaTeX resumes/CVs don't make any sense. If, in your job, you were trying to express technical information, you wouldn't use LaTeX. You might use it for a paper or a book where you have a lot of content or multiple issues that you want to look consistent. But a resume is a single, small document with multiple different sections that have different formatting requirements. In your job, you probably share information in markdown or rst. If you're looking to signal - and let's be honest, with LaTeX you are - why not use those? Bonus: ATS systems and recruiters won't bork your input.

tyingq 5y ago
Assuming the LaTeX resume would be shared with a recruiter as a pdf, is there really any difference? I could render the markdown with the Computer Modern font and many people would assume LaTeX.
- JustFinishedBSG 5y ago
  > I could render the markdown with the Computer Modern font You really shouldn't though. Computer Modern is a pretty ugly font. At least use something like New Computer Modern if you really need a Scoth Roman font with maths.
- Sharlin 5y ago
  As an aside, in 2021 Computer Modern looks really dated, especially for content that’s predominantly text rather than math. There are much better, more Unicode-friendly, and more typographically complete LaTeX fonts available.
  - est31 5y ago
    Which fonts would you recommend?
    - Sharlin 5y ago
      Recently I've been using `mathpazo` which is Palatino extended with matching math symbols (if math is needed; if not, just use plain `palatino`). Specifically, I use `mathpazo` with smallcaps and old-style figures enabled: \usepackage[sc,osf]{mathpazo}
      - Sharlin 5y ago
        (And yes, I realize that the original Palatino actually predates Computer Modern :D)
unquietcode 5y ago
Counter-opinion: your resume will likely be viewed as a PDF or printed on a piece of paper and taken into an interview session, so all that really matters it how it looks on a standard size page for the region in which you're applying.
- xyzzy_plugh 5y ago
  I find most resumes are slurped into a database, losing all formatting, then rendered real shitty on greenhouse or something. I send a PDF and plaintext, but I prefer just sending plaintext usually.
- thrwyoilarticle 5y ago
  That's if it gets viewed at all. I have sat with an interviewer correcting all the information that their ATS misread. Apple's ATS did not properly ingest my PDF LaTeX CV.
paulgb 5y ago
LaTeX has good typography. I'd rather look at a LaTeX resume with a decent template than an MS Word one. Plus, with LaTeX you can use version control. Markdown doesn't give you the level of control most people want in their resume layout. Edit: also, I agree that Computer Modern can come off as signaling (although, in quant finance, I found it to be a useful and positive signal). But using other fonts it doesn't have the same connotations and just looks a bit more polished.
- deleted 5y ago
  [deleted]
JustFinishedBSG 5y ago
> If, in your job, you were trying to express technical information, you wouldn't use LaTeX. I would, and do, use TeX. Hell I'd use LaTeX for everything if I could.
- bradrn 5y ago
  Completely agreed. Except for the very very few cases where Word is better (e.g. printing out lots of pictures), I make a point of using LaTeX whenever possible. It’s just so much less painful than anything else.
  - thrwyoilarticle 5y ago
    This you? https://github.com/bradrn/brassica/blob/master/README.md https://github.com/bradrn/brassica/blob/master/README.md
    - bradrn 5y ago
      Yes, that’s me. Why do you ask?
      - thrwyoilarticle 5y ago
        Doesn't look like LaTeX
        bradrn 5y ago
        OK, perhaps I should have added a qualifier to my previous statement: when making offline documents, I use LaTeX whenever possible. Generally speaking, PDFs in a web browser aren’t particularly nice to read, so LaTeX doesn’t work so well with online documents. As for your specific example: if the entire project is already on GitHub, of course the sensible decision is to use Markdown, since that’s GitHub’s native format. (And if Markdown isn’t enough, then I’ll fall back to LaTeX: e.g. documentation for [0].) For non-web documents, however, I always use LaTeX in all but a small number of situations. [0] https://github.com/bradrn/Conkey https://github.com/bradrn/Conkey
bobbylarrybobby 5y ago
Does anybody really care what you use to generate your resume? LaTeX produces nice looking PDF output, is semantic (\cvitem{...}) and is modularized (if you're using OpenCV, you can change the layout with one line).
- Communitivity 5y ago
  I've been meaning to use OpenCV, as I need to sharpen up my resume again (every 3 years). Do you have any resources you would recommend? I've used OverLeaf [1] and a tweaked Shawn Pan's 'Resume for a Software Engineer' template [2] in the past. [1] https://www.overleaf.com/ https://www.overleaf.com/ [2] https://www.overleaf.com/latex/examples/resume-template-for-software-engineer/fvsqzcybnwdn https://www.overleaf.com/latex/examples/resume-template-for-...
- OJFord 5y ago
  There's a LaTeX curriculum vitae template called 'OpenCV'? That's brilliant. I use LaTeX for mine, not because of some misguided sense of street cred, but just because I want it version controlled. I'm sure there are some nice pandoc templates for styling markdown CVs, but AwesomeCV for LaTeX CVs was what I came across, and has worked fine (roughly, it's abandonware that I've tweaked/fixed a bit but nobody's PRs get merged) since. My CV doesn't say 'proudly generated with heart emojis in LaTeX', or anything like that, it's just the tool I happened to use.
- bobbylarrybobby 5y ago
  Edit: whoops, it's moderncv, not openvc.
  - exdsq 5y ago
    Ha! I was about to ask if you meant you could changing your CV around with computer vision Edit: Wait... OpenVC? ;)
pow_pp_-1_v 5y ago
I am building a LaTex resume. Why? Because I hate working on my resume and doing it with markup and other stuff makes it a bit more... bearable? Yeah, I know, I am weird.
actually_a_dog 5y ago
You can skip doing all that formatting work yourself by using a good template. If you choose a 1-column layout, ATS probably won't bork it any more than any other PDF, too. Here are a bunch of templates that range from decent-looking to beautiful: https://www.overleaf.com/gallery/tagged/cv https://www.overleaf.com/gallery/tagged/cv
Communitivity 5y ago
I agree on your main point, in a weaker wording: 'LaTeX resumes/CVs rarely make sense', but not for the reason you gave, and I disagree with not using LaTeX in general for technical information. The reason I think LaTeX resumes/CVs rarely make sense is that there are a number of HR departments that require them in MS Word format (often this is a SharePoint house and yes, I think that bizarre, but that is what I've found). LaTeX can be converted to Word doc, but in my experience always requires tweaking. For sharing technical work, I think it depends on your audience. A connected team with a decent wiki or document generation pipline authoring informal technical how-tos or status intended for the team only? Then some flavor of markdown (I prefer Creole) can make perfect sense. Authoring anything for team external use should use a well defined community standard (rustdoc, rst, etc.) if what's being documented is specific to that community (Rust code, Python code, etc.). Authoring anything of a more technical nature (papers, how-tos to be delivered to a client, CONOPS) should be authored in a pipeline that starts with a text based format, so that you can put it under good version control (opinionated, but SharePoint/Word do not count for that for me). I prefer LaTeX for that format. Some prefer Docbook, some DITA, and I've even seen a TOML version. This gets you version control, document section re-use, and fine-grained control over document layout. Note I said should. Some potential barriers to that are: * Skillsets - the rest of the team does not know Docbook, DITA, or LaTeX and may be resistant to learn. This will make it a hard sell to management. * Time - The project does not have the budget or scope to change how documentation is being done, according to management. In reality, this pipeline will save time in editing, and improve quality delivered to the client or end customer. * NIH/NIMBY - Not Invented Here and it's more obstinate brother, Not In My Backyard. If your shop has always done it a certain way, then the team may be resistant to changing. Especially if the way it has been done is reflective of a Windows world (MS Word, MS PowerPoint). If management is part of this problem, move. Only partially kidding, but a good document pipeline will be a hard sell. What do you do if you cannot sell a good document pipeline? You could version control your MS Word documents in Git through conversion[1], but this means you might lose some of the little tweaks your manager did to improve quality/put their stamp on the doc. Another option is that MS Word has track changes, and you may be stuck with a combination of track changes and SharePoint/Confluence versioning. Another option, which I've never tried, is to unzip the MS .docx file into a folder (each .docx file is a zip of a bunch of files, most them text), git version control that folder, and re-zip it up when needed. Not sure how well git diffs will work in this situation though. My guess it probably not well, but maybe better than nothing. [1] https://blog.front-matter.io/mfenner/using-microsoft-word-with-git https://blog.front-matter.io/mfenner/using-microsoft-word-wi...
wycy 5y ago
Having my resume in LaTeX offers a nice perk I haven't seen mentioned in the replies yet: under each section you can put a ton of different bullet points all commented out, and simply uncomment the most relevant ones for each job you're applying to.
- c618b9b695c4 5y ago
  I do the same. It is nice because I not only add a bullet point, but I can also keep in-line comments to remind me what the project was years down the road. %\item{Built internal dashboard for foo} % this was that awful project for <person> where they changed the requirements at the last second and yada yada...
globular-toast 5y ago
> If, in your job, you were trying to express technical information, you wouldn't use LaTeX. If it was for print then yes, I would. But a CV isn't technical information so I'm not sure what your point is here. Have you considered that LaTeX might be the only typesetting tool I know? Why would I learn another piece of software just to typeset my CV?
- thrwyoilarticle 5y ago
  Well I think a CV is technical information and I do know more than one typesetting tool.

smokey_circles 5y ago

Tangential question: I've used both Manjaro and Arch and Manjaro is far away my favorite distribution, because (to me at least) it's Arch for the lazy. I ran Arch for years before Manjaro and so maybe that's the reason, but I don't believe Manjaro abstracts you away from nuts and bolts layer as much as Ubuntu does? INB4 the ubuntu comment: I know, I know. You can still do a lot of fiddling under the hood, it's just not in a manner i'd describe as "the linux way". There are a lot of helper layers that break if you try to subvert them, but i will admit that update-alternatives is the only example coming to mind now

SkyMarshal 5y ago
I recently spent some time evaluating a bunch of different systems for migrating away from Ubuntu, including several Arch-based ones. I was the most impressed with Manjaro, it seems very well polished. From Gnome 40 on Wayland, to the the default ZFS shell with custom Powerline prompt, to the GUI desktop layout switcher which even includes the tiling PoP Shell as an option. The Manjaro team has done an excellent job at assembling a configuration that is simultaneously power-user-focused but also user-friendly.
- smokey_circles 5y ago
  Absolutely! I just wish there'd be some more love on architect. But maybe I need to learn more about the default installer, I couldn't get it to run on LVM and/or LUKS
  - SkyMarshal 5y ago
    The default installer offers an option to encrypt the disk, meaning LUKS + LVM. (iirc, LUKS requires LVM, but correct me if I'm wrong). The only main shortcoming of the installer is, in 2021 it really needs to also offer btrfs as an option for automatic installation. Basically four options for automatic install: Ext4, btrfs, LUKS+Ext4, and LUKS+btrfs. Having recently migrated to ZFS, and quickly become accustomed to the immense flexibility of datasets/subvolumes, snapshotting, and checksumming, I can't imagine using anything other than ZFS or btrfs now. And btrfs is standard on Fedora 34 and Garuda, probably some other distros too.

kosolam 5y ago

Nice! Rust as first language. You must be something special. I suggest employers to check this guy out.

Communitivity 5y ago
Going to drop a link to Paul Graham's Hierarchy of Disagreement diagram here [1]. I've upvoted you to give you the benefit of the doubt, because your comment could be taken as either positive, or negative. Based on the other comments in your profile I think you genuinely intended a positive meaning for your complement. [1] https://en.wikipedia.org/wiki/File:Graham%27s_Hierarchy_of_Disagreement.svg https://en.wikipedia.org/wiki/File:Graham%27s_Hierarchy_of_D...
- kosolam 5y ago
  Hey! Thanks! Indeed the comment is meant to be a compliment to this guy. I truly believe that if he managed the learning curve of Rust in addition with that being his first programming language, it means that he is quite strong and has potential to bring value to his future employer.

fecak 5y ago

Professional resume writer here. Quick review. We don't use first person voice on resumes. We use 'implied first person' (no 'I'). So "Former emergency response driver..." Mentioning a Twitter handle is only useful if your Twitter has things you'd want people to see. The professional experience section (Modules here) should be in reverse chronological order - so most recent first. It would be useful to say something that you did while working for RustMinded and maybe tell the reader who the company is. So it might look like: Software Developer, Rustminded $DATE_- present RustMinded is a Belgian startup dedicated to the promotion of the Rust language. As others have said, I don't really get the fascination with LaTeX. I get a lot of incoming resumes from my tech clients that are written in LaTeX. It feels more like "I built it using LaTeX to try and impress you" than "it's the best tool for the job". The project sections are mostly OK other than some language issues.

foldr 5y ago
Grammar nitpick: first person is not a voice.
- bradrn 5y ago
  Furthermore, I’d describe GP’s comment as encouraging ‘pro-drop’ rather than any ‘voice’. (Though I suspect the technical details of syntactic terminology are somewhat irrelevant for résumé-writing.)
  - deleted 5y ago
    [deleted]
  - foldr 5y ago
    I'm afraid pro drop isn't technically right either, for a couple of reasons :D First, English doesn't have pro drop. Second, there's more than just the subject missing in "Former emergency response driver...". If you read it as elliptical of a sentence, then the sentence is something like "I am a former emergency response driver...". If English had pro drop, pro drop would give you "Am a former emergency response driver..."

follownotrend 5y ago

To OP - I think the resume is a clever format, and riding a language's popularity is a great way of putting yourself out there, especially as a junior. To others, the "Traits" section -- how much impact does this really matter to the hiring managers? You're hired for what you know, but you're fired for who you are. Is it worth it to expand on these "traits", or is it a fluff area that can be replaced with something more meaningful?

onei 5y ago
For hiring software devs, I don't care about soft skills on a CV. If I'm concerned, I'll pull that thread in an interview. I'd much rather see those traits demonstrated rather than claim you have them and fall short of my expectations. Recently, I've also seen people put progress bars for soft skills on a CV, as if they're close to mastering the skill or at least levelling up. It normally takes up a lot of space and is virtually meaningless.
- exdsq 5y ago
  Was once hiring for a IT Support role and someone applied with a star-based system for their skills. I still to this day do not know what 4.5 Stars in "Cables" could ever possibly mean.
minxomat 5y ago
For soft skills, saying "can do X" isn't useful. The only written example that I'd even consider is you demonstrating X as part of a written sample (STAR answer), or BQ during an interview.

actually_a_dog 5y ago

My impression: this is cute, but confusing. I don't like having to mentally translate things like "modules" and "constants" into headings that would appear in a resume.

paulgb 5y ago

As usual with quirky resumes, I think a lot of people are missing the point. Nobody is suggesting that we all start using rustdoc for our resumes. It's a fun, different way of presenting a resume. The fact that it made it to the front page of HN means it worked at what it was intended to do: be seen by a bunch of prospective employers and stand out.

PragmaticPulp 5y ago
> Nobody is suggesting that we all start using rustdoc for our resumes. Maybe nobody is suggesting it, but these clever resume formats tend to inspire a lot of copycats in my experience. When infographic resumes went through waves of popularity on social media I started receiving a lot of poorly constructed infographic-style resumes. Most of them came from junior candidates who thought they were going to stand above the crowd and impress us with their ingenuity. Maybe 1 out of every 10 was actually well-designed. The rest were just needlessly cryptic and failed to deliver the information I actually needed to see in a resume format. For example, I don’t want to see that someone rates themselves as 4/5 stars in Python. I need to see some text that explains their Python experience. After reading 50 resumes in a row, the last thing I want to do is parse my way through non-standard resume formats. This Rustdoc resume comes close to looking like a normal resume, which is good, but I would strongly suggest the author add a link at the beginning to a regular PDF resume that can be downloaded and shared. The full resume should expand on the normal resume points, such as explaining their role and responsibilities at their current job and adding dates to employment ranges.
- chc 5y ago
  Like 90% of the job interviews I've been to have asked me something along the lines of "rate yourself on a scale of 1-10 on these technologies," so maybe you don't want to see 4/5 stars in Python, but it does seem to be a pretty common wish.
  - teddyh 5y ago
    The interviewer asking the question and the person reading the résumé are not looking for the same information, and may often be entirely different people.

dwenzek 5y ago

I'm missing the integration tests ;-)

jaimie 5y ago

I really like your header. As someone that makes hiring decisions, starting by showing your curiosity and reasoning as clearly as the Linux example, then immediately casting your mentorship and current position as an opportunity shows that you will be an engaged coworker that can push things to the next level. The resume itself showing that creative thinking. It's not so much the way the content is presented, as much as the content itself!

pkolaczk 5y ago

If the resume has a good content, the only rule IMHO is it needs to be easy to read. It doesn't matter if you use LaTeX, Rustdoc, MS Word, Libre Office, HTML or markdown as long as I can quickly get all the information I want. When I dealt with hiring for my team, I've never paid any attention to the formatting. Making formatting stand out from other resumes did not increase the chances for the resume to be picked and moved to the next stage. It did decrease them though, if crazy formatting made it harder to read. Using Rustdoc might be "clever", but I don't find this resume very readable honestly. It took me some time to figure out what modules or structs mean in this context. Don't do this. Recruiters have really little time and they often get hundreds of resumes. If they can't get the essential information quickly enough, they'll just throw it out. What makes an outstanding resume is in the content and how well it matches the job requirements. If I'm looking for a database engine expert and I get 999 resumes which all mention building websites in JS or machine learning models in Python, but one mentions experience on Linux kernel performance work (proven by accepted patches), which one do you think I'd choose?