Week 6 postings- Reflections

 This week’s chapters on TCP/IP, applications, and naming networks were a little more technical, but once I got into it, it actually started to make sense how everything connects.

Starting with TCP/IP, I’ve heard the term before but never really understood what it actually did. Now I get that it’s basically the foundation of how devices communicate over a network. TCP makes sure data gets delivered correctly, while IP handles the addressing part. It’s kind of like sending a package—IP is the address, and TCP makes sure it actually arrives without anything missing. I didn’t realize how much coordination goes into something as simple as loading a webpage or sending a message.

The applications part helped me connect TCP/IP to real-world use. Things like web browsing, email, and file transfers all rely on specific protocols working behind the scenes. For example, HTTP/HTTPS for websites and things like FTP for file transfers. It’s interesting because we use these every day without thinking about what’s actually happening in the background. It made me realize that every app we use depends on these protocols working correctly.

Naming networks was another topic that I didn’t think would be that important, but it actually is. Things like domain names and DNS make it possible for us to use easy-to-remember names instead of IP addresses. I can’t imagine trying to remember a bunch of numbers for every website. DNS basically acts like a translator between human-friendly names and machine-friendly addresses. Learning about how networks are named and organized also showed me how important structure is, especially in larger systems.

Comments

Post a Comment

Popular posts from this blog

Week 1 Posting - Will Ai predict heart failure patients

 Through my findings of IT, I came into an article about how Ai can potentially predict which heart failure patients will worsen throughout the year. I found this very interesting because it really highlights how technology is being used in more ways than just what we have our understanding of with computers and networking. One thing that stood out to me is how the system can take something as simple as an ECG and then use it to predict future problems with the heart. Which to me sounds crazy cause normally I feel like you would expect doctors to make you take a lot of complicated tests to figure that stuff out. This could lead to less time wasted and a quicker response in the process. However, it is worth mentioning even though this technology sounds amazing it still has it challenges like dealing with messy or incomplete data. So, if the data isn't clean the predictions might not be so reliable. Which in this instance can be more detrimental since it deals more with real patients...
Read more

Week 5 Postings- Reflections

 This week’s chapter on TCP/IP and routing was honestly one of the more challenging ones, but also really important. Before this, I had heard of TCP/IP a lot, but I didn’t fully understand how it actually works behind the scenes. Learning that TCP/IP is basically the foundation of how devices communicate over a network made me realize how critical it is to everything we do online. One thing that stood out to me was how TCP and IP have different roles but work together. TCP is responsible for making sure data gets delivered correctly and in the right order, while IP handles addressing and getting the data to the right destination. I thought it was interesting how TCP breaks data into smaller packets and then reassembles them on the other end. It kind of made me think of sending a bunch of puzzle pieces that get put back together when they arrive. Routing was another part that took some time to understand. The idea that routers decide the best path for data to travel across network...
Read more

Week 7 postings- Reflections

 This week’s chapter covered troubleshooting, display technology, and virtualization, and it honestly felt like a mix of super practical stuff and more advanced concepts. The troubleshooting part stood out the most to me because it’s something I’ll actually use all the time. It’s not just about fixing things randomly, but following a step-by-step process like identifying the problem, testing solutions, and documenting what you did. I realized that being organized with troubleshooting can save a lot of time instead of just guessing and hoping something works. The section on display technology was also interesting because I never really thought about how many different types of displays there are. Learning about things like LCD, LED, and resolution differences made me realize why some screens look way better than others. It also helped me understand things like refresh rate and response time, especially for gaming or media. Now I actually get why people care so much about monitors an...
Read more