CST363 Week 6

This week has been pretty challenging, but also really rewarding. Working with the team to get this project done wasn’t easy, but I definitely learned a lot along the way. We had to build a system to manage prescriptions, doctors, patients, and pharmacies, and it really pushed me to understand how everything fits together. We used JDBC for connecting to the database, Spring for organizing everything, and Thymeleaf to build the web pages.


Usually, I’ve worked with JPA, Hibernate, and JSF in the past, so doing things with JDBC and Thymeleaf was a bit different for me. It felt more hands-on since I had to write all the SQL queries myself and manage things like transactions and exceptions directly, rather than relying on an ORM like Hibernate to handle a lot of that for me. It was an interesting change, and I liked seeing how things work at a more detailed level. One of the biggest things I learned was how to handle data properly with JDBC. 

We spent a lot of time making sure things like RXIDs, patient names, and pharmacy details were validated correctly. If something was wrong, like an invalid pharmacy name or a wrong RXID, the system had to handle it and show helpful messages. It wasn’t just about writing SQL queries, it was about making sure the system responded the right way when things didn’t go as planned.

Spring was a big help in keeping everything organized, especially with managing the database connections using JdbcTemplate. It made the code a lot cleaner and easier to work with. 

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more