latexcv VS Standard

View on GitHub

I generally avoid sending Word documents. IMO scanning PDFs is nowadays good enough to deal with LaTeX-generated PDFs. And when it comes to the templates... Personally I use LaTeX generated. Some time ago I was using LibreOffice but updating it was not pleasant. I wanted to have more fancy CV and store the source in GIT. I have chosen Sidebar Left from this repo: https://github.com/jankapunkt/latexcv and I am generally satisfied, but I also respect the above approach.

And for all resumes in https://github.com/jankapunkt/latexcv , I think they're not appropriate for CS resumes as they're too fancy

IMHO - Look at a different resume style nothing is jumping out at me and it's the style not the person. This is an older style very bland. There are lots of creative styles out there, you want to find what is most valuable about you and make that pop everything else is details. Example - https://github.com/jankapunkt/latexcv - this is just a few examples after a quick Google, I personally refuse to put my picture on there but a resume can show personality use it to your advantage.

Ja ga koristim za fakture, ali imas jako puno primera za CV u LaTeX-u (https://github.com/jankapunkt/latexcv)

I picked up standard[1] a while back for this reason, I don't want to have to think about it. It works fine, I have no complaints (took me a while to get used to not using semi-colons but now I prefer it) Same reason I use `cargo fmt` as well.

[1] https://standardjs.com/

# question 1: ? How would you like to use ESLint? … To check syntax only To check syntax and find problems ❯ To check syntax, find problems, and enforce code style # question 2: ? What type of modules does your project use? … ❯ JavaScript modules (import/export) CommonJS (require/exports) None of these # question 3: ? Which framework does your project use? … ❯ React Vue.js None of these # question 4 (select "No", because we won't add TypeScript support for this project): ? Does your project use TypeScript? › No / Yes # question 5: ? Where does your code run? … Browser ✔ Node # question 6: ? How would you like to define a style for your project? … ❯ Use a popular style guide Answer questions about your style Inspect your JavaScript file(s) # question 7 (we'll rely on Airbnb's JavaScript style guide here): ? Which style guide do you want to follow? … ❯ Airbnb: https://github.com/airbnb/javascript Standard: https://github.com/standard/standard Google: https://github.com/google/eslint-config-google # question 8: ? What format do you want your config file to be in? … JavaScript YAML ❯ JSON # the final prompt here is where eslint will ask you if you want to install all the necessary dependencies. Select "Yes" and hit enter: Checking peerDependencies of eslint-config-airbnb@latest The config that you have selected requires the following dependencies: eslint-plugin-react@^7.21.5 eslint-config-airbnb@latest eslint@^5.16.0 || ^6.8.0 || ^7.2.0 eslint-plugin-import@^2.22.1 eslint-plugin-jsx-a11y@^6.4.1 eslint-plugin-react-hooks@^4 || ^3 || ^2.3.0 || ^1.7.0 ? Would you like to install them now with npm? › No / Yes

A Thin JavaScript Document Storage with Middleware Stack

https://github.com/standard/standard/issues/384

For example, if you use https://standardjs.com/ - it will error on your second code snippet and if you ask it for an autofix - it will transfer the minus sign to the first line.

In comparison, JavaScript doesn't have a strict coding standard, although it does have widely accepted code style guides like the Airbnb JavaScript Style Guide and the JavaScript Standard Style. These guides provide recommendations for code formatting and naming conventions, but they are not as strictly enforced as the Java coding standard.