Hi @crfries
. Your portfolio site looks great, good job.
As some other people have mentioned, recruiters probably aren't going to be paying attention to your code, so changing that will only get you so far.
That said, if I was reviewing your portfolio site code, I think the main thing I'd suggest to work on is refactoring your components out into their own files within a src/components directory. Your App.js file is pretty long and there are a few components in there which you could be importing instead.
A good skill to demonstrate in React is being able to identify which parts of your UI/code could be extracted into their own components.
The next thing I would do is add some unit tests, even just a few to demonstrate that you have some knowledge. I'd recommend using jest with react-testing-library, as these are very popular.
Don't spend too long on these things though; it's probably more helpful to get more applications out there. Most employers will give you a tech test to do anyway and might not look at your site's code.
I can't give expert advice on what recruiters are looking for when they read your resume, but it would be best to assume that they are reading through stacks of resumes and probably only skim reading. So keep it simple and to the point: say what you're good at, what you're offering, give links to projects, tell them solid examples of things you've done in your career (even if it's just transferrable skills from non-dev jobs).
Hi @crfries . Your portfolio site looks great, good job.
As some other people have mentioned, recruiters probably aren't going to be paying attention to your code, so changing that will only get you so far.
That said, if I was reviewing your portfolio site code, I think the main thing I'd suggest to work on is refactoring your components out into their own files within a
src/componentsdirectory. Your App.js file is pretty long and there are a few components in there which you could be importing instead.A good skill to demonstrate in React is being able to identify which parts of your UI/code could be extracted into their own components.
The next thing I would do is add some unit tests, even just a few to demonstrate that you have some knowledge. I'd recommend using
jestwithreact-testing-library, as these are very popular.Don't spend too long on these things though; it's probably more helpful to get more applications out there. Most employers will give you a tech test to do anyway and might not look at your site's code.
I can't give expert advice on what recruiters are looking for when they read your resume, but it would be best to assume that they are reading through stacks of resumes and probably only skim reading. So keep it simple and to the point: say what you're good at, what you're offering, give links to projects, tell them solid examples of things you've done in your career (even if it's just transferrable skills from non-dev jobs).
Best of luck!
advice taken. thank you