Not really but im working with someone in order to standardize the excel sheet
Getting either UIDs or a standard format into place will make this infinitely easier. At that point you could just find the intersection between the two lists and job done. More up front work, but it sounds like you're well underway.
So long story short i dont have a dev job but because i work for a startup i have alot of autonomy I can write/build script to automate anything I do another guy is already doing this on my team. the application my company has built is built on ruby and i just got access to their github I have experience from using github and programming from university but never in a commercial setting like this. For you guys working in a commercial setting what is the best way i can utilize this access except for the obvious just reading through the codebase trying to figure out what is going on is there anything i should keep an eye out for?
Think my long term is to stay at this job until late Q1 2021 by this time i should have at least 1 year of somewhat commercial programming experience with my bachelors being management information system I will at least be able to finesse myself into a more senior dev/sales engineer/solutions engineer/solutions architect role
Our internal contribution process is create a Jira Ticket, create a development branch, make your changes to the development branch, open a pull request to get your changes merged into the master branch. Even though version control mitigates the risk of fukking up the entire codebase, you should never commit directly to master unless you're 105% sure you know what you're doing and what the outcome will be. In fact, our repositories are set up so that direct pushes to master are forbidden. When in doubt, "git status".
The best way to learn your application and codebase is to extend functionality. My application is relatively modular, so I began by extending one of the modules in a "Hello World" type of fashion. After working through those roadblocks, I decided to make one from scratch to help out with a side task I was working on. Went through my trials and tribulations with that, and ultimately that work went nowhere, but the knowledge helped with some later modules I put together. Those modules are actually out in the wild in an open source project as we speak
. Right now I'm in the middle of a big experimental refactor that will make one of the modules more usable by other developers. I'm using it as an opportunity to learn some more OOP and Java concepts. Polymorphism, singletons, abstract factories, reflection. Yesterday I was able to put together a system that dynamically instantiates a specific subclass based on user configuration. So they can set up the module to use functionality from Class ABC, or Class XYZ, or even write their own Class 123. As long as they follow the structure I'm putting together, all exchanges should be seamless.
But maybe even before trying to jump into code, get an understanding on how the application is built, packaged, deployed, and run. For me it was understanding Maven and POMs. How to include dependencies and manipulate plugins, dealing with versioning, understanding parent/child hierarchies, resolving build failures that weren't necessarily code related. After all, can't develop if the application doesn't build. Then came extending functionality, then understanding how to get my module installed into the application.
