<?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 Muhammad Iqbal on Medium]]></title>
        <description><![CDATA[Stories by Muhammad Iqbal on Medium]]></description>
        <link>https://medium.com/@muhammadiqbal_41775?source=rss-f7cb01e51a3a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bjiuMYU7pBLlaNMJ.</url>
            <title>Stories by Muhammad Iqbal on Medium</title>
            <link>https://medium.com/@muhammadiqbal_41775?source=rss-f7cb01e51a3a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:46:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muhammadiqbal_41775/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[Decoding the Web: The Developer’s Guide to URL Encoding (and Why Privacy Matters)]]></title>
            <link>https://medium.com/@muhammadiqbal_41775/decoding-the-web-the-developers-guide-to-url-encoding-and-why-privacy-matters-f5bfef470c85?source=rss-f7cb01e51a3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5bfef470c85</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Muhammad Iqbal]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 16:14:35 GMT</pubDate>
            <atom:updated>2026-10-26T16:15:11.902Z</atom:updated>
            <content:encoded><![CDATA[<p>Every time you share a link containing a space, an emoji, or a complex query string, a silent translation happens behind the scenes. The web runs on a strict set of rules, and URLs are incredibly picky about the characters they accept.</p><p>If you’ve ever looked at a web address and seen a jumble of %20, %3F, or %3D, you’ve witnessed URL encoding in action.</p><p>While it might seem like a dry, invisible mechanic of the internet, understanding how to properly encode and decode URLs is essential for web developers, SEO specialists, and digital marketers. Let’s demystify how this process works, the technical pitfalls to avoid, and the best tools to keep your data secure.</p><h3>What is URL Encoding?</h3><p>At its core, URL encoding (officially known as percent-encoding) is a mechanism for translating characters that are either unprintable or hold special meaning in a URL into a universally accepted format.</p><p>The internet’s fundamental protocols were built around the US-ASCII character set. URLs can only be sent over the internet using this specific set of characters. If a URL contains characters outside of this set—like spaces, foreign language characters, or reserved characters (like ?, &amp;, #, or /)—they must be converted.</p><p>The process is simple: the problematic character is replaced by a % followed by its two-digit hexadecimal equivalent.</p><p>A space becomes %20 (or sometimes a +).</p><p>An ampersand &amp; becomes %26.</p><p>A comma , becomes %2C.</p><p>Various Ways to Encode and Decode</p><p>Depending on your workflow, there are several ways to handle URL encoding.</p><pre>1. Programming Languages (The Automated Way) If you are building a web application, you should never encode URLs manually. Every modern programming language has built-in functions to handle this:</pre><p>JavaScript: encodeURIComponent(&quot;hello world&quot;) securely encodes query parameters, while decodeURIComponent() reverses it.</p><p>PHP: urlencode() and urldecode() are standard for preparing strings to be used in a query part of a URL.</p><p>Python: The urllib.parse module provides quote() and unquote() for seamless translation.</p><p>2. The Command Line For developers living in the terminal, tools like curl or simple bash scripts can quickly encode payloads before firing off API requests.</p><p>3. Online Web Tools When you just need to quickly decode a messy UTM parameter or encode a webhook payload, spinning up a code editor is overkill. This is where browser-based URL encoder/decoder tools come into play, offering instant conversions via a simple user interface.</p><p>Benefits and Limitations</p><p>The Benefits:</p><p>Data Integrity: Encoding ensures that data sent via GET requests arrives exactly as intended, without the browser confusing a piece of data for a command.</p><p>Cross-Platform Compatibility: It guarantees that a link generated on a Windows machine in Japan works flawlessly on an iPhone in Canada.</p><p>Security Guardrails: Proper encoding helps prevent basic injection attacks where malicious users might try to break a URL structure to manipulate application logic.</p><p>The Limitations:</p><p>Readability: Highly encoded URLs are incredibly ugly. A beautifully crafted, SEO-friendly slug can quickly become an unreadable block of percentages and numbers, which can deter users from clicking.</p><p>Payload Bloat: Because one character can turn into three (e.g., a space to %20), heavy encoding can inflate the size of your URL. While modern browsers support very long URLs, older systems or specific servers still enforce length limits (often around 2,000 characters).</p><p>The Technical Trap: Double Encoding</p><p>The most common technical issue developers face is double encoding.</p><p>This happens when a system receives a URL that is already encoded and mistakenly encodes it again. Your standard space (%20) gets its percent sign encoded (which is %25), turning the space into %2520. When the receiving server decodes it once, it’s left with %20 instead of a space, breaking the application logic or resulting in a dreaded 404 error. Fixing this requires meticulous tracking of where data is sanitized in your application pipeline.</p><p>The Privacy Factor: Choosing the Right Online Tool</p><p>While there is no shortage of free online URL encoders, developers often overlook a massive security flaw: pasting sensitive data into random web forms.</p><p>When you decode an authorization token, a private API key, or customer data using a generic online tool, you have no idea if that server is logging your keystrokes or saving your query strings.</p><p>This is why I rely on the AABI Tech URL Encoder &amp; Decoder.</p><p>When distinguishing between the sea of available developer utilities, AABI Tech stands out for three specific reasons:</p><p>Uncompromising Privacy: It is a browser-based developer utility. The encoding and decoding happen entirely client-side, meaning your sensitive query strings and API keys never leave your machine or touch a remote server.</p><p>Ironclad Security: By eliminating server-side processing for this utility, it removes the risk of your proprietary data being logged, intercepted, or leaked.</p><p>Pinpoint Accuracy: It handles complex, multi-layered data perfectly without the glitchy character misinterpretations common in lower-quality tools.</p><p>Whether you are debugging a complex REST API payload or just trying to make a messy affiliate link readable, understanding the mechanics of URL encoding is a fundamental web skill. Equip yourself with the right knowledge, watch out for double-encoding traps, and always use secure, browser-level tools like AABI Tech to keep your data private.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5bfef470c85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[STOP WRITING PYDANTIC MODELS BY HAND]]></title>
            <link>https://medium.com/@muhammadiqbal_41775/stop-writing-pydantic-models-by-hand-2d9e75ec7f44?source=rss-f7cb01e51a3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d9e75ec7f44</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Muhammad Iqbal]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 16:11:36 GMT</pubDate>
            <atom:updated>2026-10-26T16:13:22.367Z</atom:updated>
            <content:encoded><![CDATA[<p>A free browser tool turns raw JSON into typed Python models, and the five things you still need to check afterward<br>You&#39;ve just been handed a new API. The docs are thin, so you call the endpoint and get back 200 lines of nested JSON. Now you need Pydantic models for it.<br>So you start typing. class Address(BaseModel). Then class Customer(BaseModel). Then you scroll back up to check whether phone was a string or an int.<br>It&#39;s not hard work. It&#39;s just slow, repetitive work that a computer can do in a second. That&#39;s why I started using the JSON to Pydantic Converter from AabiTech.<br>HOW IT WORKS<br>Paste your JSON (or upload a file up to 5 MB) and you get Python model code back.<br>Take this input:<br>{<br> &quot;name&quot;: &quot;Ayesha&quot;,<br> &quot;age&quot;: 25,<br> &quot;active&quot;: true<br>}<br>You get:<br>from pydantic import BaseModel</p><p>class User(BaseModel):<br> name: str<br> age: int<br> active: bool<br>With a real payload, nested objects become separate classes and arrays of objects become lists of models. You can choose Pydantic v1 or v2 mode, set the root model name, pick 2, 4, or 8 space indentation, and then copy the code or download it as a .py file. According to the page, your JSON is processed in the browser, and there&#39;s no signup.<br>WHERE IT EARNS ITS PLACE<br>Prototyping FastAPI endpoints. Take a sample request body, generate the model, and drop it into your route. You get validation and OpenAPI docs almost immediately.<br>Wrapping third-party APIs. Paste a real response and start from a working draft instead of a blank file.<br>Typing config files. A typed model turns a silent typo into a loud error.<br>THE PART MOST TOOLS DON&#39;T TELL YOU<br>A model generated from one JSON sample is a guess. It&#39;s a good guess, but a guess. Here is what a single example can&#39;t tell you:<br>Optional versus nullable. These are different things:<br>a: str | None (required, but can be None)<br>b: str | None = None (can be missing, can be None)<br>If your sample has &quot;b&quot;: null, you can&#39;t know whether b is ever absent.<br>Mixed types. If id is an integer in some records and a string in others, you&#39;ll need int | str or a validator.<br>Key names. Keys like firstName or user-id need Python-friendly names plus an alias:<br>first_name: str = Field(alias=&quot;firstName&quot;)<br>Empty arrays. An empty list gives nothing to infer an item type from.<br>Constraints. No sample will tell you about minimum lengths, patterns, enums, or ranges. That part is yours.<br>MY WORKFLOW<br>Use the most complete record you have as the sample.<br>Generate the model in the right Pydantic version.<br>Fix optionals, unions, and aliases.<br>Add validators and constraints.<br>Test with valid and invalid payloads.<br>This way the tool handles the repetitive 80%, and your attention goes to the 20% that actually matters for correctness.<br>One last habit: even though the conversion runs in your browser, keep tokens and real customer data out of any sample you paste into an online tool.<br>TRY IT<br>The tool is free: <a href="https://aabitech.com/tools/json-to-pydantic-converter">https://aabitech.com/tools/json-to-pydantic-converter</a><br>If you work with APIs in Python, I&#39;d like to hear how you handle messy responses. Leave a comment with your approach.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d9e75ec7f44" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>