pawaitemadisoncollege
commented
1 year ago Hi @fchristian1992 - Thank you for sharing your self-assessment for each of the Enterprise Java competencies. To demonstrate your final grade as it relates to your self evaluation document https://github.com/fchristian1992/pcHardwareViewer/blob/main/designDocuments/self-eval.md and the scale here:
, can you please update your self-eval document and respond here when it is ready for review (along with the grade that it corresponds to). This might be done by simply copying your statements from your issue above and pasting them into the appropriate column in your eval. Thanks!
fchristian1992
@pawaitemadisoncollege
The way I feel I have grown this semester is in the usage of different tools in the development of a web application (Cognito, Hibernate, RESTful, IntelliJ, SoapUI, etc.), as well as valuable experience in what it's like to work on an application as a team. Even though there was still quite a few things I wasn't able to do in the class (some exercises, feedback for prof dev presentations, implement all the features I wanted to in my indie project as well as clean it up as well as I wanted to), I do think I was able to learn a ton in this class.
Regarding the suggested prompts of discussion, not all of my work has full javadoc documentation, but I do think I've certainly shown I know how to. Security in my application is done through Cognito and I was able to understand it well enough to integrate it into my project. Like I said in my presentation, I at first wanted to just have users sign up with a username and password and add the email part another time, but I didn't realize that even though email wasn't required, confirming the account still is, so that's definitely not ideal.
Regarding logging, I did use log4j in my project, in the exception handling and to log values of different variables, but it did not help me in the development process. It might have been because I didn't configure it properly because it would create an output file, but nothing would be in it and when I did get it to output something, it was so much information that I couldn't use it at all, so I used System.out.println() instead.
In terms of producing and consuming web services, I was able to produce an errorless web application, but not consume one in my indie project due to time constraints. I did, however, help work on an application that consumed a web service in the team project, which I understood fairly well.
I did write unit tests for almost all my DAO methods, aside from one because I added it later in development. It certainly helped my dev process because it got me to fix an issue that I would have ran into later on.
For Git and Github, I would typically commit when I would either have a checkpoint to make an issue for, I would be getting help with something that my github repository would need to be up to date for, or I would complete a chunk of work. My commit messages would usually be simple summaries of what has been added or changed (ex: "code formatting, added the parts_list jsp and the servlet that goes with it"). I did not need to use branches in my indie project, but the group project required it as we had at least 1 branch per person so we were not all committing to the same thing.
For Hibernate, after MUCH troubleshooting, I have a one-to-many relationship fully implemented in the code, but again, due to time constraints, I was not able to implement the "many" part into the end product. I was able to do so by referring to the lecture videos, demos, and the exercises associated with it as well as asking classmates for help.
When I would do debugging, I did try to use the debug stepping tool, but when I would take one step at a time, it had to go through all these super abstract classes first and crowd up my windows bar on the top of the intellij, so instead I just followed the code manually and was able to solve my problems like that.
When asking for help, I would typically start by stating the error message (stack trace) I got to see if there is any obvious fixes for it, then provide information as needed if there is not (and there usually is not).
In giving feedback, I start small and work my way up. Small meaning code formatting, typos, etc., then maybe if there's some redundant or missing code as well as the organization of it and how easy it is to understand the functions of each part (usually improved by the quality of the javadoc comments).
The grade I think I earned: I'm always a lot more critical of myself than complimenting, so I really can't know or say for sure how well I actually did in terms of what the expectations are of this class. I think I was probably severely average. I know there's quite a few "smaller" things I was not able to do, but I can definitely say that I did learn A LOT, and I'd like to think that because I was able to get through the big 3 assignments (team project, indie project, and prof dev presentation) that I was able to accomplish enough in this class to pass it (I'm aware that simply passing should not be my goal, and it isn't, but I don't think I can ask for much more), but I would understand if you disagree. To answer the question, average is typically thought of as a C, so let's go with that.