Skip to main content

Lost in the Terminal, Found in IntelliJ

During Week 1 of CST 338: Software Design, we covered Lab 00 and Lab 01, which introduced essential foundational tools like unit testing, Git, and interfaces. One of the highlights for me was learning how to integrate GitHub with IntelliJ. I was genuinely amazed at how seamlessly these tools work together, and I’m excited about using them in collaborative projects later in the course. Setting up version control and seeing how commits, branches, and pull requests function in a real development environment made the learning experience feel both practical and professional. Learning how to write and run unit tests also stood out—it’s clear how crucial they are for ensuring code correctness and preventing regressions, especially in larger codebases.

Although the bulk of the material on interfaces is scheduled for next week, the early introduction helped me start forming a mental model. I’m beginning to understand how interfaces provide structure and promote flexibility in code design. It’s a concept I’m eager to explore more deeply.

One challenge I faced this week was time management. Adjusting to the course schedule while also studying for my cybersecurity certification was difficult, but it reminded me of the importance of planning and staying on top of the weekly workload. I also realized that skipping over training materials to get straight to the assignments makes things more confusing and time-consuming in the long run. Fortunately, the recorded videos and detailed instructions helped me catch up and understand the material thoroughly. I’m grateful that the course is designed with support in mind—it makes a big difference for online learners. Going forward, I’ll prioritize the training resources and improve my scheduling to stay ahead.




Comments

Popular posts from this blog

CST462S - From Learning to Impact: My Service Learning Journey

What went well during my service learning experience was my ability to contribute meaningfully to the ASCENDtials web team. I was able to complete several tasks such as updating website pages, working on LifterLMS courses, and improving user experience through better layouts and navigation. I also communicated effectively with my team, asked questions when needed, and stayed consistent with meeting deadlines. Over time, I became more confident using tools like WordPress, WPForms, and course-building platforms. If I could improve something, it would be my time management and planning. There were moments when tasks felt overwhelming, especially when balancing schoolwork and service hours. I would also improve my confidence in decision-making, particularly when working independently on design or technical issues. Taking more initiative earlier and asking for feedback sooner would have made my work even stronger. The most impactful part of this experience was seeing how my work directly co...

CST438: Hands-On System Testing and Cloud Technologies

This week, I worked on both system testing and understanding cloud and distributed system concepts. One of the main things I learned was how to build Selenium system tests that simulate real user behavior. I created tests in which an instructor enters final grades and in which instructor-created assignments appear in a student’s view. While doing this, I learned how important it is to have all parts of the system running, including the frontend, backend, and external services like the gradebook. I also improved my debugging skills by fixing issues with Selenium, such as incorrect XPath selectors, missing UI elements, and unnecessary alert handling. I also learned how to properly manage my code using Git and GitHub. I created branches, committed my changes, pushed them to GitHub, and opened pull requests for review. This helped me understand a more realistic development workflow and how collaboration works in a team environment. In addition to coding, I reviewed several key concepts i...

WHERE I’m At: Midpoint Lessons in SQL and Beyond

 Halfway through this course, I can see how much I’ve learned and how it connects to both my past experiences and my future goals. One of the biggest takeaways has been understanding how SQL views work. I now know that a view is like a virtual table, useful for simplifying queries and presenting data, but usually read-only since it doesn’t store data itself. I’ve also learned the importance of normalization, which helps remove redundancy and ensures cleaner updates by splitting one large table into multiple related ones. Another valuable lesson has been comparing SQL with Java: SQL is declarative and focuses on the “what,” while Java is procedural and focuses on the “how.” This comparison helps me appreciate each language’s role in problem-solving. I’ve also seen firsthand how powerful SQL can be in real workflows compared to spreadsheets, such as enforcing business rules like course eligibility in a single query. Beyond SQL, I’ve grown as a programmer in general—planning better, w...