CST 363 Week 1

 This week has been really eventful and insightful, I am loving the structure of this class and the information we will learn. As someone who has been using database for quite a while, this is a great refresher. I have been using Oracle databases at work for the past year but I haven't learnt about it in detail. 

1. The difference between databases and spreadsheets comes in its functionality and structure. Databases enforce strict data types and relationships between tables using constraints like the primary key and foreign key. On the other hand, spreadsheets are more flexible and doesn't have the same enforcement. One other major difference is that using a database allows multiple users to work on it without having to face issues like when working on a single spreadsheet. 


2. Even though installing and configuration a database and learning how to use it is more complicated that just reading and writing data to a file, using a database ensures data integrity by enforcing the rules mentioned in point 1 and allow for effective and efficient data management. It makes it really easy to query for information you need and getting that information in the format that meets your business requirements. Databases are also designed for scalability and can handle a huge volume of data along allowing multiple people to work on that data with no problems. And finally using a database correctly can help you in the case of getting your data deleted where you can get it back if it ever gets corrupted. 


3. For me personally, I am really interested in learning different types of databases and very excited to learn about MongoDB and of course getting a refresher is always a plus. 

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