Posts
These are some of my thoughts as I have worked with TARDIS.
My First Solo Project
My first solo project was in documentation. I had been working on fixing up documentation errors that were present on GitHub issues, when I got ready to tackle two large issues: the creation of documentation and coding guidelines for TARDIS. This was a large step up in importance, as I would be setting guidelines for how all code past and future should be written. It would also make it so that documentation issues like the ones I had been working on for the past month wouldn’t be repeated.
Working With Documentation
As a result of my somewhat slow results and my basic knowledge of Python at the time, I was put onto the documentation for TARDIS. TARDIS documentation is very cohesive, but there were issues mostly regarding formatting and the style of documentation, specifically with regards to docstrings. There was old syntax present that would mess with the TARDIS documentation pages, so I read through all of the modules going around fixing the docstrings.
First Interactions with TARDIS
My first introduction to TARDIS was due to my involvement in the Professorial Assistantship program at MSU, which allowed me as a freshman to start doing research. I was placed with TARDIS due to my interest in understanding how the world works and my enjoyment of math. After I had finished my crash course of Python 2 (TARDIS is written in Python 3, but Python 2 was free) through CodeAcademy, I was given my first task.
First Experience with Coding
Python was the first coding language I ever learned. I started learning it in the Fall of 2020 in my Introduction to Computer Programming class. I learned Python 3.0, and used Spyder to work with Python. Spyder had an Editor, Debugger, Variable Explorer, and Shell all in one. It was a very contained experience which made it easy for me. I found the Shell fun because I could test out code by writing it directly into the shell to see the results instead of having to write a program and then run it.