Software Development Experience

Open-Source Contributor

Jun 2021 – Oct 2021 (and a couple of commits in Nov 2022)

Description: Gamify your productivity tools and unlock multiplayer for personal development.

Links: Web App Product Hunt GitHub

Technologies: ReactJS, NextJS, JavaScript, PostgreSQL, Supabase, TailwindCSS, HTML, CSS

• Developed the inner workings of the Dailies (Daily Habits) feature and played an active part in designing how daillies should be represented in the Supabase backend, which used PostgreSQL
• Created the initial version of the Edit Daillies feature using an Ant Design table, which showed the user’s list of habits (offered local CRUD functionality)
• Often referenced the 3 normal forms when we were discussing database design; Provided development guidance for the above two features
• Contributed to the development of the Parties feature
  

Dec 2020 – Mar 2021

Description: A software development training program that prepares you for a career in software development, in addition to having you interview with their client companies (ex. Infosys).

Software Engineer (Feb 2021 – Mar 2021)

• Prepared for client interviews, i.e. Infosys

Associate Software Engineer (Dec 2020 – Feb 2021)

Project 3 – RVTR Campsite (Feb 2021 – Feb 2021)

Technologies: C#, ASP.NET Web API, MongoDB, ADO.NET Entity Framework, Angular, JavaScript, Testing, DevOps, Docker, HTML5, CSS3, SQL, BDD, TDD, Microsoft Azure, .NET, Continuous Integration, Microservices, TypeScript, Jasmine, Karma, REST, Kubernetes

• Served as the team leader for one of the four teams; Participated in the daily team lead/scrum, standup, and code review meetings.
• Added features to the Account API, in addition to refactoring code.
• Supported my team in making enhancements to the Angular web application.
• Reviewed pull requests; Informed the team-wide lead know which pull requests from my team were ready so that they could be reviewed and merged into the upstream repository

Project 2 – Revature Dev Tribune (Jan 2021 – Feb 2021)

Links: GitHub

Technologies: C#, ASP.NET Web API, SQL Server, ADO.NET Entity Framework, HTML, JavaScript, CSS, Microsoft Azure, ASP.NET MVC, YAML, GitHub Actions, Docker, Docker Hub, Okta, xUnit

• Served as one of the two leads for this 3-person team; Provided the vision for the project; Created wireframes.
• Played an active role in defining the different properties for all of our domain classes and how the multiplicity relationships should be represented in our SQL Server.
• Corrected the service-side endpoints that dealt with article creation, editing, and deletion.
• Implemented the MVC functionality that allows (1) authors to view all articles and create, edit, and delete articles (2) readers to filter articles by topic.
• Used bootstrap to style all of the pages that I worked on; Made it so that the general layout styling would be dependent on whether the user is an author, reader, or guest.
• Corrected the YAML script so that it would deploy our MVC and API docker images to separate Azure web app services; Supported other DevOp efforts.
• Supported efforts to set up security using Okta.

Lead Software Developer

Jan 2016 – Jun 2016

Description: A proof of concept Android application that would allow users to monitor business operations, like fleet performance.

Technologies: Android, Java, Spring, REST, MPAndroidChart

Part 1 – Focus: Usability Design & Implementation Design (Winter Quarter)

• Actively participated in architectural discussions that led to the use of the Model-View-View Model architecture for eased view and application logic testing
• Constructed sequence, class, and activity diagrams for the planned application flow and proposed features
• Served as the main liaison to the System Architect at Thales who advised us on our implementation design and briefed us on how we should make requests to Thales’ cloud architecture. (This approach was ultimately scrapped for a mocked RESTful backend using Spring.)
• Played an active role in our bi-weekly sprint report presentations to our client and class over the course of both quarters

Part 2 – Focus: Implementation (Spring Quarter)

• Delegated development tasks and directed integration efforts during sprints
• Laid the foundations for the class that made login and coverage data requests to our mocked RESTful backend
• Implemented login functionality and used Android’s AccountManager class for on-device account creation and token authentication
• Played a vital role in the discussion that finalized the data visualizations on the Operations dashboard
• Completed the Operations dashboard, which, using mocked coverage data from the backend, displayed five line charts that identified how many airplane data payloads were lost each day for each coverage area and allowed users to select a data point to see detailed information for the specified day (Graphing Library Used – MPAndroidChart)
• Fine-tuned and populated the Operation dashboard’s detail page, which listed all of the airplanes that lost a payload on the chosen day
• Refactored code for clarity and wrote documentation

Software Developer

Apr 2016 – Jun 2016

Description: A web-based administration system that would allow doctors and trainers to track the exercise data of their Leukemia patients.

Technologies: Spring, MongoDB, AngularJS, HTML, CSS

• Participated in architectural discussions that determined what technologies would be used for the backend and front-end
• Played an active role in backend development discussions and supported backend development efforts that were being spearheaded by another team member:
  • Made the REST controllers make use of the service layer classes, which interacted with the MongoDB database
  • Constructed the model classes and added missing operations to the service layer classes
• Provided direction for development efforts that led to the creation of a message queue based on the client’s requirements
• Developed a python script that was used to remotely update the Spring-based server on the client’s physical server, which I previously set up
• Wrote documentation that described our architecture and why specific technologies were chosen