<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Islam on Medium]]></title>
        <description><![CDATA[Stories by Islam on Medium]]></description>
        <link>https://medium.com/@hsnislam2026?source=rss-6d64d3d411d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Islam on Medium</title>
            <link>https://medium.com/@hsnislam2026?source=rss-6d64d3d411d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:49:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hsnislam2026/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Happens When You Type https://www.google.com in Your Browser and Press Enter?]]></title>
            <link>https://medium.com/@hsnislam2026/what-happens-when-you-type-https-www-google-com-in-your-browser-and-press-enter-95f69f5efc2c?source=rss-6d64d3d411d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/95f69f5efc2c</guid>
            <dc:creator><![CDATA[Islam]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 19:48:23 GMT</pubDate>
            <atom:updated>2026-08-09T19:48:23.627Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever wondered what happens behind the scenes when you type https://www.google.com into your browser and press Enter? A lot of things happen in just a few seconds. Your browser communicates with several systems across the Internet before the Google homepage is displayed.</p><p>Let’s follow the request step by step.</p><h3>1. DNS Request</h3><p>The first thing the browser needs to know is the IP address of <a href="http://www.google.com./">www.google.com.</a></p><p>Computers communicate over networks using IP addresses, but humans prefer domain names such as www.google.com. The Domain Name System (DNS) translates domain names into IP addresses.</p><p>The browser first checks whether it already knows the IP address from its cache. If the address is not cached, the computer sends a DNS request to a DNS resolver.</p><p>The resolver may contact several DNS servers, including root servers, Top-Level Domain (TLD) servers, and authoritative name servers. Eventually, it receives the IP address associated with <a href="http://www.google.com./">www.google.com.</a></p><p>For example, the result may be an IPv4 address such as:</p><p>142.250.x.x</p><p>The exact address can change depending on Google’s infrastructure and your location.</p><p>Now the browser knows where it needs to send the request.</p><h3>2. TCP/IP Connection</h3><p>After obtaining the IP address, the browser needs to establish a network connection with the Google server.</p><p>For HTTPS traffic, the connection normally uses TCP over IP.</p><p>TCP establishes a reliable connection using a three-way handshake:</p><ol><li>The client sends a SYN packet to the server.</li><li>The server responds with SYN-ACK.</li><li>The client sends an ACK.</li></ol><p>Once the TCP connection is established, data can be exchanged reliably between the browser and the destination.</p><p>The IP protocol is responsible for addressing and routing packets across different networks, while TCP provides reliable delivery and ordering of the data.</p><h3>3. Firewall</h3><p>Before the request reaches the application infrastructure, network security mechanisms such as firewalls can inspect and filter traffic.</p><p>A firewall controls which network connections are allowed or blocked according to configured security rules.</p><p>For example, web servers commonly accept traffic on:</p><ul><li>Port 80 for HTTP</li><li>Port 443 for HTTPS</li></ul><p>A firewall can block unwanted traffic while allowing legitimate HTTPS requests to reach the appropriate infrastructure.</p><p>Google operates a large and complex network, so there are many layers of security and traffic filtering between the Internet and its internal systems.</p><h3>4. HTTPS and SSL/TLS</h3><p>Because the URL begins with https://, the browser must establish a secure HTTPS connection.</p><p>HTTPS uses TLS (Transport Layer Security) to encrypt communication between the browser and the server.</p><p>During the TLS handshake, the server presents a digital certificate. The browser verifies that the certificate is valid and that it corresponds to the requested domain.</p><p>The browser and server then agree on cryptographic parameters and establish encryption keys.</p><p>After this process, the HTTP request and response are encrypted. This helps protect sensitive information from being read or modified while it travels across the Internet.</p><p>Although people often say “SSL”, modern HTTPS uses TLS rather than the old SSL protocols.</p><h3>5. Load Balancer</h3><p>Google receives an enormous number of requests, so a single server cannot handle all of them.</p><p>A load-balancing system distributes incoming traffic across many servers and services.</p><p>When the request reaches Google’s infrastructure, the load balancer or related traffic-management systems can determine where the request should be sent.</p><p>Load balancing provides several important benefits:</p><ul><li>Distributes traffic across multiple servers</li><li>Prevents a single server from becoming overloaded</li><li>Improves availability</li><li>Allows infrastructure to scale</li><li>Helps route users to appropriate locations and services</li></ul><p>The user does not need to know which physical machine will process the request.</p><h3>6. Web Server</h3><p>After the request is routed through Google’s infrastructure, it eventually reaches a web-serving component.</p><p>The web server receives the HTTP request from the browser.</p><p>The request might look conceptually similar to:</p><pre>GET / HTTP/1.1<br>Host: www.google.com</pre><p>The web-serving layer determines how the request should be handled.</p><p>For simple static resources, a web server may be able to return the content directly. For more complex requests, it can forward the request to an application server or another internal service.</p><p>The response eventually travels back through the network to the browser.</p><h3>7. Application Server</h3><p>The application server is responsible for executing application logic.</p><p>For a large service such as Google, there are many application components working together rather than one simple application server.</p><p>The application logic can determine what content or services should be returned to the user.</p><p>For example, the application may:</p><ul><li>Process the user’s request</li><li>Determine what data is needed</li><li>Authenticate the user if necessary</li><li>Communicate with internal services</li><li>Query databases</li><li>Generate the response</li></ul><p>The application server may therefore communicate with several other backend services before the final response is produced.</p><h3>8. Database</h3><p>Some of the information needed to generate a response may be stored in databases or other storage systems.</p><p>The application can send queries to the appropriate data-storage systems, retrieve the required information, and use it to construct the response.</p><p>Large-scale services such as Google typically use distributed storage systems rather than relying on one database server.</p><p>The database layer may store information such as application data, configuration, indexes, or other information required by backend services.</p><p>Once the necessary data has been retrieved, the application produces a response.</p><h3>9. The Response Returns to the Browser</h3><p>After the server-side processing is complete, Google’s infrastructure sends an HTTP response back to the browser.</p><p>The response is encrypted because the connection uses HTTPS.</p><p>The data travels through the Internet using IP packets. TCP ensures reliable delivery, while TLS keeps the communication encrypted.</p><p>The browser receives the response and begins processing it.</p><p>The response may contain HTML, CSS, JavaScript, images, fonts, and other resources.</p><h3>10. The Browser Renders the Page</h3><p>Finally, the browser processes the received resources.</p><p>It parses the HTML and builds the DOM (Document Object Model). It processes CSS to determine the appearance of elements and executes JavaScript when necessary.</p><p>The browser may also make additional HTTP requests for resources such as images, stylesheets, JavaScript files, and fonts.</p><p>After processing everything required, the browser renders the page on the screen.</p><p>All of these steps happen extremely quickly.</p><h3>Conclusion</h3><p>Typing https://www.google.com and pressing Enter looks like a simple action, but it starts a complex chain of events.</p><p>In simplified form, the process looks like this:</p><pre>Browser<br>   |<br>   v<br>DNS<br>   |<br>   v<br>IP Address<br>   |<br>   v<br>TCP/IP Connection<br>   |<br>   v<br>Firewall / Network Security<br>   |<br>   v<br>HTTPS / TLS<br>   |<br>   v<br>Load Balancer<br>   |<br>   v<br>Web Server<br>   |<br>   v<br>Application Server<br>   |<br>   v<br>Database / Other Services<br>   |<br>   v<br>HTTP Response<br>   |<br>   v<br>Browser<br>   |<br>   v<br>Rendered Web Page</pre><p>Understanding this process is important for software engineers because it shows how different parts of the web stack work together. A single URL entered into a browser can involve DNS, networking, security, load balancing, servers, applications, databases, and finally the browser’s rendering engine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95f69f5efc2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Python Mutable and Immutable Objects — Explained Simply]]></title>
            <link>https://medium.com/@hsnislam2026/python-mutable-and-immutable-objects-explained-simply-e640cfaefaef?source=rss-6d64d3d411d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e640cfaefaef</guid>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Islam]]></dc:creator>
            <pubDate>Sat, 23 May 2026 15:12:45 GMT</pubDate>
            <atom:updated>2026-05-23T15:12:45.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5VHmR30Si1PbJ4Pw" /></figure><p>When beginners start learning Python, variables seem very simple.<br>You write:</p><pre>x = 5</pre><p>and it feels like the number 5 is stored inside the variable x.</p><p>But Python actually works very differently.</p><p>One of the biggest discoveries for new Python developers is understanding that:</p><blockquote><em>variables do not store values directly — they reference objects in memory.</em></blockquote><p>This single idea explains many confusing Python behaviors, especially with lists, dictionaries, and functions.</p><h3>Everything in Python Is an Object</h3><p>In Python, almost everything is treated as an object:</p><ul><li>numbers</li><li>strings</li><li>lists</li><li>dictionaries</li><li>functions</li><li>even classes themselves</li></ul><p>For example:</p><pre>x = 10</pre><p>Python does not create a “box” called x.</p><p>Instead:</p><ol><li>Python creates an integer object 10</li><li>the variable x becomes a reference to that object</li></ol><p>Conceptually:</p><pre>x ───► 10</pre><p>This is why Python has the id() function.</p><pre>x = 10</pre><pre>print(id(x))</pre><p>The id() function returns the identity of the object in memory.</p><h3>Mutable Objects</h3><p>Some objects in Python can change after creation.</p><p>These are called <strong>mutable objects</strong>.</p><p>Examples include:</p><ul><li>lists</li><li>dictionaries</li><li>sets</li></ul><p>Consider this example:</p><pre>numbers = [1, 2, 3]</pre><pre>print(id(numbers))</pre><pre>numbers.append(4)</pre><pre>print(numbers)<br>print(id(numbers))</pre><p>Output:</p><pre>[1, 2, 3, 4]</pre><p>The important detail is that the id remains the same.</p><p>Why?</p><p>Because Python modified the existing list object instead of creating a new one.</p><p>The object itself changed.</p><h3>Immutable Objects</h3><p>Other objects cannot be modified after they are created.</p><p>These are called <strong>immutable objects</strong>.</p><p>Examples:</p><ul><li>integers</li><li>floats</li><li>strings</li><li>tuples</li></ul><p>Now look at this:</p><pre>x = 5</pre><pre>print(id(x))</pre><pre>x = x + 1</pre><pre>print(id(x))</pre><p>At first glance, it looks like the number changed from 5 to 6.</p><p>But internally, Python created a completely new object.</p><p>The original object 5 still exists in memory, and x now points to a different object.</p><p>Conceptually:</p><p>Before:</p><pre>x ───► 5</pre><p>After:</p><pre>x ───► 6</pre><p>This is why immutable objects always produce new objects when modified.</p><h3>Why Mutability Matters</h3><p>Understanding mutability is critical because it affects how variables behave.</p><p>One of the most common beginner mistakes is this:</p><pre>a = [1, 2, 3]<br>b = a</pre><pre>b.append(4)</pre><pre>print(a)</pre><p>Output:</p><pre>[1, 2, 3, 4]</pre><p>Many beginners expect a to stay unchanged.</p><p>But both variables reference the same list object.</p><p>Conceptually:</p><pre>a ──┐<br>    ├──► [1, 2, 3]<br>b ──┘</pre><p>When b changes the list, a sees the same modification.</p><p>This behavior is extremely important when working with lists and dictionaries.</p><h3>Immutable Objects Behave Differently</h3><p>Now compare that behavior with integers:</p><pre>a = 5<br>b = a</pre><pre>b = b + 1</pre><pre>print(a)<br>print(b)</pre><p>Output:</p><pre>5<br>6</pre><p>Why did a stay the same?</p><p>Because integers are immutable.</p><p>Python could not modify the integer object 5, so it created a new object 6.</p><p>Now the variables point to different objects.</p><h3>Function Arguments and Object References</h3><p>One of the hardest Python concepts for beginners is how functions receive arguments.</p><p>Python passes references to objects.</p><p>This becomes very important with mutable objects.</p><p>Example with integers:</p><pre>def increment(number):<br>    number += 1</pre><pre>x = 5</pre><pre>increment(x)</pre><pre>print(x)</pre><p>Output:</p><pre>5</pre><p>The original integer does not change because integers are immutable.</p><p>Now compare with a list:</p><pre>def add_item(items):<br>    items.append(4)</pre><pre>numbers = [1, 2, 3]</pre><pre>add_item(numbers)</pre><pre>print(numbers)</pre><p>Output:</p><pre>[1, 2, 3, 4]</pre><p>The original list changes because the function modifies the same object in memory.</p><h3>The Dangerous Mutable Default Argument</h3><p>One famous Python problem comes from mutable default arguments.</p><p>Example:</p><pre>def add(value, my_list=[]):<br>    my_list.append(value)<br>    return my_list</pre><pre>print(add(1))<br>print(add(2))</pre><p>Output:</p><pre>[1]<br>[1, 2]</pre><p>Many people expect the second result to be [2].</p><p>But the same list object is reused between function calls.</p><p>The correct approach is:</p><pre>def add(value, my_list=None):<br>    if my_list is None:<br>        my_list = []</pre><pre>    my_list.append(value)<br>    return my_list</pre><p>This creates a fresh list every time.</p><h3>What This Topic Really Teaches</h3><p>The mutable vs immutable topic is not only about lists and integers.</p><p>It teaches how Python itself works internally.</p><p>The most important realization is:</p><blockquote><em>variables are labels pointing to objects in memory.</em></blockquote><p>Once you truly understand this idea:</p><ul><li>references become easier</li><li>bugs become easier to debug</li><li>function behavior makes sense</li><li>copying objects becomes clearer</li></ul><p>This topic is often the moment when beginners stop “memorizing Python” and start actually understanding it.</p><h3>Conclusion</h3><p>Mutable and immutable objects are one of the foundations of Python programming.</p><p>Mutable objects can change in place.<br>Immutable objects cannot be modified and require new objects to be created.</p><p>Understanding the difference helps explain:</p><ul><li>variable behavior</li><li>memory management</li><li>function arguments</li><li>object identity</li><li>common bugs with lists and dictionaries</li></ul><p>At first this topic feels abstract, but once you start thinking in terms of references and objects, Python becomes much more logical and predictable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e640cfaefaef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>