Pivoting and GitHub managing.

 Our team's previous week was the "slowest" it has been since our formation last month. Slow isn't a bad reasoning compound in this case. Slow in the sense of carefulness. We are in a phase of getting our application to its MVP phase. We know that it is important that we have this be up to a high-quality standard and we are taking our time to put everything together in manner that is professional and understandable for beginners and project experts.

This previous week was the first time I needed to pivot to another task. I am tasked with completing an adoption form for our app. The button must be available on every adoptable pet profile page, as a clickable button. This button needs to use some of the Pet finder API information and get a list for that pet and take whatever entry and make the button displayed to the user. The user can now click the button and be taken to an adoption form and submit the form to our backend servers. Once the application is submitted then we redirect the user to the start page and tell them their application has been submitted.

All of this is doable, but I need to have some things happen before i can move on to complete all of the above steps in code.

•  I need the backend to have the servers set up and allow the information to be housed there and sent to the application forms stakeholder.
• I need the API's that generate pet profiles to be live so that I can reference my code to the corresponding segments within our main application code and create the buttons from there.
• I need the submit buttons call to action linked to the user homepage and this would have to be after a user has signed in.

So, I had to figure something out in the meantime of my waiting, and I went to the Trello board to see what I could do. As I talked to team members, it was clear that all the rest of the tasks were tied up from the previous points I mentioned earlier. This was at the very end of the week, and it was okay for me this time because I still had to get a final rough draft for our readme in order. So, I pivoted to completing our teams ReadMe.md documentation. This previous week's experience lends a lesson in communication. I need to work more closely with my team and prep any little thing, so I can have something ready for when i need to pivot. I have found code samples here and there and read the guides. I am familiar with what i would need to do to get these things we need to be working.

As for the Readme.md, I got familiar with how using markdown works. I learned how to make buttons and links that are very useful to visitors of our repository. It was tedious at first but as with all things, practicing makes things easier. I ran through the application and cleaned up errors and am proud of my first final rough draft. I am using it for a screenshot in this post because it looks good and I wanted to show it off!