The implications of my Explore internship to my future career

 My Explore internship experience consisted of two phases; Project Management and Software Development. I spent the first four weeks of my internship working through ideation to prototyping. During this phase, I conducted customer interviews to understand how Microsoft Excel customers faced my project's problem. After completing the interviews, I wrote developed a Figma design with various ideas of the problem solution. 

Then, I compiled a product specification that highlighted the problem statement, user scenarios, prototype designs, and possible success matrices for the project. Although working through the Project Management phase was interesting, I discovered that I am more interested in software development. I enjoyed spending time thinking about how to implement a function or debugging code. It was new exciting challenges daily in the software development phase than in the Project Management phase. 

During the summer of 2020, I had a Front-end internship where I worked with HTML, CSS, and React to develop web applications. Although I enjoyed working on the front-end, I always felt limited by the inability to create a full-stack solution with both front and back-end software development. By working on this summer's internship project, I discovered that I enjoy back-end development and should explore the possibility of full-stack development. 

Moving forward, I plan to learn more about full-stack software development and different ways to improve my software development skills. I also plan to attend more events organized by different companies to learn about the different full-stack development roles and how to best prepare for these roles. 


Comments

Post a Comment

Popular posts from this blog

Software test engineering career

During the last two weeks, I talked to a couple of full-time employees to learn how Microsoft tests its software and a career option as a Software Test Engineer. Test engineers write software tests like unit tests, sub-system tests, scenario tests, and vendor tests. Unit tests are tests written to check how different functions or methods work at the lowest level of abstraction. During a conversation with a former Test engineer, I learned about Test-driven development, where test suites are developed before the actual development of the product. Although test-driven development is highly encouraged, some engineers write tests to verify their product's functionality after the coding. One importance of Test-driven development is fully understanding various edge cases to consider while developing. Sub-system tests are tests written to cover code shared between different components. A specific type of sub-system testing called cross-platform testing verifies how code behaves on other E...
Read more

Learning source Depot

 I remember asking my manager about the technology used in Microsft Excel projects and what skills would support me during my internship experience. I was glad to know that the primary programming language we would use was C++; however, I was surprised that we would use a new version system called source depot, which is different from Git. Source Depot was a completely different source control that I needed to read about before my internship. My primary goals were to learn how to commit, push, pull, and merge changes and the similarities and differences between Git and Source Depot that I can leverage when researching Source depot.  Unlike Git, a distributed system with local and remote repositories, source depot is a centralized version control system with a central repository and client mappings to that repository. Another significant difference is how Git has terminal and graphical user interfaces(GUI) options, but Source depot is accessed through the Command-line option. W...
Read more

Lesson from overcoming a challenge

 I spent most of the week reviewing comments on my code review and preparing for demo presentations of the end-to-end customer experience of our feature. During my last demo presentation, I remembered how overwhelmed I felt during my first week at the internship. Everything from understanding my project description, adjusting to work in Pacific Standard time when physically located in Berea, and trying to understand the meaning of the C++ code in Excel's codebase seemed a lot to understand. By taking one task at a time and reaching out to my mentors and manager whenever I needed help to understand something, I overcame my technical and non-technical challenges. One major challenge I faced during my internship was executing my second project task. My task was to enable customers to navigate to a specific sheet and cell in Microsoft Excel using deep linking. To deep-link to the customer's cell location, I worked with code from the front and back end of SharePoint's server, wh...
Read more