Goal

We're four friends that would stay over and hold overnight neetcode.io / redstone sessions as we're passionate backend developers. However, we decided to change our routine a little bit by participating in a hackathon. With only Bart being experienced in doing hackathons and building full-stack Web Apps, we had to learn how to build a web application and how to use Django all in one night. So, our goal going into this hackathon is to implement our web app using at least one new tech stack and technologies that each of us has never used before. So, for all of us, Django and SQLite were completely novel tech stacks that none of us has ever touched before, and we've never really touched google maps api before (except for static streetview api, which was not used in this project). In addition to this, none of us really knew how to do UI / UX... which was a VERY difficult hurdle to overcome as backend developers. We ended up walking away learning a lot, especially about collaborating in a team.

Roles

Patrick: Backend Developer Jason: Backend Developer Bart: UI / UX and Full-Stack Developer Millan: Project Manager

Inspiration

Road trips are stressful, expensive, and long. They take precious time in exchange for the views along the way, however, we at J.A.Z.A hope to make the process of planning more enjoyable and elevate the experience for our users. In addition, we hope that our product will incentivize companies and people to work together to lower carbon emissions as both benefit from our setup.

What it does

J.A.Z.A creates an environment in which companies can offer job-listings which users can take to make a quick buck while still enjoying all the benefits of a road trip. In addition, we offer the both the users and the companies this ability to post, this is so that they can either offer others to carpool for more cash, or take along company merchandise for the same. Best case scenario they do both! Now we take a theoretical situation where there would be 12 cars and 1 truck on the road, and using J.A.Z.A we can make a case to remove the truck, and even some cars without changing the end result.

How we built it

The front end was built using REACT The back end was built using Django, RestAPI, and SQLite

Challenges we ran into

The back end developers have never used Django and thus spent the majority of the time on the login page before learning how to implement everything else. This happened because we followed an online tutorial which upon reaching part 4 they learned it focused on the front end, so they decided, due to the sunk-cost fallacy, to finish it through anyways. In addition, the backend developers did not, funnily enough, know how to use RestAPI and only had a basic understanding of SQLite. So this proved to be a fun roadblock while attempt to wrestle with this and the constant red, sometimes purple or yellow, showing up the logs for the website while Django did not work. The front end developer struggled with making persisting sessions, which prove to be a very difficult task that got in the way of testing until it was fixed.

Accomplishments that we're proud of

Completing the implementation that we did, as we did not know what we were doing and still only somewhat do. Thus we are proud of the amount of work we did and how the product came out.

What we learned

Make sure your tutorial is for the right section of your code. We also learned along about Sequalizers and JSON file formatting Working with Django and SQLite, learning RestAPI A lot of UI/UX portions Working with/creating persisting session ids Login storage and creating permission via Django

Built With

• django
• react
• restapi
• sqlite