From adee39601c41487071b89a412dea83d0efec5bbd Mon Sep 17 00:00:00 2001
From: Omer Syed <90342893+omersyed9@users.noreply.github.com>
Date: Mon, 11 Dec 2023 15:51:47 -0500
Subject: [PATCH] Update testimonials.md

---
 resources/testimonials.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/resources/testimonials.md b/resources/testimonials.md
index 7291911..9d3d4b2 100644
--- a/resources/testimonials.md
+++ b/resources/testimonials.md
@@ -16,3 +16,5 @@ When creating your assignment schedule at the start of the semester, avoid letti
 
 In order to succeed on this class, I strongly suggest to start doing practice badges every day after class so that that way you do not have to rush at the end of the semester to do all of the work last minute. I struggled a lot in the beggining because I did not know how the practice badges worked too well so I just wouldnt do them. I would aslo try to not miss a single lecture because even though you can make up the experience report, it is kinda annoying to do it as sometimes they require evidence which is annoying to get. Overall if you stick with not skipping classes, doing practice badges every day after class, you should be all set to pass this class. 
 
+To succeed in CSC 392, I would suggest being on top of every single assignment that is being assigned, ideally the day they are due. It's easy to look at a badge, see something you're confused at, then put it off for later, but continuosly doing so will make it harder in the long run. Taking advantage of the office hours and the TA's makes it ten times easier to get through any roadblocks you have, and the plus side is it helps you actually learn about something that is so practicle in the computer science or software engineering world. Another suggestion I would make is to not miss any labs or lectures, you need every single lab in this class and you practically need every single lecture badge (experience) and those are achieved by working on them in class/labs. 
+