Week 3 Learning Journal – Time, Ethics, and Becoming a Thoughtful CS Student

Part 1: Rethinking How I Manage My Time

This week I focused on time management, specifically the strategies outlined on AcademicTips.org. Since procrastination has been something I’ve struggled with, I decided to go through the full personal time survey. Honestly, it was a bit of a wake-up call.

Once I added up how much time I spend on sleep, commuting, meals, classes, exercise, and other daily routines, I realized I do have time left for studying. But I haven’t been using that time in a meaningful or structured way. A lot of it gets lost in distractions or doing “just one more thing” before I start homework. This made it clear that it’s not really a lack of time. It’s a lack of intentional use of time.

The Study Hour Formula also shifted my perspective. I used to assume every class required the same amount of study time, but that’s not realistic. Now I’m thinking about my classes in terms of difficulty. Courses like Data Structures and Systems Programming clearly require more hours than general electives. I’ve started breaking down my schedule accordingly and setting specific blocks of time for harder subjects.

A few other strategies stood out too:

• Learning to say no has been important. I’ve gotten better at recognizing when I need to protect my time, even if it means skipping out on casual plans or social events.

• Letting go of perfectionism has helped me avoid that “I’ll start when I’m ready” mindset. I’ve learned it’s better to begin imperfectly than to wait for the perfect conditions.

• Prioritizing tasks using an A-B-C method has helped organize my day. A tasks get done today, B tasks need attention soon, and C tasks can wait. This keeps me focused on what actually matters.

• Combining activities has also been a game changer. I now listen to coding podcasts while walking or cooking. It helps me stay engaged with tech even outside of study hours.

This week made me realize that time management isn’t about doing more, it’s about doing what matters with the time I already have. I’ve already started applying these tips to my daily routine, and I feel more in control and less overwhelmed.

Part 2: Ethics in Tech – What Really Matters

The ethics material this week went much deeper than I expected. We started with the video “Ethics in the Age of AI” from the World Economic Forum, and it raised a question I hadn’t really thought about before: Could AI and new technology change what it means to be human?

The conversation started with common concerns like privacy, misinformation, and job loss. But what really grabbed my attention were the deeper issues like the use of AI to bring back actors who have passed away, or to digitally recreate people for entertainment. It made me think: even if someone consents, is that enough? Are we crossing a line when we recreate someone’s presence without their actual involvement?

Michael B. Jordan said something that really stuck with me. He talked about how, even if the technology could perfectly recreate his grandmother’s voice or image, it still wouldn’t feel right. It wouldn’t be her. The emotional connection, the way she looked at him, the way she smelled or smiled. Those things can’t be replicated by an algorithm. And I agree. No matter how advanced AI gets, there’s a level of authenticity and dignity that only comes from real human presence.

The debate about AI in matchmaking also made me think. If a dating app could use data to find the perfect partner, would we trust it more than a parent’s advice? Some people in the discussion argued that the awkward first dates, the missteps, and even the heartbreaks are part of the experience. Skipping over that just to find the "perfect" match feels like it would take away something essential about how we grow and connect with others.

This tied in perfectly with the ACM Code of Ethics, which we also reviewed. The line that stood out to me most was: “The public good is always the primary consideration.” That’s powerful. As developers, it’s easy to get caught up in solving problems or building something cool, but if we don’t think about how our work impacts people, we’re missing the bigger picture.

The ACM Code also emphasized honesty, fairness, and respect for privacy. It reminded me that technical skill alone isn’t enough. Being a good developer also means being a responsible one. Whether it’s protecting user data, avoiding bias in algorithms, or designing for accessibility, everything we build affects someone’s life. That’s a big responsibility and it’s one I want to take seriously.

Part 3: What a CS Major Really Needs to Know

Reading “What Every Computer Science Major Should Know” by Matt Might gave me a lot to think about. It wasn’t just a list of technical topics, it was a reminder that being a CS student means more than just checking off courses.

One big takeaway was the idea that I need to build a portfolio, not just a resume. That really hit home. Employers don’t just want to see what classes I’ve taken, they want to see what I’ve built, how I think, and how I solve problems. I’ve started cleaning up my GitHub and plan to document more of my projects, even the unfinished ones. It’s about showing that I can create, not just learn.

The article also stressed the importance of technical communication, and I couldn’t agree more. It’s not enough to write functional code if I can’t explain what it does or why it matters. I’ve seen this firsthand in group projects. Clear communication makes all the difference.

Another part that resonated with me was the reminder to stay curious. The field of computer science is always changing. New tools, languages, and frameworks are constantly emerging. What really matters is being open to learning, thinking critically, and adapting as needed.

It was also humbling to read how much more there is to explore. Things like systems programming, Unix tools, algorithmic thinking, and even ethics. There’s no way to learn it all at once, but that’s part of what makes this journey exciting.

Part 4: Integrity That Lasts

If there’s one theme that tied everything together this week, it was integrity. Whether it’s how I manage my time, how I build software, or how I treat people’s data, doing the right thing matters.

Before this week, I thought of integrity mostly in academic terms, don’t cheat, don’t plagiarize, do your own work. But now I see it as something much bigger. It’s about being someone people can trust. It’s about being honest when I hit a wall and asking for help the right way. It’s about giving credit where it’s due, and being clear about the choices I make, both in code and in life.

As future software developers, we’re going to be responsible for building tools that others rely on. That’s a big deal. If we’re careless or dishonest, we could do real harm. But if we lead with integrity, we can build things that genuinely help people. That’s the kind of developer I want to be.

Final Thoughts

This week gave me a lot to think about, how I use my time, how I approach learning, and what kind of impact I want to have as a future CS professional. I’ve started applying better time management techniques, and I feel more in control already. The ethics discussions reminded me that tech isn’t just about tools, it’s about people. And the readings on integrity and responsibility helped me see the bigger picture.

I’m starting to understand that being a great CS student isn’t just about solving problems. It’s about asking better questions, thinking critically, and staying true to what matters. And honestly, I’m excited to keep learning, growing, and figuring it out one step at a time.