Week 3 - Getting Technical

        As we move into week three, I have begun to shift into more technical work, utilizing my software engineering skills. After gathering requirements, creating a lo-fi prototype, and refining based on feedback from my mentor, I was tasked with creating a high-level web portal to display data from an IoT device. I had the freedom to choose my own stack, so after weighing different options, I settled on something that will hopefully allow for scalability in the future, also by including documentation that will guide others through my codebase. 

    I set up a CI/CD pipeline early on to ensure no roadblocks for frontend deployment while also ensuring compatibility with the backend integration. While I have the main components set up, the more I started to delve into details about routes and specific pages, I recognized I needed to reconvene with my mentor to get an idea of how high-level we want to be, while also aligning with future integration. This entire experience made me realize how vital requirements gathering, especially the ability to translate business requirements into technical requirements, is. 

One thing I recognized is how easy it can be to misunderstand what is intended for a product, especially when considering how people might define or categorize specific terms. Being able to decrease cognitive friction for new users who might migrate to our platform means that terminology becomes crucial, based on what we define as such from the outset. 

Comments

Post a Comment

Popular posts from this blog

Week 9 - Last week thoughts

    It's crazy how quickly the 9 weeks have passed at my internship at the digital summer clinic. I am set to graduate this week, so I am excited to see the friends I've made at the internship, along with my company, attending the graduation. This 9-week internship has helped me learn so much for the future of my career, not only on the technical side but also on the networking side. Being able to communicate your ideas clearly to an audience, network, and delve into new skills has allowed me to progress and learn so much.          With the weekly cohort meetings, we were given advice on how to address challenges we face, actions to take, and how to grow our network. We were advised to update our LinkedIn, blog about our experiences, and reach out to our network. The experience taught me a lot about the importance of reaching out to people, whether it was a simple message or a coffee chat...
Read more

Week 7 - Demo

    This week's primary focus has been on preparing for a demo to present the work we have done, which is scheduled to take place at Ann Arbor Spark. The event is called "The Waymo Journey: From Moonshot to Your Next Ride." I am very excited to present the work I have done over the past 7 weeks. From deploying a functioning web portal to designing a database, it's been a journey learning new technology. I hope that through the event, I will be able to show the progress I have made. We also all plan to wear matching Roadsr shirts, so I will definitely be posting a picture next week of the demo :)          As for the work that I have been doing, I mentioned refactoring the code I have been working on to ensure I have been following all best practices to ensure future scalability. This week, I have added a couple of more features, primarily focused on user accounts and the set...
Read more

Week 8 - Admin Portal

Image
    As promised, pictures from demo day! I had an amazing experience talking to a bunch of different people from different backgrounds. I was able to connect on LinkedIn as well, so the overall experience benefited the company along with myself.     This week, I worked on the Admin Portal, which is separate from the Web Portal. The Admin Portal is designed to help manage account creation, as those who use our platform will not be able to sign up on their own. Those at Roadsr will be able to add an account, and from there, a user can then log in with an authorized email. There has been a lot of discussion on how we want to manage this workflow while ensuring that there's not too much control on Roadsr's end. I have been thinking of ways to optimize the workflow while also balancing the power of reads/writes. Especially when considering deletes, it takes a lot of reads, especially data tied to the company.    Because there is a lot of...
Read more