Week 3

Whose code did you review? Cristian Perez

 Review

• Variable names, are they meaningful and clear? 
• Good variable naming conventions, pretty clear and generally easy to follow along. 'str' for String and 'dp' for 'defensePoints' are easy to follow, though I know it might be preferred to fully spell out the variable name for a cleaner read, the variables are pretty straight forward.
•  Logic that could be more efficient 
• Logic is pristine and follows the prompts well, showing a good understanding working with abstract classes! 
• Unused imports or warnings. 
• No unused imports, though in Electric Rat, there are some suggestions 
• Clear formatting o Very clean structure and formatting 
• Are there comments? 
• Not too many traditional // comments but there are javadoc comments above the methods and a few additional helpful comments within the methods 
• Which unit tests pass? 
• All 12 Unit tests pass!

 

Summary

    I didn't get to sit with the LDPM project nearly as long as I had hoped. I accepted, with great difficulty, that it would be an inevitable hard hit, as the past couple weeks were spent trouble shooting and fighting with gradle than I was able to sit with the lecture and material. This was a heavy blow and not one that deserved much celebrating, however, turing what I had, even minimally, was enough of an accomplishment for the time being. Small and miniscule as the win may be, it still states my current position and shows me where I can improve, revisions that need to be made, and highlighted some of my inherent understanding from previous courses. This didn't quite save me, but has allowed me to prevail and face the rest of the course with a much more stubborn approach. 

    Unforunately, the prompts were very challenging for me, as I had barely gotten to review, in full detail, how to work with abstracts and interfaces. I do believe, now that I'm working on Markov, that the assignments are getting easier to follow as I have much more time to sit with the lectures rather than fighting with the IDEs and this is promising for me. I'm not out yet. 

Beginning CST338: Week1 and Week2

  Git Commands

• git status (Shows working branch and changes made at that branch)
• git branch -b [name of branch] (Creates a branch that doesn't already exist)
• git checkout -b [name of branch] (Create a branch using -b or switch branches without -b) 
• git add . (Saves any changes made to that branch)
• git commit -m "with your message" (Commits changes to git with an updated message)
• git push (Pushes the changes to git repository)
• git pull (Pulls the repository)
• git stash (Temporarily stashes changes so they can be moved to the appropriate branch)
• git pop (Opens stash and, after changing to the correct branch, applies changes to that branch)

CodingBat

    Aside from git commands, we did go over some Java code in codingbat, and I must say, I absolutely love it. I definitely see myself on there regularly and plan to spend an hour on it each day, if I can, to help solidify simple coding. It's simple and rewarding, with satisfying checkmarks tracking your progress so you can accumulate stars. 

Lab00 and Lab01

The first couple of labs introduced us to IntelliJ, its features, some Java code, and Git commands that we'll be using regularly throughout the course. Lab 00 was the first introduction to IntelliJ, where we created .java files, branches, and worked on creating a general Rectangle shape that we'd update throughout the next couple of weeks. This led into Lab01, further discussing IntelliJ features from cloning repositories, reapplying changes to the appropriate branch, creating Java classes to include in our main, merging process, and how to update, commit, and push our changes to git. We’re beginning to learn more about OOP in Java, which consists of inheritance, polymorphism, and abstraction, and occurs when you extend an existing class.

Summary

Overall, I started off pretty stressed with all the IntelliJ, Gradle, path, and other system roadblocks that prevented me from fully engaging with the material as much as I would have liked. I've learned to just ask immediately, even if it does seem like an easy fix, as the time crunch really doesn't allow much time for those setbacks. Luckily, in researching and reaching out to the TA, spending DAYS trying to get the IDE to just run normally, I can certainly say I've clicked around IntelliJ enough that it seems to help resolve similar issues I encounter today. Incredibly skittish start, but I feel I'm starting to find my bearings.