Week 4

Part One: Set Your Educational Goals

My main educational goal in the CS program is to graduate with a strong foundation in cybersecurity and automation. I want to finish with a GPA above 3.9 and develop at least five practical projects that I can include in my portfolio — two related to cybersecurity (like penetration testing or scripting with Python) and three that show automation and data processing skills (such as workflow automation or analytics dashboards). I can picture myself in my workspace, pushing my final project to GitHub, preparing for graduation, and seeing the growth I’ve achieved in both coding ability and confidence.

Beyond this degree, I plan to pursue a graduate certificate or master's program in cybersecurity while continuing to develop my technical certifications (I already hold CompTIA A+). I want to stay ahead of trends in the field and build a career that merges defensive security and ethical hacking.

---

Part Two: Set Your Career Goals

In the short term, I’m aiming to get a full-time job in IT or cybersecurity support not long after I graduate. Ideally, I’d love to work for a school district, a city agency, or even a private company that values people who are eager to grow and contribute. I’m looking for a role where I can actually put my scripting and automation skills to use, maybe even help with basic security checks or support the team during incidents. I want to be someone who can solve real problems and keep things running smoothly.

Looking ahead a few years, my goal is to become a Security Analyst or Penetration Tester — hopefully in a remote or hybrid setup. I’m aiming for a salary between $90K and $110K within five years. More than the money, though, I want to feel like I’m really making a difference by stopping security threats and helping protect organizations from attacks. I want to be that go-to person who can figure things out when something goes wrong.

---

Part Three: Wild Guess of My ETS Computer Science Percentile

After checking out the ETS Major Field Test in Computer Science, including the example questions and structure, I feel reasonably good about where I stand right now. I still have a lot to learn, but I think 18 months gives me enough time to close the gaps. Right now, I’m pretty solid in areas like programming, discrete math, and software engineering. I know I need to put more time into systems topics and networking — those are definitely my weak spots.

If I keep reviewing consistently and keep building projects to practice what I’ve learned, I think I could score somewhere around the 80th percentile — maybe a bit higher if I stay focused. It won’t be easy, but I like a good challenge.

---

Part Four: What I Learned This Week

This week’s readings helped me see how important it is to take control of my own career development — especially the article on setting career and salary goals. It was interesting to learn that the famous Harvard goal-setting study might be a myth, but the broader lesson still holds: people who write clear goals and track progress are more likely to succeed.

I also reflected on the idea of constantly updating skills and avoiding career complacency. This motivated me to keep improving my portfolio and track my accomplishments throughout the year. I’ve started keeping a document with milestones I’ve achieved so far in this program — like building a partial inventory system with Python, working with Excel automation, and studying for CompTIA Network+, and Security+.

Finally, I explored the structure and content of the ETS Computer Science test. It gave me a better sense of what to expect and what areas I should start revisiting soon, especially discrete math and algorithms. It’s one more reminder of how important preparation is — not just for school, but for the kind of career I want to build.

Industry Expert / Executive Interview Exploring Career Paths and Industry Trends

 

Industry Expert Interview – Post-Interview Reflection

Interviewee: Sothy Lean
Title: Information Technology Specialist
Organization: Fresno Unified School District

---

Introduction

For this assignment, I talked to Mr. Sothy Lean, who works as an Information Technology Specialist for Fresno Unified School District. I reached out to him mainly because he’s in the same district I work in, and I’ve always noticed how dependable the IT department is—especially in high-pressure moments. Honestly, I’ve seen them work during device outages and internet issues, and it’s made me respect how much they do behind the scenes.

When schools shifted to remote learning during the pandemic, the tech team kept things afloat. That left an impression on me, and I’ve wanted to better understand what goes into their day-to-day ever since. Mr. Lean seemed like the right person to talk to because he’s done this for over 30 years, starting in a basic support role and gradually growing into more advanced responsibilities. I figured his perspective would be a good reality check—something deeper than what you find in textbooks or job ads.

Since I’m thinking about moving into cybersecurity or an entry-level IT support position myself, I thought this would give me a chance to see the path more clearly and ask the kind of questions I couldn’t find on Google.

---

Summary of Key Takeaways

