Lambda Labs Logs: Week 5

February 21, 2019
|
Tech

Part 1 - Individual Accomplishments this Week

Team Contribution Graph: https://github.com/Lambda-School-Labs/labs9-developer-profiles/graphs/contributors

Github Handle: mkerbleski

Front-End URL: https://ecstatic-dev-profiles.netlify.com/

Back_End URL: https://developer-profiles.herokuapp.com/

Summary:

Bugs, Bugs, and Bugs. This week was all about bugs. We made a ton of progress this week as a team and really made a good looking site. I was surprised at how much work we needed to put in this week to get everything running smooth. There were a lot of small tasks that turned into bigger tasks and small tasks (like adding an edit feature) that turned out not to be so big.

Tasks Pulled

Front end: 12

Back end: 1

Total: 13

Monday

Tuesday

Wednesday

Thursday

Detailed Analysis

The last week was all about finding bugs and fixing them. Most of what we were doing this last week has been centered around styling. Styling to me is the most tedious aspect of an application and I would rather do the filter function all over again then mess with that, so this week wasn't my favorite. What was my favorite tho was getting the edit and delete functions set up and working on Thursday and fun challenge to do on the last minute. Another thing that I enjoyed is the fun last minute pressure of everyone working together, I don't know why I like it but it is always fun to see everyone working and the product coming together. I think it looks quite polished.

A few bugs/styling problems I encountered this week: 

Getting the auto-fill formatted was a challenge but I think it turned out pretty nice. The only thing that bugs me was that the user entered content is not in the original text box, but it looks consistent throughout the site and way better than before.

I fought for hours to get this extra dash in the menu to dissappear, it didn't even show up as being rendered and it is still a mystery why it was there. Liz ended up just creating an X in another area and ditching the hamburger menu all together.

This week I also learned that you can't make http requests from an https site without compromising security. Overall this as been an enjoyable project and I am glad to see it in its final form!

Part 2 - Milestone Reflections

Description and Tech Stack Justification:

Dev Profiles is a  website that allows recruiters to connect with developers currently seeking a position.

It doesn’t cost anything to view prospective candidates. Recruiters can easily browse through the pool of developers by location and skills.

This is a great place to find a candidate quickly, instead of sorting through thousands of job applications you can easily reach out to a qualified developer. Recruiters can also filter developers by their current location, willingness to relocate or work remotely.

For this reason there is no need to create an account or login if you are looking to hire a developer.

For developers, this is a great place to be seen by recruiters who are focused on hiring. This is why only paid and completed accounts will be shown. By ensuring only serious candidates with complete profiles are on the site, recruiters will know that their time will be used efficiently.

The user dashboard is where developers can make changes to their profile card that is seen by the public. Here you can do everything from upload your photo,  verify acclaim badges and tell recruiters a little bit about yourself.

On the technical side of things, we used React for the use of lifecycle methods and the breadth of tools that work with it. We decided to use node.js to keep a similar ecosystem between front-end and back-end development.

For the database we are using a postgreSQL relational database that is hosted on heroku. We used a library called knex to make our database queries using javascript and facilitate the seeding and migrating of users in development.

For styling we used a library called Grommet for consistency throughout the website, integration with styled components and a polished look throughout.

To sort the users by location we used a google maps api to provide both an auto complete of possible cities and to return a coordinate associated with the city. From there we we store the coordinate on the users profile. When a search is requested for someone that is located with a certain mile range we calculate mileage based off the coordinates, and return the relevant results.

To deploy we are using a heroku postgress instance for the backend and netlify to deploy our frontend. We have continuous integration so all modifications are released immediately.

‍