WTF resume (Who cares who you are)

#react #javascript #typescript #frontend

"Who cares who you are? you should prove yourself"

wtfresume

Some months ago when I decided to find a new job I tried to update my resume, I searched in google for how to build my resume, I register many sites but almost all of them need money for export PDF.
Then I decided to create my resume with myself.
first I created simple HTML and export PDF with Chrome then I thought many people are the same me and they need to update their resume. that is the story of why I created this resume builder.

First I created with create-react-app then I changed my codes to next js. why? because I wanted to experience it. The question I faced from many companies: did you have any experience with Typescript? then I started to refactor my codes from Javascript to Typescript (currently I refactor 60% of the codes).
This is my Github repository you can look at the codes:
wtfresume Github repo

I will be happy if You use wtfresume or look at the codes and contribute.
Also if you like that please give me a star.

Get n8n VPS hosting 3x cheaper than a cloud solution

Get fast, easy, secure n8n VPS hosting from $4.99/mo at Hostinger. Automate any workflow using a pre-installed n8n application and no-code customization.

Start now

Top comments (0)

5 Playwright CLI Flags That Will Transform Your Testing Workflow

0:56 --last-failed: Zero in on just the tests that failed in your previous run

2:34 --only-changed: Test only the spec files you've modified in git

4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production

5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline

5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

0:56 --last-failed: Zero in on just the tests that failed in your previous run
2:34 --only-changed: Test only the spec files you've modified in git
4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Watch Full Video 📹️

DEV Community

WTF resume (Who cares who you are)

Get n8n VPS hosting 3x cheaper than a cloud solution

Top comments (0)

5 Playwright CLI Flags That Will Transform Your Testing Workflow

Okay