One of the biggest takeaways from our conversation was how unpredictable and sometimes chaotic IT support can be, especially in a school district setting. Mr. Lean said that even now, he often finds himself jumping in to repair devices or troubleshoot network issues because there simply isn’t enough staff to go around. It surprised me how much improvisation the job still requires.

He explained how priorities shift minute by minute—you might be working on a device update when someone suddenly needs help connecting to the Wi-Fi, and then another person shows up with a broken screen. There’s no “normal day” in this role. That kind of flexibility and calm under pressure is something he’s learned over time.

Something else that stood out was how tools and platforms have changed drastically since he started. He mentioned how cloud services like Microsoft 365 and Google Workspace are now baked into almost every part of school operations. Also, he talked about newer tools like JAMF and Intune for managing devices remotely. I didn’t even know schools were using that level of software for endpoint security.

When we moved into the topic of cybersecurity, he brought up phishing scams and ransomware attacks, especially how schools are increasingly being targeted. What really made me stop and think was when he said that IT support staff—especially in schools—are often the first people to detect when something’s off. That kind of frontline responsibility wasn’t something I had considered.

But honestly, what hit me most was when he started talking about soft skills. He said knowing how to communicate with non-technical people is just as important as knowing how to fix the problem. A lot of his time is spent helping teachers and staff understand what went wrong without overwhelming them with tech jargon. He also stressed patience—something he admitted he had to learn the hard way.

Before wrapping up, he gave me a few pieces of advice. First, just start wherever you can, even if that means helping someone with a minor issue. Second, don’t be afraid of mistakes—he said they’re part of learning. Third, he said certifications like CompTIA A+ and Network+ are helpful, but they’re not enough on their own. What matters most, he said, is experience—figuring things out, tinkering, breaking stuff, and fixing it.

---

Reflection

Before this interview, I had a general idea of what working in IT looked like, but it was pretty vague. I thought it would mostly be responding to help desk tickets and installing software. After talking with Mr. Lean, I realized that there’s way more to it. The job requires flexibility, people skills, a good memory, and honestly—some thick skin too.

What really made an impact on me was learning how he built his entire career through hands-on learning. No fancy degrees, no bootcamp. Just decades of showing up, being helpful, and not being afraid to say, “I’ll figure it out.” That reminded me a lot of my own approach. I’ve always been a “learn by doing” type, and hearing that someone succeeded by following that same style gave me more confidence in myself.

I also appreciated how honest he was. He didn’t try to make the job sound easy or glamorous. Instead, he told stories of long days, of having to repair 15 Chromebooks before lunch, of being called into classrooms mid-lesson. That kind of transparency made it feel real. It made me want to prepare myself not just technically, but mentally too.

What I took away from his experience is that it’s okay not to have all the answers at the beginning. The key is to be curious, keep learning little by little, and take chances to help when I can.And when mistakes happen (because they will), to treat them as part of the path rather than proof that I’m not cut out for it.

---

Future Steps

I’m taking several steps after this interview, and they’re all based on what we talked about:

• I’m going to finish my CompTIA Network+, which I’ve been studying for, and then go straight into Security+ to round out my understanding.
  
  

• Lately I’ve been messing with an old laptop I had lying around — not great hardware, but I’ve been using it to try out virtual machines and test stuff I’ve been learning. I wouldn’t say I have a perfect setup or anything, but it’s kind of nice to have a space where I can just try things and not worry if I break something.
  
  

• Also, I’ve realized I need to get better at talking about tech without making it confusing. Sometimes I go too fast or use words people don’t follow, especially if I’m nervous. I’m trying to slow it down and explain things in a way that actually helps — maybe just by practicing with people I already know.
  
  

• I’ll stay connected to mentors—especially Mr. Lean if he’s open to it. Even just sending updates or asking small questions can help me stay engaged.
  
  

• I’ve been trying to stay more in the loop with tech stuff — sometimes that just means watching a random YouTube video or skimming through a forum when I get a chance. Things change so quickly that if I don’t check in every now and then, I feel like I’m already behind.
  
  

• Finally, I’ll volunteer whenever I can, whether at work or through side projects, to keep gaining experience. I realize now that even small tasks add up to something bigger over time.
  
  

---

Closing Thoughts

