Vishnuparammal

Joined 8 March 2020
No edit summary
Line 35: Line 35:
* '''Java:''' Part of the college curriculum. Intermediate experience.
* '''Java:''' Part of the college curriculum. Intermediate experience.
**'''Trace_It:''' A software capable of plotting graph of any polynomial. Cross-platform implementation for Windows, Linux and Android. Used JavaFX for GUI.[https://github.com/Vishnuparammal/Trace_it]
**'''Trace_It:''' A software capable of plotting graph of any polynomial. Cross-platform implementation for Windows, Linux and Android. Used JavaFX for GUI.[https://github.com/Vishnuparammal/Trace_it]
* '''PostgreSQL:''' I have experience using PostgreSQL for database management.
* My best experience being in a development team was for my Java project, Trace_It. Earlier, I liked to 'code' my projects single-handedly (thinking it was better-off alone), but then working with a team gave me some new insights. I understood the importance of why and how tasks should be defined and divided among the team. I also got the gist of time and resource management and the inevitably important role they play in a team project. I learnt to use git with collaboration. We faced many merge conflicts. Even had to delete the repository and start over. There were suggestion, revisions, conflict of ideas, differences in coding style, but we worked through it all. I learnt many skills like coordination, communication, feedback, trust, focus and a sense of respect for opinions different than mine. After weeks of early-morning and late-night efforts, we completed the project. The feeling itself was rewarding for me.
* My best experience being in a development team was for my Java project, Trace_It. Earlier, I liked to 'code' my projects single-handedly (thinking it was better-off alone), but then working with a team gave me some new insights. I understood the importance of why and how tasks should be defined and divided among the team. I also got the gist of time and resource management and the inevitably important role they play in a team project. I learnt to use git with collaboration. We faced many merge conflicts. Even had to delete the repository and start over. There were suggestion, revisions, conflict of ideas, differences in coding style, but we worked through it all. I learnt many skills like coordination, communication, feedback, trust, focus and a sense of respect for opinions different than mine. After weeks of early-morning and late-night efforts, we completed the project. The feeling itself was rewarding for me.
*The biggest project I have done so far is the JavaScript-based Simulighter. It is a simple ray optics simulation software. I started it as a small project which was easy to code and maintain. But as more features got added, it became difficult to track code flow, debug errors, and understanding parts of code later on. The need for code organization and documentation dawned upon me. I had to refactor the code from scratch. I split up the HTML, CSS and JavaScript files, created functions, used classes and made a hierarchical folder structure, documented them, adopted the official coding style and made sure anybody who works on the code abides by them. Having worked on such a complex project has taught me that taking small corrective measures is important, or else it will be very difficult to manage later on. My role in the project:
*The biggest project I have done so far is the JavaScript-based Simulighter. It is a simple ray optics simulation software. I started it as a small project which was easy to code and maintain. But as more features got added, it became difficult to track code flow, debug errors, and understanding parts of code later on. The need for code organization and documentation dawned upon me. I had to refactor the code from scratch. I split up the HTML, CSS and JavaScript files, created functions, used classes and made a hierarchical folder structure, documented them, adopted the official coding style and made sure anybody who works on the code abides by them. Having worked on such a complex project has taught me that taking small corrective measures is important, or else it will be very difficult to manage later on. My role in the project:
Line 43: Line 42:
** Mathematical modelling and algorithm development for reflection
** Mathematical modelling and algorithm development for reflection
* Bugs
* Bugs
** Working on octave bug (#57774)[https://savannah.gnu.org/bugs/?57774].
Submitted patches for Octave bug ( #57774 ). Now working on improving efficiency.[https://savannah.gnu.org/bugs/?57774]
** Working on pythonic bug "Warnings when installing pythonic on Win-7"[https://gitlab.com/mtmiller/octave-pythonic/-/issues/65]
** Submitted patch on Pythonic issue #44[https://gitlab.com/mtmiller/octave-pythonic/-/issues/44]
** Reported bug (#58071)[https://savannah.gnu.org/bugs/?58071]
** Working on Pythonic issue #65[https://gitlab.com/mtmiller/octave-pythonic/-/issues/65]
** Reported Octave bug ( #58071 )[https://savannah.gnu.org/bugs/?58071]
** Reported Pythonic issue #71[https://gitlab.com/mtmiller/octave-pythonic/-/issues/71]
** Reported Pythonic issue #72[https://gitlab.com/mtmiller/octave-pythonic/-/issues/72]
** Reported Pythonic issue #73[https://gitlab.com/mtmiller/octave-pythonic/-/issues/73]
** Reported Pythonic issue #74[https://gitlab.com/mtmiller/octave-pythonic/-/issues/74]
** Reported Pythonic issue #75[https://gitlab.com/mtmiller/octave-pythonic/-/issues/75]
** Reported Pythonic issue #76[https://gitlab.com/mtmiller/octave-pythonic/-/issues/76]


== F: Feeling fine ==
== F: Feeling fine ==