Originally, I was going to use the National Parks Service api, found here: [https://www.nps.gov/subjects/developer/api-documentation.htm](https://www.nps.gov/subjects/developer/api-documentation.htm) After playing around with examples and documentation, I found it difficult to find other information on parks besides just the Acadia Park. This might have been user error, but after trying to get information on other parks, I decided to opt for another API that was easier to work with. I chose the Weather API ([https://www.weatherapi.com/](https://www.weatherapi.com/)) for my main project. I aimed at creating a current weather checker, similar to how a weather app would work, showing standard visuals on the canvas. You can choose a specific city or town and the sketch will return the type of weather. What I've Learned I think this semester has really given me the time to reflect on how I approach projects in general. Early in this quarter, we had to write a design manifesto in Design for This Century; I focus on design as a way of change. Design is used to make change in the world, because "when we design something, we want something to be different", best said by Julie Zhou, former Product Design VP at Facebook. We want behaviors, thoughts, or feelings, etc to be different. In my Design Manifesto, I mention that, because design is change, I should use my skill in design to change how we think about relationships, communities, etc. After going through my first semester in DT, I've learned that design can be other things too. It can be something just for myself. Because I was in the mindset that design should solve important issues, I was a barrier for myself, in that I couldn't use design to just play and explore new things without a complete product. This comes into play when I think about some of the projects I've attempted to do vs. the final project I submitted. I've tried to start every project with the intention that it would be something that sparked change in the world. And with the topics we were navigating in class, I was particularly inspired. I don't think I allowed myself to just play and explore this semester, especially things that are completely new to me, like coding. For this project, I originally wanted to build a national park information page. I wanted to lean into my UX skills and marry them with coding. Sometimes, my design brain is very ambitious and my coding brain just isn't there yet. I need to allow myself the time to just play around with coding to feel truly comfortable with it. I'm actually not quite sure how this project ties in with feminist data principles. At first, I thought it was transparency of information. That makes total sense, until I quickly realized there's still lots of data points that aren't shown to the user. So at the same time, it's hiding information. Currently, my code only shows if it's raining, snowing, sunny, etc. It doesn't show variations of those things, and therefore is a bit limiting. For example, it might be 35 degrees out, but because it's so windy if feels like 25. That nuance is important to someone using a weather application because they may be using it to determine what to wear, where to go, etc.