After we talked, I kept thinking about everything he said. It honestly shifted how I’ve been seeing the whole IT field. I used to think you had to be some kind of genius to make it, but now I get that it’s more about being consistent, learning on the fly, and being the kind of person people can count on. I left that conversation feeling more motivated — not just because I’m into tech, but because I actually want to help people and fix real problems when they happen.

And for the first time in a while, I’m not overwhelmed by where to begin. I’m actually excited to take the next step.

Week 3

 Part 1 – Study Tip Reflection

One of the areas that I recognized was a weakness for me was being consistent with the SQ3R Method. After reviewing the strategies through www.academictips.org, I understood that my biggest gap is with the Recite and Review phases. I find that I often read and highlight, but I do not actually engage with the content out loud in the Recite phase, and that I do not go back to the text after I have read it the first time unless a test is looming. From the tips I learned it is so important to make reviewing a habit and not just a hurried attempt when you need to prepare for assessments. I will start summarizing readings in my own words, and will review them constantly so that I can hopefully build better retention. 

An area that I am actively working on is not being a passive reader. I tend to over-highlight thinking that will help me later, then I forget why I highlighted what I did. I am going to start  shifting from longer cramming sessions to shorter study blocks with breaks, it means study for 40 minutes and take 10-minute breaks. 

Part 2 – Ethics Material Reflection

This week's ethics materials made me think about the responsibility we are going to carry as future computer scientists. The talk about ethical frameworks helped me understand that people think about justifying their decisions very differently, such as who is affected by the decision and outcomes, duties, or self-interest. For example, in my ethics essay about self-driving cars, I will write on why some people might support or argue from a Utilitarian point of view (maximizing safety for everyone), while others might argue from the one of Egoist self-interest (companies wanting to maximise their own freedom of innovation). 

Part 3 – Reflection on "What a CS Major Needs to Know"

Reading "What a Computer Science Major Needs to Know" was an eye-opener. It helped me understand computer science is not only about coding, rather it is more about thinking deeply, solving problems, and having a lifetime of continued learning. Algorithms, data structures, and version control are not particularly easy topics, but they are the foundation upon which real software development is built. I also understood the amount of self-teaching we will need to do as well. 

Part 4 – Reflection on the CSUMB Code of Integrity

When I read the CSUMB Code of Integrity, I thought about what kind of student and professional I wanted to be. In a major like computer science where collaboration is common and the internet is full of helpful resources, it's really easy to want to cut corners or "borrow" ideas, but it's not only damaging from my experience and learning, but it also destroys the credibility I might have as a future professional. I want to be the kind of person that others would trust, ask for help when I need it, and even ask for an opinion. Academic integrity is much more than a rule, it is at the foundation of everything we create.

Week 2

 Part 1: Review and Reflect Learning Strategy

Top 3 Areas I Am Good At

1. Creating and Following a Study Schedule: I am extremely disciplined about managing my time. I time block my study time with the same time block for work, family commitments, and classes. I always build in time for the unexpected to revise my schedule, in line with Dr. Kizlik's suggestion to have a schedule that is flexible yet reliable.
   
   

2. Note-Taking and Reviewing: I take notes in one notebook separated by subject. I also read my lecture notes as soon after class as I can to clarify confusing points, cementing understanding when the material is as fresh as possible. I often summarize topics, an approach that the SQ3R method emphasizes and suggests.
   
   

3. Maintaining a Productive Study Environment: I also always try to have everything set up before I start to help reduce interruptions. I always choose quiet, distraction free locations like libraries or dedicated home spaces. This is inline with the tip about having an organized study space with everything nearby.

Top 3 Areas Where I Feel I Am Weak

1. Using the SQ3R Method Fully and Consistently: Although I use several techniques such as summarizing and questioning, I do not always do step by step, Survey, Question, Read, Recite, Review. Often, I skip out on actually reciting aloud or thoroughly reviewing unless a test is approaching. My goal is to use this as a habit, not just a technique I do sometimes.
   
   

2. Outlining Textbooks and Avoiding Passive Reading: I still sometimes over-highlight or underline rather than actively outlining chapters or pulling out main ideas and key details. I recognize outlining allows me to connect ideas more naturally and improves long-term retention, so I need to stop reading passively.
   
   

