HN user

uhgrippa

14 karma

SWE, I like math and tinkering with embedded systems

https://github.com/athola

Posts1
Comments11
View on HN

I know I know, yet another resume generation project. The ones I've encountered built in python are either inactive or didn't quite address what I wanted in a quick generation engine to update my resume for different job postings. I became frustrated with other tools and declined to pay money for an online service, so here we are.

This is a CLI tool which allows for defining resume content in a single YAML file and then generating PDF, HTML, or LaTeX rendered resumes from it. The idea is to write the configuration once, then be able to render it in a variety of different iterations.

Some key details:

It comes with a few templates and color schemes that you can customize.

For academic use, the LaTeX output gives you precise typesetting control.

There's a Python API if you want to generate resumes programmatically. It's designed to have a limited surface area to not expose inner workings, only the necessary structures as building blocks.

The codebase has over 90% test coverage and is fully type-hinted. I adhered to a functional core, imperative shell architecture (after reading a recent post about it here!)

Example YAML:

  template: resume_base
  full_name: Jane Doe
  job_title: Software Engineer
  email: jane@example.com
  config:
    color_scheme: "Professional Blue"

  body:
    experience:
      - title: Senior Engineer
        company: TechCorp
        start: 2022
        end: Present
        description: |
          - Led microservices architecture serving 1M+ users
          - Improved performance by 40% through optimization
Generate with:
  uv run simple-resume generate --format pdf --open

May be a poor example, it’s what came to mind initially. I don’t think the end results are at all the same but I think the initial emotions around why you may balk at something new entering your community have parallels to the topic at hand.

Yeah I certainly don’t want to mischaracterize anyone here and I attempted to communicate how this is really a knee-jerk, human reaction to something new making inroads into a space people have extensive expertise in. New ideas additionally shouldn’t be derided based upon the poor behavior of some in the community.

Fair, I acknowledge I may have misrepresented this group who are against the Rust community as not being experts in this this space; they certainly are. Rust doesn’t have to be the answer but if we treat others (namely Rust supporters) and their solutions as dead-on-arrival because it’s implemented in a technology we’re not entirely familiar with how can we get to a point where we’re solving difficult problems? Especially if we create an unwelcoming space for contribution?

These are often the same classification of individual who tend to modify their viewpoints towards “change is progressing rapidly in an area that I don’t understand and this scares me.” Anytime an expert in a particular area has their expertise challenged or even threatened by a new technology it is perfectly human to react in a way that is defensive towards the perceived threat. Part of growth as a human is recognizing our perceived biases and attempting to mitigate them, hopefully extending this into other areas of our lives as well. After all, NIMBYS probably started out with reasonable justifications for why they want to keep their communities the way they currently are - it’s comfortable and it works, and they’re a significant contributor to the community. Any external “threat” to this concept becomes elevated to a moral crusade against the invaders who are encroaching upon their land, when really they’re jousting against windmills.