<?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 Anokithen on Medium]]></title>
        <description><![CDATA[Stories by Anokithen on Medium]]></description>
        <link>https://medium.com/@anokithen?source=rss-0ed5699e0b04------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gRKAq8Dr_z0JVIzGzc9z0Q.png</url>
            <title>Stories by Anokithen on Medium</title>
            <link>https://medium.com/@anokithen?source=rss-0ed5699e0b04------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:21:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anokithen/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[JWT Authentication Explained]]></title>
            <link>https://medium.com/@anokithen/jwt-authentication-explained-49f7f6fa33fe?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/49f7f6fa33fe</guid>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 04:08:39 GMT</pubDate>
            <atom:updated>2026-07-13T04:08:39.261Z</atom:updated>
            <content:encoded><![CDATA[<p>Demystifying JWT Authentication: The Stateless Guardian</p><p>In the world of modern web development, managing user sessions without slowing down your servers is crucial. Enter JSON Web Tokens, or JWTs, a compact and secure way to transmit identity information. Unlike traditional session-based authentication, which requires the server to store session data in a database or memory, JWTs are stateless. This means the server doesn’t need to remember who you are; it only needs to verify the token you present.</p><p>Think of a JWT like a concert wristband. When you buy a ticket (log in), the venue (server) issues a wristband with specific details printed on it, such as your seating section and the event duration. Once you have the wristband, you can walk in and out of different areas without stopping at the ticket booth every time. The security guard (server) simply checks the wristband to ensure it is authentic and hasn’t been tampered with. If the signature matches, you are in.</p><p>A JWT consists of three parts: a header, a payload, and a signature. The payload holds your user data, while the signature ensures no one has altered the information. Because the server trusts its own signature, it can quickly validate requests from anywhere, making JWTs perfect for mobile apps, microservices, and single-page applications. This approach reduces database load and improves scalability, allowing your application to handle millions of users without breaking a sweat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49f7f6fa33fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Database Relationships with Real-Life Examples.]]></title>
            <link>https://medium.com/@anokithen/database-relationships-with-real-life-examples-396a8f55e54a?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/396a8f55e54a</guid>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 04:04:22 GMT</pubDate>
            <atom:updated>2026-07-13T04:04:22.413Z</atom:updated>
            <content:encoded><![CDATA[<p>Understanding Database Relationships Through Real-Life Examples</p><p>Database relationships are the invisible threads that connect data across tables, turning scattered information into a coherent story. Without them, a database is just a collection of unrelated lists. Here is how they work in the real world.</p><p>Think of a library. The “Books” table lists every title, while the “Authors” table holds writer details. A single author writes many books, creating a one-to-many relationship. Instead of repeating the author’s name in every book record, we simply store an Author ID in the Books table. This keeps data clean and prevents errors.</p><p>Consider a school system. A “Students” table and a “Classes” table share a many-to-many relationship. One student takes multiple classes, and one class has many students. To manage this, we create a middle “Enrollment” table. It links Student IDs to Class IDs, tracking exactly who is in which room without duplicating massive lists.</p><p>Finally, imagine an online store. Each “Order” belongs to one specific “Customer,” but a customer can place many orders. This one-to-many link ensures that if a customer updates their address, we don’t have to fix it in thousands of order records. We just update the single customer profile.</p><p>Mastering these relationships is the key to building efficient, scalable systems that mirror the complexity of real life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=396a8f55e54a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Clean Code Matters in Software Development]]></title>
            <link>https://medium.com/@anokithen/why-clean-code-matters-in-software-development-2db9b45de7f4?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/2db9b45de7f4</guid>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 04:20:28 GMT</pubDate>
            <atom:updated>2026-06-16T04:20:28.949Z</atom:updated>
            <content:encoded><![CDATA[<p>Writing code that works is the minimum bar. Writing code that others can read, understand, and build on — that is the real craft. Clean code is not about aesthetics or perfectionism. It is a practical discipline that determines how long a codebase stays alive and how quickly a team can move inside it.</p><h3>Readability is a team sport</h3><p>Most code gets read far more often than it gets written. A function you draft in an afternoon might be opened, skimmed, and debugged by a dozen people over the next few years — including a future version of yourself who has completely forgotten the original context. Clear variable names, small focused functions, and consistent structure are not luxuries. They are how teams communicate across time.</p><p><em>“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”</em></p><h3>The real cost of messy code</h3><p>Technical debt compounds quietly. A shortcut taken under deadline pressure becomes a workaround that five other features depend on. Messy code slows every new feature because developers spend their time deciphering what already exists rather than building what comes next. Studies consistently show that maintenance consumes the majority of a software project’s total lifetime cost. Clean code directly reduces that burden.</p><h3>Clean code is a professional standard</h3><p>Teams that prioritise clean code ship fewer bugs, onboard new developers faster, and spend less time in emergency fixes. It signals that the people writing the software care about the people who will inherit it. In an industry where requirements shift constantly and teams grow and shrink, that care is what keeps a codebase from becoming a liability.</p><p>Clean code is not slow code. It is sustainable code — and sustainable code is how good software gets built.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2db9b45de7f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile vs Waterfall: Which Development Method Works Better?]]></title>
            <link>https://medium.com/@anokithen/agile-vs-waterfall-which-development-method-works-better-c71262c8bd9e?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/c71262c8bd9e</guid>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 04:16:43 GMT</pubDate>
            <atom:updated>2026-06-16T04:16:43.663Z</atom:updated>
            <content:encoded><![CDATA[<p>Every software project starts with a question nobody answers out loud: how are we actually going to run this thing? Two methodologies have dominated that conversation for decades — Waterfall and Agile. Choosing between them shapes how teams communicate, how quickly products ship, and how gracefully they handle the inevitable surprises.</p><h3>The case for waterfall</h3><p>Waterfall moves in straight lines. Requirements come first, then design, then development, then testing, then release. Each phase closes before the next opens. This structure appeals to projects where the scope is fixed and well-understood — government contracts, regulated industries, or large infrastructure builds where changing direction mid-flight is genuinely dangerous or expensive.</p><p>The discipline it demands is also its strength. Detailed documentation, clear handoffs, and predictable timelines make Waterfall easy to budget and easy to audit. When every stakeholder needs to sign off before work begins, that front-loaded clarity is a feature, not a flaw.</p><p><em>“The right method isn’t the fastest one — it’s the one that matches how your requirements actually behave.”</em></p><h3>The case for agile</h3><p>Agile was written in direct response to Waterfall’s rigidity. It breaks work into short cycles — usually two-week sprints — and revisits priorities constantly. Feedback loops are tight. Shipping something small and real beats delivering something perfect and late.</p><p>For most modern product teams, this rhythm fits better. Customer needs shift. Markets move. A requirement that made perfect sense in January can be obsolete by March. Agile doesn’t panic when that happens; it adapts.</p><h3>So which one wins?</h3><p>Neither, on its own, always wins. Waterfall earns its place when requirements are stable and the cost of late changes is high. Agile earns its place when discovery is ongoing and speed-to-feedback matters more than upfront precision.</p><p>The teams that deliver the best software tend to be the ones who understand both methods well enough to borrow from each — and honest enough to match their process to the actual shape of their project, not the shape they wish it had.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c71262c8bd9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[REST vs GraphQL: Understanding Modern APIs]]></title>
            <link>https://medium.com/@anokithen/rest-vs-graphql-understanding-modern-apis-dd6bce887dba?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd6bce887dba</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 02:45:01 GMT</pubDate>
            <atom:updated>2026-06-08T02:45:01.283Z</atom:updated>
            <content:encoded><![CDATA[<p>APIs are an essential part of modern software development. They allow different applications to communicate and exchange data. Whether you are using a mobile app, a website, or a cloud service, APIs work behind the scenes to make everything function smoothly. Two of the most popular API technologies today are REST and GraphQL. Both help applications access and manage data, but they do so in different ways.</p><p>Understanding the differences between REST and GraphQL can help developers choose the right approach for their projects.</p><h4>What is REST?</h4><p>REST, which stands for Representational State Transfer, is an architectural style for building web APIs. It has been the industry standard for many years and is widely used in web and mobile applications.</p><p>In REST, data is accessed through different endpoints. Each endpoint represents a specific resource, such as users, products, or orders. Clients send HTTP requests like GET, POST, PUT, or DELETE to interact with these resources.</p><h4>Advantages of REST</h4><p>- Simple and easy to understand.<br>- Uses standard HTTP methods.<br>- Well-documented and widely supported.<br>- Easy to implement and maintain.<br>- Works well for most traditional applications.</p><h4>Limitations of REST</h4><p>- Multiple requests may be needed to fetch related data.<br>- Sometimes returns more data than required.<br>- Managing many endpoints can become complex in large applications.</p><h4>What is GraphQL?</h4><p>GraphQL is a query language and runtime for APIs developed by Facebook. It was designed to solve some of the limitations of REST by giving clients more control over the data they receive.</p><p>Instead of accessing multiple endpoints, GraphQL usually uses a single endpoint. Clients can request exactly the data they need, and the server responds with only that information.</p><p>For example, if an application only needs a user&#39;s name and email, GraphQL can return just those fields instead of the entire user record.</p><h4>Advantages of GraphQL</h4><p>- Fetches only the required data.<br>- Reduces the number of API requests.<br>- Uses a single endpoint for data access.<br>- Improves performance in data-heavy applications.<br>- Provides flexibility for frontend developers.</p><h4>Limitations of GraphQL</h4><p>- More complex to set up and manage.<br>- Queries can become difficult to optimize.<br>- Caching is often more challenging compared to REST.<br>- Requires additional learning for new developers.</p><h4>Key Differences Between REST and GraphQL</h4><p>REST organizes data through multiple endpoints, while GraphQL typically uses a single endpoint. In REST, the server decides the structure of the response. In GraphQL, the client decides what data should be returned.</p><p>REST is generally easier for beginners and works well for straightforward applications. GraphQL provides greater flexibility and efficiency, especially when applications need data from multiple sources.</p><p>Another important difference is data fetching. REST may sometimes return too much or too little information, requiring additional requests. GraphQL helps solve this issue by allowing clients to request exactly what they need.</p><h4>When Should You Choose REST?</h4><p>REST is a great choice when:</p><p>- Building simple or medium-sized applications.<br>- Working with a team familiar with REST principles.<br>- Fast development is a priority.<br>- Strong caching support is needed.<br>- The data structure is relatively stable.</p><h4>When Should You Choose GraphQL?</h4><p>GraphQL is a good option when:</p><p>- Applications require complex data relationships.<br>- Multiple frontend platforms consume the same API.<br>- Reducing network requests is important.<br>- The project needs flexible data retrieval.<br>- Mobile application performance is a priority.</p><h3>Conclusion</h3><p>Both REST and GraphQL are powerful technologies for building modern APIs. REST remains popular because of its simplicity, reliability, and widespread adoption. GraphQL offers greater flexibility by allowing clients to request exactly the data they need.</p><p>The best choice depends on your project&#39;s requirements. For many applications, REST provides everything needed with minimal complexity. For larger and more dynamic applications, GraphQL can improve efficiency and developer experience. By understanding the strengths and weaknesses of both approaches, developers can build APIs that are scalable, efficient, and easy to maintain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd6bce887dba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SQL vs NoSQL: Choosing the Right Database]]></title>
            <link>https://medium.com/@anokithen/sql-vs-nosql-choosing-the-right-database-e7b48a8066fb?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7b48a8066fb</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[nosql]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 02:39:40 GMT</pubDate>
            <atom:updated>2026-06-08T02:39:40.697Z</atom:updated>
            <content:encoded><![CDATA[<p>Databases play a crucial role in modern software development. They help store, manage, and retrieve data efficiently. When building an application, one of the most important decisions is choosing the right database. Two of the most popular database types are SQL and NoSQL. While both are designed to store data, they work differently and are suited for different situations.</p><h4>What is SQL?</h4><p>SQL stands for Structured Query Language. SQL databases store data in tables made up of rows and columns. These databases follow a predefined structure called a schema, which means the format of the data is decided before information is stored.</p><p>Some popular SQL databases include MySQL, PostgreSQL, Microsoft SQL Server, and Oracle Database.</p><p>SQL databases are known for their reliability and consistency. They are commonly used in applications where data accuracy is critical, such as banking systems, e-commerce platforms, and inventory management systems.</p><h4>Benefits of SQL</h4><p>- Stores data in a structured and organized way.<br>- Provides strong data consistency and integrity.<br>- Supports complex queries and transactions.<br>- Has extensive documentation and community support.<br>- Ideal for applications that require accurate and reliable data.</p><h4>Challenges of SQL</h4><p>- Schema changes can be difficult when requirements change frequently.<br>- Scaling large applications may require more planning.<br>- Less flexible when handling unstructured data.</p><h4>What is NoSQL?</h4><p>NoSQL stands for &quot;Not Only SQL.&quot; Unlike SQL databases, NoSQL databases do not require a fixed schema. They can store data in multiple formats, such as documents, key-value pairs, graphs, or columns.</p><p>Popular NoSQL databases include MongoDB, Cassandra, Redis, and CouchDB.</p><p>NoSQL databases were created to handle large amounts of data and support applications that need high scalability and flexibility. They are widely used in social media platforms, real-time applications, and big data systems.</p><h4>Benefits of NoSQL</h4><p>- Flexible data structure that can adapt to changing requirements.<br>- Easy to scale across multiple servers.<br>- Performs well with large volumes of data.<br>- Suitable for unstructured and semi-structured data.<br>- Supports modern cloud-based applications effectively.</p><h4>Challenges of NoSQL</h4><p>- Data consistency may not be as strict as SQL databases.<br>- Managing complex relationships can be more difficult.<br>- Different databases may use different query methods.</p><h4>Key Differences Between SQL and NoSQL</h4><p>The main difference between SQL and NoSQL is how they store and manage data. SQL databases use tables and predefined schemas, making them ideal for structured data. NoSQL databases offer flexible structures, making them suitable for rapidly changing and large-scale applications.</p><p>SQL focuses on data consistency and reliability, while NoSQL focuses on scalability and flexibility. SQL databases are often preferred for traditional business applications, whereas NoSQL databases are commonly used for modern web and mobile applications that handle large amounts of diverse data.</p><h4>When Should You Choose SQL?</h4><p>You should consider SQL when:</p><p>- Your application requires strong data accuracy.<br>- Transactions are important.<br>- The data structure is unlikely to change frequently.<br>- You need complex queries and relationships between data.</p><p>When Should You Choose NoSQL?</p><p>You should consider NoSQL when:</p><p>- Your application needs to handle massive amounts of data.<br>- The data structure changes regularly.<br>- Scalability is a major requirement.<br>- You are working with real-time or cloud-based applications.</p><h3>Conclusion</h3><p>Both SQL and NoSQL databases are powerful technologies, and neither is universally better than the other. The best choice depends on your project&#39;s requirements. SQL is an excellent option for applications that require structured data, strong consistency, and reliable transactions. NoSQL is a great choice for applications that need flexibility, scalability, and the ability to handle large volumes of diverse data.</p><p>By understanding the strengths and limitations of both database types, developers can make informed decisions and build applications that perform efficiently and grow successfully over time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7b48a8066fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to APIs and How They Work]]></title>
            <link>https://medium.com/@anokithen/introduction-to-apis-and-how-they-work-074d13427eb8?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/074d13427eb8</guid>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Sun, 31 May 2026 17:42:53 GMT</pubDate>
            <atom:updated>2026-05-31T17:42:53.171Z</atom:updated>
            <content:encoded><![CDATA[<p>Every time you check the weather on your phone, log in with Google, or pay through an app, something invisible is working behind the scenes — an API.</p><p>API stands for Application Programming Interface. In simple terms, it’s a set of rules that allows two software applications to talk to each other. Think of it like a waiter at a restaurant. You don’t walk into the kitchen and cook your own meal. Instead, you tell the waiter what you want, the waiter carries that request to the kitchen, and then brings back what you ordered. The waiter is the API — the middleman that handles communication between you and the system doing the actual work.</p><h3>How APIs Actually Work</h3><p>When you use an app that pulls data from somewhere — say, a travel site showing live flight prices — your app sends a <strong>request</strong> to an airline’s API. That request includes details like the destination, dates, and number of passengers. The API receives it, fetches the relevant data from the airline’s database, and sends back a <strong>response</strong> — usually in a format called JSON, which apps can easily read and display.</p><p>This request-response cycle happens in milliseconds, and most of the time users never notice it.</p><h3>Why APIs Matter</h3><p>APIs allow developers to build faster by reusing existing services rather than building everything from scratch. A startup can integrate payments via Stripe, maps via Google, and messaging via Twilio — all without owning any of that infrastructure.</p><p>They also keep systems secure. Instead of giving direct access to a database, APIs act as a controlled gateway, exposing only what’s necessary.</p><p>In short, APIs are the invisible plumbing of the modern internet — quietly powering nearly everything we use online.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=074d13427eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Generative AI vs Traditional AI: Key Differences]]></title>
            <link>https://medium.com/@anokithen/generative-ai-vs-traditional-ai-key-differences-8be6259854ed?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/8be6259854ed</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[traditional-ai]]></category>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Sun, 31 May 2026 17:41:26 GMT</pubDate>
            <atom:updated>2026-05-31T17:41:26.677Z</atom:updated>
            <content:encoded><![CDATA[<p>Artificial intelligence has been reshaping industries for decades, but not all AI is built the same. Understanding the distinction between traditional AI and generative AI is essential for anyone navigating today’s tech landscape.</p><h3>What Is Traditional AI?</h3><p>Traditional AI is designed to analyze data and make decisions based on predefined rules or learned patterns. It excels at specific, well-defined tasks — think spam filters, recommendation engines, or fraud detection systems. These models are trained to classify, predict, or optimize within a fixed scope. They answer the question: <em>what is the right output for this input?</em></p><h3>What Is Generative AI?</h3><p>Generative AI goes a step further. Rather than simply recognizing or categorizing, it creates — producing new text, images, code, audio, and more. Models like large language models (LLMs) learn the underlying structure of data so deeply that they can generate entirely new content that mirrors it. They answer the question: <em>what could a plausible new output look like?</em></p><h3>The Key Differences</h3><p>Traditional AI Generative AI <strong>Goal</strong> Predict or classify Create new content <strong>Output</strong> Labels, scores, decisions Text, images, code, audio <strong>Flexibility</strong> Narrow, task-specific Broad, open-ended <strong>Training</strong> Labeled datasets Massive unlabeled data</p><h3>Why It Matters</h3><p>Traditional AI remains the backbone of countless business systems — reliable, explainable, and efficient for structured tasks. Generative AI, meanwhile, is unlocking entirely new workflows: drafting content, writing software, and simulating conversations at scale.</p><p>The two aren’t competitors — they’re complements. The future of AI lies in knowing when to use each.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8be6259854ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Websites Load: From URL to Page Display….]]></title>
            <link>https://medium.com/@anokithen/how-websites-load-from-url-to-page-display-a8d82ef46899?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8d82ef46899</guid>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Tue, 26 May 2026 04:18:35 GMT</pubDate>
            <atom:updated>2026-05-26T04:18:35.416Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Websites Load: From URL to Page Display</h3><p>Every time you type a web address and hit Enter, a fascinating chain of events unfolds in milliseconds — most of which you never see.</p><h3>Step 1: DNS Lookup</h3><p>Your browser doesn’t understand human-readable addresses like <em>example.com</em>. It first contacts a <strong>Domain Name System (DNS)</strong> server, which acts like a phonebook, translating the domain name into a numerical IP address — something like <em>93.184.216.34</em>.</p><h3>Step 2: Establishing a Connection</h3><p>With the IP address in hand, your browser initiates a <strong>TCP handshake</strong> with the web server — a quick back-and-forth exchange to confirm both sides are ready to communicate. If the site uses HTTPS (which most do today), an additional <strong>TLS handshake</strong> happens to encrypt the connection.</p><h3>Step 3: Sending an HTTP Request</h3><p>Your browser sends an <strong>HTTP GET request</strong> to the server, essentially saying: <em>“Please send me the content at this address.”</em> The server processes this and responds with the HTML file for that page.</p><h3>Step 4: Parsing HTML</h3><p>The browser reads the HTML top to bottom, building a <strong>Document Object Model (DOM)</strong> — a structured map of all the page’s elements. As it encounters references to CSS files, JavaScript, images, and fonts, it fires off additional requests to fetch them.</p><h3>Step 5: Rendering the Page</h3><p>With styles applied and scripts executed, the browser performs <strong>layout</strong> (calculating where each element sits) and <strong>painting</strong> (drawing pixels to the screen). This is the moment the page becomes visible to you.</p><p>The entire process — from keystroke to fully loaded page — often completes in under a second. It’s one of the most quietly impressive feats of modern engineering happening dozens of times a day, right in your browser.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8d82ef46899" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frontend vs Backend Development…]]></title>
            <link>https://medium.com/@anokithen/frontend-vs-backend-development-bd2aeabc2864?source=rss-0ed5699e0b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd2aeabc2864</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Anokithen]]></dc:creator>
            <pubDate>Tue, 26 May 2026 03:40:38 GMT</pubDate>
            <atom:updated>2026-05-26T03:40:38.784Z</atom:updated>
            <content:encoded><![CDATA[<h3>Frontend vs Backend Development: What’s the Difference?</h3><p>When building a website or application, two worlds work silently together — frontend and backend development. Understanding the difference is key for anyone stepping into the tech industry.</p><h3>Frontend Development: What You See</h3><p>Frontend development is everything a user interacts with directly — buttons, layouts, colors, animations, and forms. Frontend developers work with <strong>HTML</strong>, <strong>CSS</strong>, and <strong>JavaScript</strong>, along with modern frameworks like React, Vue, or Angular.</p><p>Their goal is simple: make the experience beautiful, fast, and intuitive. If a website feels smooth and looks great, credit the frontend team.</p><h3>Backend Development: What Powers It</h3><p>Backend development is the engine under the hood. It handles databases, servers, authentication, APIs, and business logic — all the things users never see but constantly rely on. Backend developers work with languages like <strong>Python</strong>, <strong>Node.js</strong>, <strong>Java</strong>, or <strong>PHP</strong>, paired with databases like PostgreSQL or MongoDB.</p><p>When you log into an app and your data appears instantly, that’s backend magic at work.</p><h3>Key Differences at a Glance</h3><p>Frontend Backend <strong>Focus</strong> User interface Server &amp; data <strong>Languages</strong> HTML, CSS, JS Python, Java, PHP <strong>Goal</strong> Visual experience Logic &amp; performance</p><h3>Which Should You Choose?</h3><p>If you love design and creativity, frontend is your playground. If you enjoy problem-solving, data, and systems thinking, backend might be your calling. Many developers eventually become <strong>full-stack</strong>, mastering both sides.</p><p>Ultimately, neither is superior — they’re two halves of the same coin, and great products need both done well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd2aeabc2864" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>