Effective date is 2023 November 1st, from L4 -> L5

Update skills, programming languages, etc. as well while there

Old NYU email is still on resume, change to Hello @JasonYao [dot]] com instead

Background

• Currently, font awesome 4 is being used in the travis environment and locally to add in icon support in the header
• version 5.5 is out now, so this is to see if it's worth switching over

Since it's a PDF and not an image, use the code from:
https://stackoverflow.com/questions/39777166/display-pdf-image-in-markdown

<object data="http://yoursite.com/the.pdf" type="application/pdf" width="700px" height="700px">
    <embed src="http://yoursite.com/the.pdf">
        This browser does not support PDFs. Please download the PDF to view it: <a href="http://yoursite.com/the.pdf">Download PDF</a>.</p>
    </embed>
</object>

• Add in good serif font in general
• Make \workplace use a block lettering, and possibly remove bolding
• Make section headers a particular colour that's non-blue (green or red?)

Current tree seems to be:

├── Education
│   └── New York University
├── Skills
│       ├── Programming
│       └── Languages
├── Activities
├── Experience
└── Projects (optional, commented out for space)

Tree should be:

├── Education
│   └── New York University
├── Skills
│       ├── Programming
│       └── Languages
├── Activities
├── Experience
│       ├── MediaMath
│       │    ├── Software Engineer II
│       │    └── Software Engineer I
│       ├── Ivy Tech Capital
│       │   └── Software Engineer Intern
│       └── Phi Kappa Sigma, Delta Phi Chapter
│             └── Technology Chair
└── Projects (optional, commented out for space)

Right now the resume's pretty much "hard coded", with content intermixed with presentation in the .tex file.

This is to look into separating out content from presentation, and such as by using JSON-LD as the content form, and a JSON-LD -> pdf converter for generating the PDFs.

This also enables generating a JSON-LD "about me" format, which could then be used to generate a .html that's automatically served by github pages as a mechanism for showing structured data about me in search engines

Background

• When displaying the resume over at jasonyao.com/resume, the img value there is just the raw .png file that's ~2 MB.
• Since this is the web, there are two requirements:
  • Convert this to generate multiple .jpgs at different resolutions so they can all be included in a srcset
  • Retain the original high quality .png as the fallback source for any browsers that don't support srcset

Next to the company names

Use an osiria token with:

• LINKEDIN_READ_BIO
• LINKEDIN_WRITE_BIO

permissions

Previous version used manual line breaks, let's make this happen automatically so we don't need to think about this issue when dealing with arbitrary text since we're now automating this. The \parbox directive might become useful here.

• Add in travis build badge
• Reformat README following standard README
  • Add in installation instructions
  • Add in commandline generation instructions

• for the ci/cd, i think it's just an issue with the deploy script where I need to update the personal token variable name
• for the watermark, it just sounds like a fun idea

When updating this, take the time to also add in the date of employment as well, since it's nice to know exact start dates

Either use a makefile to generate, or some other build tool. Look up build tool for latex

• literally just font-awesome 4, and get rid of the installation of the extra fonts (172MB) dep currently

• by location, one that includes address (for local), one that doesn't (for outside the state)

Currently images are in the /docs folder, but we'll wanna remove those since they're not actually generated artifacts

Since this resume's autogenerated every once in a while thanks to travis's CI/CD cron-style, we can change the resume to dynamically show how long I've been at the company (x months)

Latex documents require 3+ passes to have guaranteed correct references.

http://www.andy-roberts.net/writing/latex/bibliographies

Looks like they've increased the limit since the last time I checked