3. Short, Focused Study Sessions with Breaks: When I feel behind, I often try to cram in long segments of study time without breaks. I learned from the guide that studying over a longer time (30–40 minutes) with breaks improves retention, and decreases burnout. I need to begin to incorporate study breaks into my practice, so I can study smarter, not harder!

Part 2: Preview Time Management Skills

 

 

 

 

 

 

 

 

 

Part 3: Project Management Basics

The three short videos are an excellent introduction to project management because they present concepts that are easy for anyone to understand and relate to. They highlight what makes a project unique, with a clear goal, timeline, and budget - which is much different than the ongoing or day-to-day work we are used to. I really enjoyed the identification of a project manager being a Chief Executive Officer of the project, in that it helps us realize how critical the project manager's role is, to keep everyone and everything on track. The Work Breakdown Structure and Gantt Chart were two tools I found particularly useful, in terms of breaking the work down into manageable pieces and being able to visualize the schedule. All in all, the videos provided a valuable understanding that with good planning, defined roles and tools, the success of any project can be more easily guaranteed.

Part 4: Check Out Previous Capstones

1. Otter Parsing (OtterSoft Team)

Type of project: NLP-powered Resume Parser

Reflection: This was a real-world HR and recruiting project that was both technical and hands-on. The team built a resume parser in Python using SpaCy and Prodigy to get structured data from unstructured PDF resumes. They implemented a thorough process and demonstrated knowledge of model training, annotation, and data processing. The demo was well done and clear, and it demonstrated the ability to identify relevant sections of a resume and output those sections in JSON format so that they could be easily filtered.

Was it well done? Yes. The team dealt with complex challenges like PDF parsing inconsistencies and training data limitations effectively.

Improvement suggestions: They could improve the user interface further and integrate scalability testing, as they acknowledged performance concerns when parsing large batches.

2. Security Scan Summary (U.S. Naval Research Laboratory)

Type of project: Cybersecurity Report Simplification Tool

Reflection: The project goal was to convert complicated static code analysis (SARIF files) into easy to comprehend, visual graphical summaries in PDFs. The social and organizational value was useful to me—facilitating an understanding of security vulnerabilities for non-technical stakeholders is a significant problem. The tool was developed in Python, and had a tidy presentation flow. In the final reports the graphics represented well and were closely connected with the mission of improving communication across teams.

Was it well done? Yes, especially in terms of team collaboration and client-oriented problem solving.

Improvement suggestions: Future iterations could include interactivity in the reports (e.g., clickable summaries or expandable sections) and support for additional file formats like JSON.

3. A Bird Song (Game Dev Team)

Type of project: 2D Educational Video Game

Reflection: This was a narrative-driven project that dealt with the extinction of the Kauai O’o bird through the lens of environmental destruction. It was developed in Unity with original art and level design, and was emotionally motivating and artistically made. I thought that the ways that the game used environmental storytelling with the game mechanics was great inspiration. It was a nice change from the other, more technical projects and demonstrated the different paths that computer science can take.

Was it well done? Absolutely. The art, sound, and gameplay were cohesive, and the story was meaningful.

Improvement suggestions: Adding difficulty progression, achievements, or alternate endings could improve replayability and engagement.

Part 5: Summarize Your Week on Your Learning Journal

This week’s reflection allowed me to recognize my personal learning strengths and learning challenges. I am confident in my ability to manage my time with a structured schedule, organize my learning space, and take appropriate notes. Following these habits has kept me on track even given my work and family responsibilities. I did recognize that I still struggle with using SQ3R consistently, avoiding passive reading, and my ability to remember to take short breaks when studying for long periods of time. This is an area that I desire to improve and become more efficient when studying and avoiding burnout.

I also enjoyed looking through past capstone projects, specifically Otter Parsing, the Security Scan Summary, and A Bird Song. Each one presented a different side of computer science. I was amazed by the capabilities of NLP in making hiring more efficient, taking cybersecurity data and providing the user with information concisely, and even through DRM adult video game design, allowed for telling a meaningful environmental story. I guess I had forgotten how varied and amazing this discipline can be and how not only the technical skill but also the creative way systems can be manipulated by technical skills.