<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Fundamentals on Tribhuwan Kandpal</title><link>http://tribhuwan.dev/tags/fundamentals/</link><description>Recent content in Fundamentals on Tribhuwan Kandpal</description><generator>Hugo -- 0.148.0</generator><language>en-us</language><lastBuildDate>Wed, 31 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="http://tribhuwan.dev/tags/fundamentals/index.xml" rel="self" type="application/rss+xml"/><item><title>The OSI Model: Stop Memorizing Acronyms, Start Understanding Layers</title><link>http://tribhuwan.dev/posts/osi-model-layers-explained/</link><pubDate>Wed, 31 Dec 2025 00:00:00 +0000</pubDate><guid>http://tribhuwan.dev/posts/osi-model-layers-explained/</guid><description>&lt;p>You’ve probably seen the diagram: seven colored boxes stacked vertically with cryptic acronyms—PHY, DLL, NWK, TRM, SES, PRS, APP.&lt;/p>
&lt;p>If you are like most people learning networking, you memorized them for an exam —or maybe an interview —nodded, and moved on without truly understanding &lt;em>why&lt;/em> they exist.&lt;/p>
&lt;p>Here is the reality:&lt;/p>
&lt;p>&lt;strong>Layers aren’t physical things. They are agreements.&lt;/strong>&lt;/p>
&lt;p>They are protocols — a shared understanding between two systems on how to talk to each other.
Understanding this distinction changes everything about how you debug, architect, and think about networking.&lt;/p></description></item></channel></rss>