I’ve lately been trying to drive deeper into my skills and realized something: it’s very easy to build a 2-tier application "Todo List," but if you want to build something that actually survives the real world, you have to understand the "why" behind the layers.
This is me learning in public, and here is what I’m mastering this week:
I’ve started practicing this more because it’s more professional. It stops me from letting my Frontend talk directly to my Database, which is basically a security nightmare! Using a Backend middleman (Node.js/Express) to handle the logic keeps the data safe and the architecture clean.
Second, I used to think a domain name was just a label. Now I see it as a complex routing system using A Records to point to global servers. Understanding how it asks your computer, goes to the Top Level Domain, and finally finds your IP has been eye-opening. It definitely explains why some sites take a bit to load
Third, there’s something wild about knowing that anytime I send a message, it is broken into tiny chunks and reassembled perfectly using TCP when it reaches the receiver's IP address.
Honestly, recalling the DNS process was not easy. It’s a lot of steps! I’ve been using AI to breakdown the parts that didn't click, and it has been a total game-changer for my learning speed.
My Goal: I don't just want to "code," I want to understand the systems that make the code run.
To the seniors in the industry:
What is the one networking concept you wish you had learned sooner in your career, that you still use in your day-to-day runs?
Let’s chat in the comments ↆↆↆ
Top comments (0)