Personal Portfolio

All aspiring developers need a good portfolio, it's how we communicate our skills and share our experiences.

Comment

Inspiration

This portfolio site was built based off of the template provided and is intended to serve as a portfolio for our group members. As aspiring Software Engineers, a portfolio will allow us to share our experiences, projects, and thoughts in an organized manner.

What it does

Our website displays basic information about us, some of the projects we have worked on, and serves as a blog which will contain posts in the future.

How we built it

This project was built using python and flask in the backend and HTML/CSS for the frontend. Our team of three communicated on Discord and collaborated through GitHub over the last week to build this website.

Challenges we ran into

One of our biggest challenges was the differences in time zones between our team members which made scheduling meetings a bit tricky. Earlier in our development, we encountered a slight learning curve since none of us had previously used python with flask, but we made great progress over the week and ultimately finished this project.

Accomplishments that we're proud of

We are proud of having learned Flask well-enough in a week’s time to complete a project. We are also proud of how well we communicated as a team because without it, we would have struggled to coordinate our work due to the different time zones. Another point of pride is with how well we handled working on GitHub collaboratively, such as assigning issues; creating and merging branches; handling merge conflicts; etc., considering we were relatively green on the topic.

What we learned

We learned how to use Python with Flask and how to use Git and GitHub in a collaborative project. We also learned how to coordinate work with people in different time zones or with other pressing commitments, which are possible situations that we may find ourselves in during our careers.

What's next for Personal Portfolio

We will fork our own version of the repo, possibly deploy. Individually, we will each build out the blog section and make posts on that. Beyond that, it really just depends on the situation.

Share this project:

Updates