[HN Gopher] Rustdoc resume
___________________________________________________________________
Rustdoc resume
Author : 1f60c
Score : 107 points
Date : 2021-08-16 12:44 UTC (10 hours ago)
(HTM) web link (yozhgoor.github.io)
(TXT) w3m dump (yozhgoor.github.io)
| actually_a_dog wrote:
| 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.
| smokey_circles wrote:
| 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
| zozbot234 wrote:
| Debian is Arch for the lazy. It's also Arch for the
| professional who understands the pitfalls of the "rolling"
| release model.
| arsome wrote:
| Yeah, I remember Arch breaking systems completely back when
| they moved the entire /bin and /lib, setting python3 as the
| default python, etc. Took hours of fucking around to fix.
|
| I'm a tinkerer typically, but it seemed like they were going
| out of their way to break things and generate maintenance
| work for me, I've never had that issue with any other distro
| and I will never run Arch again because of it.
| vlovich123 wrote:
| That's a bold claim considering Homebrew has been wildly
| successful on Mac & been doing the whole rolling release
| thing the entire time. Everything in the world is tradeoffs
| so I can also say "Arch is for the professional who
| understands the pitfalls of random OS distro updates/patches
| to upstream packages that don't get updated for years".
| smokey_circles wrote:
| I'm likely too young to fully appreciate that sentiment, but
| fair enough!
| dmos62 wrote:
| If you want the Linux-way, nuts-and-bolts Slackware is where
| it's at. Slackware and Void Linux were my favorite distros.
| These days I'm just using Ubuntu for plug-and-play convenience.
| dcminter wrote:
| > [Ubuntu] 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".
|
| I use and like Ubuntu, but I have to agree with this. Even
| before I finished reading this paragraph I was thinking of
| update-alternatives. Networking config springs to mind as well
| for me.
| SkyMarshal wrote:
| 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.
| SkyMarshal wrote:
| _> to the the default ZFS shell_
|
| Correction: ZSH shell.
| JanMa wrote:
| I definitely agree with you. Manjaro is a great distro and I
| have used for multiple years. I especially liked that they
| offer such a broad range of supported desktop environments,
| each with their own downloadable ISO image.
|
| If you are looking for something that's closer to pure Arch
| under the hood, your should give Endeavour OS [0] a try. It's
| basically vanilla Arch with a nicely configured XFCE desktop
| and a graphical installer.
|
| [0]: https://endeavouros.com/
| smokey_circles wrote:
| 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 wrote:
| 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 wrote:
| Nice! Rust as first language. You must be something special. I
| suggest employers to check this guy out.
| Communitivity wrote:
| 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_D...
| jaimie wrote:
| 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!
| paulgb wrote:
| 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 wrote:
| > 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 wrote:
| 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 wrote:
| The interviewer asking the question and the person reading
| the resume are not looking for the same information, and
| may often be entirely different people.
| paulgb wrote:
| IMHO as an interviewer, when I see these: the rank-order
| is useful, so that if you put C++ first I might ask you a
| different question than if you put Python. But the
| absolute star ratings are just noise; most candidates
| just use an implicitly-ranked list which is a more
| concise way of communicating the same information.
|
| I've never asked a candidate to rank themselves on a
| skill out of 10, that seems like a low-signal way to
| filter for overconfident people.
| thrwyoilarticle wrote:
| 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.
| JustFinishedBSG wrote:
| > 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.
| thrwyoilarticle wrote:
| You're in the minority. I haven't seen any LaTeX readmes on
| github.
| bradrn wrote:
| 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 wrote:
| This you?
|
| https://github.com/bradrn/brassica/blob/master/README.md
| bobbylarrybobby wrote:
| 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).
| OJFord wrote:
| 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 wrote:
| Edit: whoops, it's moderncv, not openvc.
| exdsq wrote:
| Ha! I was about to ask if you meant you could changing your
| CV around with computer vision
|
| Edit: Wait... OpenVC? ;)
| Communitivity wrote:
| 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/
|
| [2] https://www.overleaf.com/latex/examples/resume-template-
| for-...
| pow_pp_-1_v wrote:
| 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.
| Communitivity wrote:
| 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-
| wi...
| wycy wrote:
| 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 wrote:
| 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...
| tyingq wrote:
| 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 wrote:
| > 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 wrote:
| 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 wrote:
| Which fonts would you recommend?
| Sharlin wrote:
| 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 wrote:
| (And yes, I realize that the original Palatino actually
| predates Computer Modern :D)
| globular-toast wrote:
| > 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 wrote:
| Well I think a CV is technical information and I do know more
| than one typesetting tool.
| unquietcode wrote:
| 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 wrote:
| 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 wrote:
| 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 wrote:
| 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]
| actually_a_dog wrote:
| 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
| fecak wrote:
| 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.
| dcminter wrote:
| > We don't use first person voice on resumes. We use 'implied
| first person' (no 'I').
|
| Who is "we" here? I've always had good results with a first
| person CV - so far in the US, the UK, and the EU. Maybe I just
| get away with it by luck or circumstance, but it's clearly not
| a set-in-stone requirement.
|
| > It feels more like "I built it using LaTeX to try and impress
| you" than "it's the best tool for the job".
|
| Anecdotally a friend who at that time worked at Sun
| Microsystems told me that his team prioritised CVs created with
| LaTeX over all others.
|
| After all, if the purpose of a CV is not to "try and impress
| you" then what is it?
| fecak wrote:
| Not using "I" on a resume is pretty much the first rule of
| resume writing. If you were to search for rules of resume
| writing, I expect that would probably appear on every
| article. If you've had good results with a first person CV,
| that's probably because your experience is strong enough that
| the reader forgives you for the error.
|
| Of course you 'can' write a resume in first person. It's just
| not the voice that the reader expects. Similar to third
| person.
|
| A resume is certainly meant to try and impress the reader,
| but typically we're trying to impress the reader with
| professional accomplishments. I'm much more impressed by
| someone's professional accomplishments than their choice to
| use LaTeX.
| volta83 wrote:
| Since you are openly advocating for people to blindly
| follow this rule... can you at least explain _why_ do you
| think this rule makes sense and people should follow it.
|
| When I hire, I couldn't care less about whether the person
| uses I or We.
| dcminter wrote:
| A not-very-thorough search for CV and Resume writing and
| skimming through the results and I don't find anyone
| mentioning the importance of avoiding the first person.
|
| That actually surprises me, because while I don't think
| it's good advice I did think it was common.
| lstamour wrote:
| To echo that, it's not that the resume authoring doesn't
| matter, but saying you made it in LaTeX is better said in
| the cover letter where you can highlight how that's
| relevant to the role or why you did so.
|
| Most resumes are processed and chopped up by ancient
| applicant tracking systems, so you sometimes have to stick
| to the facts in a resume with a plain layout. These ATS
| systems rank resumes by relevance, generally based on job
| ad keyword matching and matching against some synonyms not
| mentioned in the ad.
|
| I've had early success with a less traditional resume
| layout but I know I was picked due to relevant experience
| even then. Experience, relevance and luck/perseverance are
| probably the three keys to landing a job quickly.
| thom wrote:
| What's the basis for this advice? Have you tested A/B
| tested it with your clients?
| dcminter wrote:
| In fairness, A/B testing this approach would be ethically
| very iffy, _particularly_ if they believe it makes a
| difference!
| [deleted]
| monocasa wrote:
| I've heard both equally strongly. That 'I' is a big no no,
| and not using 'I' is a sign of the fact that you didn't
| actually contribute anything and you're riding on the
| coattails of your team as the 'useless group project
| member'.
| dvdkon wrote:
| I don't think a novelty resume needs to be so conventional,
| people will mostly, in my opinion, either dislike it for not
| following layout/organisation conventions or look past all that
| altogether.
| fecak wrote:
| For someone like this with little experience, being
| unconventional is probably OK because they aren't being
| judged by the same criteria as an experienced hire. That
| said, you can be unconventional and still provide the reader
| with the basic facts they'd want to know (like 'what are your
| accomplishments?' or 'did you attend school?').
| foldr wrote:
| Grammar nitpick: first person is not a voice.
| bradrn wrote:
| 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 resume-writing.)
| [deleted]
| foldr wrote:
| 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..."
| bradrn wrote:
| > English doesn't have pro drop
|
| Depends on the situation! For me it's grammatical in most
| informal texts, e.g. emails. (Also, the first sentence of
| this paragraph.)
|
| > Second, there's more than _just_ the subject missing in
| "Former emergency response driver...".
|
| This is a good point; I did indeed miss this subtlety.
| (Actually, it's not even very subtle!) In this case, I
| must admit to being unsure about how to analyse this.
| foldr wrote:
| >Depends on the situation! For me it's grammatical in
| most informal texts, e.g. emails. (Also, the first
| sentence of this paragraph.)
|
| This isn't technically pro drop. It's a different process
| called "diary drop". By coincidence I wrote a rant about
| this only a few days ago:
|
| https://news.ycombinator.com/item?id=28127035
| bradrn wrote:
| Huh, interesting -- thanks for the pointer! I've been
| wondering about this for a while. Do you happen to have
| any more resources? (I enjoy linguistics, but haven't
| really read much about syntax; my favourite topic is
| morphosyntactic alignment.)
| foldr wrote:
| It's hard to find any good scholarly references on the
| differences between pro drop and diary drop (I guess
| because they are uncontroversial and not particularly
| subtle). However, section 4.2.1 of this MA dissertation
| has a decent, though very brief, summary:
| https://awweir.files.wordpress.com/2017/04/weir-ug-
| diss.pdf Similar observations are also made in the
| following paper:
| https://core.ac.uk/download/pdf/76381796.pdf
| bradrn wrote:
| Again, thanks! I'll read through these when I get some
| time.
| sampo wrote:
| > It feels more like "I built it using LaTeX to try and impress
| you"
|
| It's not meant to impress you, a resume writer. It's meant to
| impress other techies.
| UnpossibleJim wrote:
| Out of sheer curiosity (and this has nothing to do with the
| conversation at large), how does one become a "professional
| resume writer"? Is that a recruiter who helps write resumes, or
| are you solely focused on resume writing? Is it a side gig, or
| do you do enough resume writing to make it a full time job?
|
| I apologize if these are well known answers but I stick with a
| fairly technical crowd and, well word of mouth usually gets us
| passed around to be brutally honest. I hate to admit it, but a
| half way legible resume and it's usually just references after
| a point =/
| baby wrote:
| > We don't use first person voice on resumes. We use 'implied
| first person' (no 'I'). So "Former emergency response
| driver..."
|
| Sorry but no, that's bad advice.
| xondono wrote:
| > As others have said, I don't really get the fascination with
| LaTeX
|
| LaTex is really powerful when you get to a certain point, but
| unless you've tinkered with it until you reach that point, it's
| a PITA.
|
| To me the number 1 advantage is that I can easily keep updated
| various versions of the CV, because by working at startups I've
| always have to wear a lot of hats. I keep a more 'hardware
| oriented' CV, another more 'software oriented' CV, and I added
| a more "management" version that showcases better team
| leadership instead on focusing on the tech stack.
|
| It's also very handy to keep everything as text documents when
| you are asked to submit to different webforms, and being able
| to adjust things like quality vs pdf size is important when
| submitting your CV in some places
| cies wrote:
| > I built it using LaTeX to try and impress you
|
| I built my LaTeX resume trying to impress a potential employer
| yeeears ago. So far it's really easy to keep up to date and to
| temporarily remove parts (comment them out). I think the end
| result looks a bit more professionally type-set than a
| Word/GDocs creation.
| bennylope wrote:
| > As others have said, I don't really get the fascination with
| LaTeX.
|
| I have gone down this path with other types of documents
| (reports, proposals) not because I love LaTeX but because I
| hate composing and editing in Word, etc. Especially for long
| lived or repeated documents. Some of those tech clients might
| just prefer working with plain text for editing, source
| control, and/or version branching.
| dhosek wrote:
| I used to do my resume in a custom TeX format.1 It looked
| gorgeous. But because so much of tech world hiring is
| mediated by recruiters and automated resume ingestion
| systems, having a straightforward document in Word ended up
| serving me much better.
|
| 1. An ancient resume macro (and an ancient resume) that I
| made while a freshman in college is on CTAN. What I used in
| my early career was not that, although I doubt I have any
| relic of that later file anymore.
| kemiller2002 wrote:
| You've never really "lived" until you realize that your
| document with the different sections, etc. that you've
| painstakingly setup is broken because of a copy paste issue
| when adding a new section. LaTex maybe a pain, but at least
| the output is consistent. There is no magic where the
| formatting bleeds over due to something you can't see on
| screen.
| im3w1l wrote:
| The odt format is xml in a zip and simple enough that you
| can hand edit it if you really want to.
| thrwyoilarticle wrote:
| Underfull \hbox (badness 10000)?
| cookieswumchorr wrote:
| I never had the time/brains to get past the learn curve with
| LaTeX. Recently I started using a pipeline of markdown to
| html with Pandoc and then to pdf with Dompdf for project
| documentation.
|
| Turns out you get neatly formatted printable docs with not so
| much effort, and the raw markdown stays with the code where
| it can be used and updated by fellow devs
| jjjbokma wrote:
| Fwiw, I have made a LaTeX resume template [1] for Pandoc.
| Input is markdown and output is LaTeX or LaTeX rendered to
| PDF.
|
| [1] https://github.com/john-bokma/resume-pandoc
| _moof wrote:
| Ugh, LaTeX resumes. They're a dime a dozen (I've interviewed
| hundreds of engineers) and they utterly fail to make people
| stand out, which is the whole point of a resume. When I get a
| resume that was done in LaTeX from someone who isn't a
| mathematician, it makes a bad impression. I'm not saying that's
| right, or fair, but it's true. It comes off as trying to look
| smart without the substance to back it up, and because so many
| people do it, it also comes off as really unoriginal, and makes
| the resume forgettable.
|
| So please everyone, stop with the performative LaTeX. If you
| had any idea how many people do this, you'd be embarrassed.
|
| (And to add a dash of humility to this comment, I'll confess
| that I used to write my resume in LaTeX. After seeing how many
| other people do too, I stopped.)
| follownotrend wrote:
| 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?
| minxomat wrote:
| 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.
| onei wrote:
| 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 wrote:
| 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.
| dwenzek wrote:
| I'm missing the integration tests ;-)
___________________________________________________________________
(page generated 2021-08-16 23:01 UTC)