hreynier / job-board

Full-stack (React, Express, Material UI, CronJob, Redis) App that collects, filters and displays entry-level software jobs from various job-board APIs.

Hi 👋

I'm Harvey Reynier, a product-minded software engineer 🚀 currently based in London. I enjoy building consumer products that bring real value to end users. Currently, I'm helping to build Lottielab to democratize motion design for everyone. I've previously worked at Snap, where I was part of the team that built Snapchat on the Web!
In my spare time, I try to build a few mini-projects a year, usually to learn new technologies or tools, please check them out below 🙋‍♂.
Besides programming, I love travelling 🗺️, coffee ☕, music 🎧, and Formula 1 🏎️!

My inbox is always open, so feel free to hmu 👍

job-board's Issues

🐛 Duplicate Job Postings from the GitHub Jobs API

Seems to be duplicate job posting arising from the GitHub Jobs API.

To-Do

• Check the flow of data to see when the duplication occurs.
• Fix the error.

API called twice unnecessarily.

job-board/client/src/App.js

Line 39 in 40019e7

fetchJobs(updateFiltered);

On line 39, API is called and assigned to state on the filtered list, however, the filtered list pulls its state from the original list already.

Company Logo's are too big in modal.

Bug Description:

Company logos that are displayed in the pop-up job modals are sometimes too large and overlap the title and other text.
This is due to the varying sizes of the supplied company logos.

To Do:

• Reduce global sizing of company logos to reflect the larger than anticipated size of certain company logos.

Missing Company Logos

Description:

Some jobs that are pulled from the API have no company logo. This results in the job modal displaying a missing image and sometimes JSX code.

To-Do:

• Implement a check to determine whether the job has a valid company logo before rendering in the modal to prevent missing images.

Add Read-Me documentation to project.

Description:

Add extensive Read-Me documentation to the project that describes the project in its entirety. The documentation should explain the tools and technologies that were used to develop and deploy the application. Furthermore, it should show images of the current project and outline the goals of the project moving forward. Finally, the documentation should provide instructions on how to fork and start development on this project for other people.