Skip to the content.

Trimester 1 Summary

For beginning of Trimester 2 review.

Executive Summary for Trimester 1

Executive Summary:

  • Self Grade: Earned 55/66 on MCQ, approximately 6 mistakes were silly mistakes based on misreading or not reading properly, and the other 5 were content related mistakes as described below. My most important contributions to sprint 3 were helping the initial design, the AI game (image posting, gemini AI prompt engineering, small features), backend to frontend integration for main post room and chat room.

MCQ Mistakes and Content Learned:

  • 33% on Data Compression, 50% on Crowd Sourcing, Algorithmic Efficiency, 67% on Safe computing, 60% on Calling Procedures are some of lowest categories.
  • Crowd sourcing: Enables various individuals to access information and collect data, but it is not a valid approach to distributing computational workload.
  • Encryption (public and private keys): In public encryption, the sender’s public keys encrypt the message, and the recipient’s private key is used to decrypt it.
  • Time Complexity: n^2 time complexity is executable, and most polynomial time complexities are runnable for moderately large sample sizes. The exponential (i.e. 2^n) time complexities or factorial time complexities are a problem. In rare cases super-exponential (n^n) also cause issues.
  • Byte Encoding: A type of encoding where repeating motifs are abstracted with special characters, so it doesn’t work in cases where no motifs are repeated.
  • Lossy and Lossless Transformations: Lossy transformations are where the data after encoding can’t be restored, and lossless transformations are where data is compressed with a loss in data quality.
  • Silly Mistakes: Mistakes because didn’t read the question carefully or didn’t read all answers carefully.

Specific Questions

  • Defining Internet Enabled Crowdsourcing
  • Results of the KeepPlaying Procedure
  • Encrypting and Decrypting using public key crytography
  • Infinite loops in undecidable problems
  • Runtime of algorithm for online retailer
  • Comparing smartphone and reading data in graph
  • Completing Robot Code by adding if statement
  • Shortening strings by replacing TH and IS
  • Compression by replacing TH and IS with characters
  • Procedure to determine the weather
  • Comparing robot algorithms
  • General Observations: On algorithms with long programs or answers, I tend to make foolish mistakes due to question length - may be a test taking skill to work on. And the general gaps in knowledge as mentioned previously.

Sprint 3 Contributions

  • Initial Figma Design: Brought the idea of using Figma, and built the basic flow of the webpage and helped guided the design process.
  • AI Game: Made the chat feature, added the Modal, optimized the prompt to act like a realistic human to some extent. Added other small features for realism (the loaded prompt, the time delay, the “typing…” thing)
  • Backend Integration: Added the backend integration to the main posts page and the posts for the chat room. Used the REST API with fetch requests on the frontend. Sended data in JSON, using post and get requests, etc.