Individual Code: Search Button

  • In this search button, it allows users to look up stocks by their stock symbol
  • It then displays the open price of the stock and allows them to be go to an analysis page that displays if the stock is good to buy
  • Link
  • In this I utilize a function that calls the backend after the user hits enter
  • It searches the data base for the information based on the stock symbol, then parses for the open, price to print
  • Then it prints a custom div with id and button that corresponds, this is for when they press the button the program can send proper information through localStorage
  • Then on the analysis page, the API is called again to get the volume of the stock and the price to input in to the prediction model

    GitHub Analytics

  • Commit Graph
  • Overall Commits

Key Commits

  • Getting the Search to print the results and determining the stock based on the custom id’s and button id’s Link
  • Integrating the Search with Analysis Page Link

College Board Test

For the college board test I got a 38/40 and I did this without looking up anything, but I did not set a time limit on myself and it took my about 2 hours.

  • Question 22
    • I got this question wrong because I thought that the super. would mess up the code, but the correct answer was B because you can only call methods in the function even if you did the super.
  • Question 23
    • I got this question wrong because I did not fully trace the code, I moved baboon and bass and assumed nothing else would change, but the last iteration had moved baboon back to its original spot.

Night At the Museum Peer Grading

  1. Cosmic Carnage
    • Uses Frontend
    • Uses Backend
    • Use API
    • Agile - HOOK:
    • Points: 4
    • Reason: The introduction of the project as well as eye catching project was very interesting - KNOWLEDGE:
    • Points: 3.8
    • Reason: Mostly one person was presenting, but all seemed to understand the project - VALUE:
    • Points: 0.9
    • Reason: Fun game, but the leaderboard didn’t populate - WOW FACTOR: 1
    • Reason: The animated front end is a really appealing and nice touch - Total: 9.7/10
  2. Code Monkeys
    • Uses Frontend
    • Uses Backend
    • Use API
    • Agile - HOOK:
    • Points: 3.9
    • Reason: The introduction of the project was kind of slow because they were setting it up slowly, but overall very cool idea - KNOWLEDGE:
    • Points: 3.9
    • Reason: They said that the project was not currently working, which made me question things, but they cleared up the issue quickly - VALUE:
    • Points: 1
    • Reason: Very cool project and people can learn how to use robots and coding robots - WOW FACTOR: 1
    • Reason: I like how it used a raspberry pi - Total: 9.8/10
  3. WHISP
    • Uses Frontend
    • Uses Backend
    • Use API
    • Agile - HOOK:
    • Points: 4
    • Reason: Cool graphics and introduction of the project made me very interested - KNOWLEDGE:
    • Points: 3.8
    • Reason: The project seemed to have many flaws in logic and the rules of the games, but overall very knowledgeable - VALUE:
    • Points: 0.8
    • Reason: Fun games, but I did not really understand the hitbox game, and the chess game can be found anywhere else for free - WOW FACTOR: 1
    • Reason: The live chess game was a cool touch - Total: 9.6/10

Timebox

  • Link
  • I have organized all of my student learning into my timebox of the CSA trimester one
  • I have done this to ensure my learning of the material is documented and easy to find again for later studying
  • For future trimesters, I will continue to add to the timebox to map out what I did the whole year as well as be able to study it for the AP test.

Lesson Grades

  • U1: 0.9/1.0
  • U2: We taught
  • U3: 0.9/1.0
  • U4: 0.9/1.0
  • U5: 0.85/1.0
  • U6: 0.9/1.0
  • U7: 1.0/1.0
  • U8: 0.9/1.0
  • U9: 9.2/1.0
  • U10: 0.9/1.0

Trimester 1 Reflection

  • I really enjoyed the time spent with my team, truly a great team. I believe it is a positive when your team are people you can get along with because the team members are more likely to share ideas, which may improve the project.
  • Things I have learned:
    • Most memorable thing I have learned are ArrayLists or Paaras says Airray. I find this to be avery useful tool for storing data. Since an ArrayList is able to modify the things inside of the ArrayList, it has an advantage over arrays, which are unable to be changed.
    • I have also learned about inheritance. This is an important piece of learning because it helps you organize the classes by the super classes and subclasses. This lets you make a super class of general information and the sub class to be much more specific. This is very good because it is neater.
  • What I hope to learn:
    • I hope to learn how to use vectors. The reason I would like to learn vectors is because I heard my brother using it and I tried researching it on my own and I couldn’t really find the benefits of using vectors over ArrayLists. So that is why I would like to learn about vectors in Java.