<?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 Fatima✨ on Medium]]></title>
        <description><![CDATA[Stories by Fatima✨ on Medium]]></description>
        <link>https://medium.com/@fatima02?source=rss-45010bb911c2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_yUBHNGtlt2iSVL1I8c_7A.png</url>
            <title>Stories by Fatima✨ on Medium</title>
            <link>https://medium.com/@fatima02?source=rss-45010bb911c2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:10:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fatima02/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[I packed a bag in the middle of the afternoon and then had nothing to do]]></title>
            <link>https://medium.com/@fatima02/i-packed-a-bag-in-the-middle-of-the-afternoon-and-then-had-nothing-to-do-df0080536fee?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/df0080536fee</guid>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[california]]></category>
            <category><![CDATA[morning-routines]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 08:41:58 GMT</pubDate>
            <atom:updated>2026-09-06T08:41:58.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EXXcG3x7mXAfhNAV" /></figure><p>The warning came on a weekday afternoon. I’d always assumed a thing like that would arrive at two in the morning, because that’s how it happens in everything I’d ever watched about it. Instead it was the middle of the day, and the light outside was completely normal, and I remember standing in the kitchen holding my phone and thinking: okay, so now what.</p><p>I own the house. That matters to how the rest of this went, so I’ll put it up front rather than let it sit under the story pretending not to be there. Southern California, and I’m not going anywhere, and I’ve had the argument with myself and lost it enough times to stop having it. So the question was never whether I was leaving the state. It was what I take to the car.</p><blockquote>Here’s what nobody prepares you for: you get about as much warning as you’d get for a dentist appointment, and then you have to decide what your life is.</blockquote><h3>The packing takes less time than you think, and then you have hours</h3><p>I did the obvious things first. Documents. The laptop, because of course the laptop. Chargers, which I then repacked twice because I’d grabbed the wrong ones. Medication. A change of clothes, which in hindsight was more clothes than anyone needs and I still don’t know why I did that.</p><p>And then I got to the part where you stand in a room and look at objects.</p><p>This is the bit I’d never seen described honestly. Every account of this I’d read before was either people who lost everything, or people who were fine, and both of those are stories with endings. The middle of it is a man in a hallway trying to work out whether a box of photographs is worth the trunk space, and failing to decide, and going to check the map again instead.</p><blockquote>I checked the map a lot. That was most of the afternoon, honestly — refreshing a page, reading the same information, putting the phone down, picking it up ninety seconds later to read it again. Nothing changed on it for long stretches.</blockquote><blockquote>The waiting is administrative. It’s not cinematic at all. There’s no music and nobody tells you anything and you are mostly just a guy in his own house with a bag by the door, feeling faintly stupid about the bag.</blockquote><p>I want to be careful here, because this is exactly the point where these essays start reaching for something bigger than what happened. I got a warning. I packed. I’m not going to dress that up into a survival story, and I’m not going to pretend I know what the people a few ridges over were going through at the same time, because I don’t. A warning is not a fire. It’s the state telling you it might become your problem, and you sitting with that for a while.</p><p>But it does something to you that lasts longer than the afternoon.</p><h3>The smoke week was later, and it was worse in a much duller way</h3><p>That came further into the year. And it was worse, which surprised me, because on paper it’s the lesser event by a distance. Nobody tells you to pack anything. There’s no warning to check. You just can’t go outside for a week.</p><p>The evacuation warning had adrenaline in it. There was a thing to do — badly, indecisively, but a thing. The smoke week had none of that. It was a week of closed windows and a sky the colour of a dirty dishcloth and the specific irritation of being told, correctly, that the healthiest available option was to stay indoors and do nothing about it.</p><p>I got snappish. I’d like to report that I handled it with some perspective, given that I was sitting in a house that was completely fine, but I mostly just got irritable and short with people who hadn’t done anything. That’s the honest version.</p><p>A week is a long time to be mildly angry at weather.</p><p>What got me was how ordinary everyone treated it. Which is fair enough. It’s an annual thing now, it’s priced into how people here plan a summer, and there’s a slightly grim competence to how Californians handle a smoke week that I both admire and find a bit alarming. We’ve all just absorbed it. It’s a season.</p><h3>What actually changed was how I read the news about it</h3><p>Here’s the turn, and it’s smaller than the setup probably suggested.</p><p>My homeowner’s insurance went up a lot this year. Not a non-renewal. I didn’t get dropped, I’m not on the FAIR Plan, and I want to say that clearly because those are the two stories the coverage is made of and neither of them is mine.</p><p>The premium went up by an amount that made me stop and read the paperwork properly, and then I paid it, and I stayed. That’s it. That’s the whole event.</p><p>And I’d have read that as boring a year ago.</p><p>The FAIR Plan — the state’s insurer of last resort, the one you end up on when the private market won’t have you — got an average 29.1% rate increase approved, effective October 15. KQED reported it in August: the plan asked for 35.8%, the Department of Insurance approved 29.1%, and it lands on more than 675,000 policyholders.</p><p>The number that actually stopped me was a different one in the same reporting. The plan’s total exposure was $768 billion as of June, up about 250% since September 2022.</p><blockquote>Two hundred and fifty percent in under four years. That’s not a fire statistic. That’s a market quietly moving a very large number of people from one column to another, one non-renewal at a time, and the fires are the reason it’s happening rather than the thing that’s happening.</blockquote><p>I read that now as somebody with a bag by the door in his memory. It reads different. Before this year I’d have processed “insurance market instability in California” as a phrase, in the way you process any phrase, and moved on to the next headline. Now there’s an afternoon attached to it.</p><p>That’s not insight, exactly. It’s just proximity. It didn’t make me smarter about insurance markets and I’d be lying if I said I came out of it with a position on what the state should do, because I genuinely don’t have one that survives ten minutes of argument.</p><p>Everyone’s proposal for fixing this seems to require somebody paying more, and the disagreement is mostly about who, and I notice that everybody’s answer is “not me” including mine.</p><h3>What I’d tell a neighbour</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fefQBkyHvoUjjvXj" /></figure><p>Pack earlier than you think you need to, because the packing is not the hard part and you want the hours back for the deciding.</p><p>Take the photographs. I still don’t know if I would have, and it bothers me.</p><p>And the thing I actually keep coming back to: I got the easy version. Twice. A warning and a bad week, in a state where a lot of people this year got considerably more than that, and I’ve still got a house and a policy and the same view out of the same window.</p><p>If that’s the light version and it stuck with me this much, I don’t think I have any real idea what the heavy version does to somebody.</p><blockquote>I’m not sure that’s a comfortable place to end up. But it’s where I am, and October 15 is coming, and a lot of people are about to open an envelope.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df0080536fee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My side income runs on a pun. Monday, Montenegro turned it off.]]></title>
            <link>https://medium.com/@fatima02/my-side-income-runs-on-a-pun-monday-montenegro-turned-it-off-8efaee8b6135?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8efaee8b6135</guid>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 13:22:51 GMT</pubDate>
            <atom:updated>2026-09-04T13:22:51.232Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PIQGdRSfI2ESQ0ke" /></figure><p>3:40 yesterday afternoon, my phone starts buzzing with the wrong kind of notifications. Not the good kind, where somebody subscribes. The kind where four people in a row paste me the same screenshot: “this link doesn’t work.”</p><p>The link is a t.me invite. My bot pings collectors when specific vinyl repress runs go live on three stores I’ve scraped politely for two years, $5 a month, 240-ish subscribers on a good month, enough to cover my actual rent some months and just my internet bill on others. I did not touch anything yesterday.</p><p>I checked. Twice, because the first time I didn’t believe myself.</p><blockquote>Turns out I hadn’t broken anything. Montenegro had.</blockquote><h3>The joke was always load-bearing</h3><p>Here’s the part that took me a minute to even find, because I’d genuinely never thought about it before Monday: t.me is Montenegro’s country code. Somebody at Telegram, years back, looked at “.me” and saw “tell me” and grabbed it, the same move as bit.ly running on Libya’s .ly or goo.gl squatting on Google’s own .gl. Cute. Free marketing baked into the URL bar. I’ve made the same joke myself picking domains for side projects, thought nothing of it, moved on.</p><p>What I didn’t clock is that a domain hack means your infrastructure has a government attached to it. Not metaphorically. Literally, there is a registry, in this case run technically by a US company called Identity Digital on Montenegro’s behalf, and on Monday that registry put t.me into something called serverHold. It’s a status flag registries use to kill a domain at the root, and once it’s set the domain stops resolving anywhere on the internet, full stop, no cache saves you.</p><h3>Telegram the app kept working.</h3><p>Messages sent, groups loaded, nothing crashed on the backend Telegram actually controls. But every single t.me link, every username, every channel, every invite, every “share this chat” button anyone has ever pasted into a bio or a README or, in my case, a Discord pinned message, just stopped resolving. WHOIS shows the change landing sometime July 13. As of this morning nobody’s said why.</p><p>Pavel Durov found out the same way I did, from people yelling at him. He posted at the registry directly on X: “Hey @domainME, t.me links stopped working. Can you look into it?”</p><p>He sounds like a guy checking his own phone screenshots, not like a CEO who got a courtesy call first.</p><h3>Nobody’s explaining anything, and that’s sort of the whole story</h3><p>No statement from Telegram. No statement from the .me registry. No statement from Identity Digital. Just a status flag, flipped by someone, for a reason that as of writing is anyone’s guess: legal dispute, regulatory compliance, policy enforcement, a plain technical screwup, or something nobody’s floated yet.</p><p>Hacker News has threads running most of those theories and nobody’s won yet. I refreshed one of them twice while writing this paragraph, which tells you something about my Tuesday.</p><blockquote>I’m not accusing anyone of anything, because I genuinely don’t know what happened.</blockquote><p>That’s not a hedge, it’s the actual news: a domain that a global messaging platform, and apparently my rent, depends on can go dark with zero warning, and there’s nobody you can even call about it. When the thing that breaks doesn’t have a support line, just a registry answering to nobody on your timeline, what exactly are you supposed to do?</p><blockquote>This isn’t the first time a ccTLD domain hack has scared people who should’ve been paying attention.</blockquote><p>Bit.ly registered a backup shortener, j.mp, back during the unrest in Libya in 2010 and 2011, specifically because .ly’s future got shaky enough that a company built entirely on a pun wanted an exit ramp.</p><p>More recently, the UK agreed to hand the Chagos Islands back to Mauritius, which means the British Indian Ocean Territory that .io is named after is going away as a recognized territory, which means every startup running on a .io domain is now downstream of a treaty they’ve never read, waiting to see if ICANN eventually retires the code the way it’s retired dead ccTLDs before.</p><p>I actually dodged that one, by accident more than wisdom. A friend talked me out of a .io domain for the actual product I’m building, years ago, something about “don’t put your company on land that might not exist in ten years,” and I remember thinking he was being dramatic. I bought the .com instead.</p><p>Felt a little smug about it Monday morning, honestly, right up until the exact same category of problem reached in through a completely different door and took out my side income instead.</p><h3>The part I can’t fully shake</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_WPrpKwY28rgy2vf" /></figure><p>I didn’t choose t.me. Telegram did, a decade before I ever signed up, and I built a small paying business on top of their choice without ever once asking myself what it was actually built on. Every dev who’s ever put a Telegram bot in front of customers made the identical unexamined bet. We all just assumed the plumbing was neutral, the way .com feels neutral, when it never was. Nobody had flipped this particular switch before, at this scale. Now somebody has.</p><blockquote>I don’t have a tidy fix to offer you. I’m not going to tell you to migrate off Telegram, mine still works fine, the app layer’s untouched, it’s just the front door that’s welded shut.</blockquote><p>I registered a backup domain this morning, a boring .com, and I’m going to spend tonight redirecting my subscribers to it one exhausted DM at a time, the same unglamorous move bit.ly made fifteen years ago for the exact same reason.</p><p>Whether Montenegro flips the switch back tomorrow or next week or ever, I genuinely don’t know. Neither does Durov, as far as I can tell, and he’s the one with actual leverage to find out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8efaee8b6135" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’ve patched the same Linux bug three times in ten years]]></title>
            <link>https://medium.com/@fatima02/ive-patched-the-same-linux-bug-three-times-in-ten-years-9049bd9a36ea?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9049bd9a36ea</guid>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[deep-learning]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 04:02:18 GMT</pubDate>
            <atom:updated>2026-08-26T04:02:18.763Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7FhmEaoV8MAln6ok" /></figure><p><em>Dirty COW, Dirty Pipe, now pedit COW. Different module, same wound. We keep acting surprised.</em></p><p>I didn’t get past the headline before I knew roughly how it worked.</p><p>“New Linux flaw lets a local user get root by poisoning the page cache.” Okay. Which part of the kernel forgot to make a copy of a page before it wrote to it this time? Because that’s the whole movie, and I’ve now sat through it three times.</p><p>2016 was Dirty COW. I still remember the cow. Somebody made a little logo, put it on dirtycow.ninja, a cartoon cow, because the Linux security crowd has always had this gallows humor about the stuff that can quietly hand your box to a stranger.</p><p>That one was a race in copy-on-write for private read-only mappings, and the genuinely horrifying part was its age. The bug had been sitting in the kernel for the better part of a decade.</p><p>Phil Oester didn’t find it in a lab, he found it being used against a real server. I spent that night rebooting a fleet I was on the hook for and refreshing a mailing list. 3am, cold coffee, the works.</p><p>2022 was Dirty Pipe. Max Kellermann’s writeup is still one of the best vuln writeups I’ve ever read, and I say that as someone who skims most of them. Different mechanism, pipe buffers that round, a flag called PIPE_BUF_FLAG_CAN_MERGE that got added back in 5.8 and quietly meant you could splice into a page you didn’t own and the page cache would just take it.</p><blockquote>Overwrite a read-only file you don’t have permission to touch. I patched, I moved on, I told myself the kernel people would go tighten that whole area up.</blockquote><p>And now it’s 2026 and I’m reading about pedit COW.</p><h3>Same wound, new module</h3><p>CVE-2026–46331. The bug lives in act_pedit, the packet-editing action in the traffic control subsystem. tc. The thing you reach for maybe twice a year to shape traffic and otherwise forget exists.</p><p>The function tcf_pedit_act() is meant to do the careful thing, make a private copy before it edits, the standard copy-on-write move. It checks the writable range exactly once, up front, before some of the edit keys have actually worked out where they&#39;re going to write, because a few of them only resolve their offset at runtime.</p><p>You can see the hole from here. The check passes against the range you knew about, then the write lands somewhere you didn’t, which turns out to be a shared page in the page cache instead of your private copy.</p><p>Copy-on-write, except the copy is optional if the kernel’s in a hurry.</p><p>So an unprivileged user spins up a user namespace, which hands them CAP_NET_ADMIN inside that namespace, which is enough to configure tc rules, which is enough to aim this thing.</p><blockquote>And what they aim it at is the cached copy of /bin/su sitting in memory.</blockquote><p>They patch a small payload into it. Then they run su, except it isn&#39;t really su anymore, it&#39;s su with their code stapled in, and it runs as root because su is setuid root and the kernel has no clue the bytes it&#39;s executing aren&#39;t the bytes on disk.</p><p>That last bit is the part that made me put the coffee down.</p><h3>Your integrity scanner is going to say everything’s fine</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g-Ncb6Fn45KLMnzB" /></figure><p>This is what gets me about the 2026 version specifically. The file on disk never changes. /bin/su has the same hash it had yesterday. So your AIDE database is clean. Tripwire&#39;s happy. Whatever your EDR hashes on its schedule, it reads the disk, sees nothing, sends no alert.</p><p>The poisoned copy only ever lives in the page cache, in RAM, which is exactly where the CPU goes to execute it.</p><p>So the one control a lot of shops lean on for “would we even notice if someone tampered with a system binary” answers no, confidently, the whole time there’s a root shell open.</p><p>I have sold that control to auditors. I’ve pointed at the green checkmark in a SOC 2 review and said see, file integrity monitoring, we’d catch it. For this whole class of bug that checkmark is set dressing. It was always set dressing for in-memory tampering, I just never had a clean example to point at until now.</p><p>Containers don’t save you here, before someone asks. This is the host kernel. Your pod, your CI runner, that nice rootless-looking user namespace, they all sit on the one kernel underneath, and the bug is in the kernel.</p><p>User namespaces were supposed to be the thing that made it safer to give untrusted code some room. They’re also the thing that hands out the CAP_NET_ADMIN this exploit needs. Cuts both ways.</p><h3>The part nobody’s angry enough about</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eWXX3srI7jJvqjTh" /></figure><p>The fix landed on the netdev mailing list back in late May. Out in the open. Anyone could read it. It went in as a routine data-corruption patch, the kind that scrolls past you a hundred a week, and nobody pinned the words “local privilege escalation” to it.</p><p>The CVE didn’t get assigned until June 16, when the fix actually merged. The working exploit showed up inside a day. Some account called sgkdev dropped it on GitHub.</p><p>So the window between “the bug is described, publicly, on a list the entire world can read” and “anyone with a login can have root” was, what, three weeks and change? And for most of that window the people who’d have wanted to know were not looking, because it was filed under data corruption, not security.</p><p>I’m not even mad at the kernel devs for that. There’s no clean way to flag every memory-corruption fix as a possible exploit primitive, there are far too many, and most of them honestly aren’t.</p><blockquote>But it does poke a hole in the tidy “responsible disclosure keeps you safe” story, a hole roughly the size of a public Git history. The people you’re worried about read netdev too.</blockquote><p>And it isn’t even alone this month. There’s a sibling, DirtyClone, CVE-2026–43503, the fourth one in a little family they’re calling DirtyFrag, where netfilter’s TEE target clones a packet, loses a flag that was supposed to mark the buffer as shared, and IPsec decryption ends up writing into a page cache page it shouldn’t. JFrog put out the full walkthrough on the 25th.</p><blockquote>Completely different corner of the kernel. Same exact shape. A fast path writes into a page it doesn’t own and the page cache eats the difference.</blockquote><h3>What I actually did</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z_mbrEIz3tNeiVp0" /></figure><p>Blocked the module. echo &quot;blacklist act_pedit&quot; into a file under /etc/modprobe.d, done, because I checked and not one box in our fleet uses tc pedit for anything. That took four minutes. Verifying that nothing used it, walking back through some traffic-shaping config a contractor stood up in 2019 that I&#39;ve been scared to touch ever since, that took the rest of the afternoon.</p><p>The patch itself I&#39;m rolling the normal way. RHEL 8 and 9 mostly, a couple of 10s, plus the Ubuntu side that runs everything from 20.04 up to 26.04, and every one of those is on the affected list.</p><p>If you can’t blocklist the module because you genuinely use tc, the other lever is unprivileged user namespaces. Turn them off if your workloads don&#39;t need them. A sysctl, you know the one. Plenty of people run with them off already and barely notice; plenty of others would break half their container tooling doing it. Your blast radius, your call.</p><p>But the patch-and-blocklist part isn’t really what I’ve been chewing on.</p><p>It’s that I’ve now done this same dance in 2016, 2022, and 2026, and it is the same dance. The page cache is shared mutable state that a dozen subsystems reach into. Copy-on-write is the promise that each of them will make its own copy before it scribbles.</p><blockquote>And every few years some fast path somewhere forgets to keep the promise, and you can rewrite a root-owned binary in memory while the disk sits there looking innocent.</blockquote><p>We name the new one after a farm animal, write a good blog post, patch, and act surprised. We are going to be surprised again. I’d put money on it landing before 2029.</p><blockquote>Anyway. Go see whether act_pedit is even loaded on your boxes. lsmod | grep pedit. I&#39;ll wait.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9049bd9a36ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The AI World Is Booming — Here’s What You Need to Know ]]></title>
            <link>https://medium.com/@fatima02/the-ai-world-is-booming-heres-what-you-need-to-know-e6a2e05d08f6?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6a2e05d08f6</guid>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[booming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Mon, 24 Aug 2026 04:34:58 GMT</pubDate>
            <atom:updated>2026-08-24T04:34:58.878Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k-hgSoxvTAJRcRHc" /></figure><p>The rise of Artificial Intelligence isn’t just a trend — it’s a <strong>global transformation</strong>.</p><p>From automating mundane tasks to creating music, art, and code, AI is now <em>everywhere</em>. Whether you’re a developer, entrepreneur, student, or just curious — this is your call to <strong>understand, explore, and maybe even contribute</strong> to the AI revolution.</p><p>Let’s dive deep into what’s happening in the world of AI 🌐👇</p><h3>🧠 What Exactly Is AI?</h3><p>AI (Artificial Intelligence) is a field of computer science that focuses on creating systems capable of performing tasks that typically require human intelligence — like reasoning, learning, decision-making, perception, and even creativity.</p><p>Key categories include:</p><ul><li><strong>Machine Learning</strong> (learning from data)</li><li><strong>Natural Language Processing</strong> (understanding and generating human language)</li><li><strong>Computer Vision</strong> (analyzing images/videos)</li><li><strong>Generative AI</strong> (creating new content like text, images, code)</li></ul><h3>🚀 The Explosion of Generative AI</h3><p>Generative AI tools like ChatGPT, Midjourney, and Claude have taken the internet by storm. These models can:</p><ul><li>Write stories, poems, or full-blown articles ✍️</li><li>Generate artwork from text prompts 🎨</li><li>Write and debug code in seconds 💻</li><li>Create music and edit videos 🎧🎬</li></ul><p>This is <strong>not science fiction</strong> anymore. It’s real. It’s powerful. And it’s growing <strong>faster than any tech in history</strong>.</p><h3>🧩 AI in Daily Life — You’re Already Using It!</h3><p>You may not realize it, but AI touches your life every day:</p><ul><li>📱 Your phone’s voice assistant (Siri, Google Assistant)</li><li>🎵 Spotify recommendations</li><li>📦 Amazon delivery tracking and suggestions</li><li>🛒 Chatbots on websites</li><li>🧠 Personalized ads and feeds</li></ul><p>AI is not some far-off robot apocalypse — it’s a part of your <strong>everyday decisions and convenience</strong>.</p><h3>💼 AI Is Changing Jobs — But Not Always Replacing Them</h3><p>There’s fear that AI will “steal” jobs. Truth? <strong>Yes and no.</strong></p><p>🔁 <strong>Yes</strong> — Some repetitive or manual roles may become automated<br> 🔁 <strong>No</strong> — New roles are being created: AI trainers, prompt engineers, model auditors, data ethicists, and more</p><p>Think of AI as a <strong>power tool</strong>. Those who learn to use it will unlock <em>superhuman productivity</em>.</p><h3>🧪 Developers: AI Is Your New Best Friend</h3><p>For coders, AI has become the ultimate sidekick:</p><ul><li>💡 Brainstorm logic or functions</li><li>🐞 Detect bugs faster</li><li>🏗 Generate boilerplate code</li><li>📚 Learn new languages or concepts quickly</li></ul><p>Tools like GitHub Copilot, CodeWhisperer, and ChatGPT are turning developers into <strong>10x problem solvers</strong>.</p><h3>🎨 Creatives: AI Unlocks New Mediums</h3><p>Writers, artists, video editors, designers — AI isn’t replacing your creativity. It’s <strong>enhancing it</strong>.</p><p>From turning doodles into polished designs to editing video cuts in seconds, AI empowers creators to do more with less.</p><blockquote>💡 Your imagination now has no limit.</blockquote><h3>🔐 But Wait — What About Ethics?</h3><p>As AI grows, so do concerns:</p><ul><li>Bias in training data 🧮</li><li>Deepfakes and misinformation 🧠</li><li>Privacy and surveillance 👀</li><li>Dependence on automation ⚙️</li></ul><p>The future must be built <strong>responsibly</strong>. Ethical AI isn’t a nice-to-have — it’s essential.</p><blockquote>That’s why we need more voices — developers, designers, users — to shape AI that serves <em>everyone</em>.</blockquote><h3>🛣 So, Where Is AI Headed Next?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iirYtyTk1Nu4zf95" /></figure><p>The road ahead is filled with possibilities:</p><ul><li>AI doctors giving real-time medical advice 🩺</li><li>Virtual tutors teaching in every language 🌐</li><li>Autonomous vehicles and drones 🛸</li><li>Personalized education and therapy 🧘‍♀️</li><li>AI-enhanced human creativity 🎭</li></ul><p>And this is just the beginning…</p><h3>🧭 Final Thoughts: Don’t Just Watch — Participate</h3><p>The AI world is open to you. You don’t need a PhD to get started.</p><ul><li>Explore tools like ChatGPT, DALL·E, and Claude</li><li>Learn Python or experiment with open-source AI libraries like Hugging Face</li><li>Start with small projects — like an AI chatbot, a content generator, or an image editor</li><li>Stay curious, and <strong>build things that matter</strong></li></ul><blockquote>Whether you want to make life easier, build something cool, or solve a real-world problem — <strong>AI is your co-pilot now.</strong></blockquote><blockquote>🌟 This is your invitation to not just witness the AI revolution, but to be part of it.</blockquote><blockquote>Let the future begin. 🤝</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6a2e05d08f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React JS Types of Routers]]></title>
            <link>https://medium.com/@fatima02/react-js-types-of-routers-7f861b30aec2?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f861b30aec2</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[router]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 10:48:47 GMT</pubDate>
            <atom:updated>2026-01-31T10:48:47.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YQhumr8PC-FoziUe" /></figure><p>When creating a React application, managing navigation between different views or pages is important. React Router is the standard library for routing in React, enabling seamless navigation while maintaining the Single Page Application (SPA) behaviour.</p><h3>What is React Router?</h3><p>React Router is a <strong>declarative, component-based routing library</strong> for React applications. It enables navigation without reloading the page, making the application faster and more dynamic.</p><ul><li>Supports <strong>client-side routing</strong> in React applications.</li><li>Provides <strong>nested routes</strong> for better organization.</li><li>Allows for <strong>dynamic routing</strong> using parameters.</li><li>Enables <strong>programmatic navigation</strong> via hooks like useNavigate().</li></ul><p>Before diving into types of routers, let’s ensure that React Router DOM is installed in your React project</p><pre>npm install react-router-dom</pre><h3>Types of Routers in React</h3><p>React provides several types of routers that serve different purposes. The main routers in React are</p><ol><li>Browser Router (&lt;BrowserRouter&gt;)</li><li>Hash Router (&lt;HashRouter&gt;)</li><li>Memory Router (&lt;MemoryRouter&gt;)</li><li>Static Router (&lt;StaticRouter&gt;)</li><li>Native Router (&lt;NativeRouter&gt;)</li></ol><h3>1. Browser Router</h3><p>BrowserRouter is the most commonly used router in React applications that are deployed in a modern web environment.</p><ul><li>It uses the HTML5 history API to manage the navigation.</li><li>This router makes use of pushState, replaceState, and the popState event to keep the UI in sync with the URL.</li><li>It allows for clean and human-readable URLs without hash fragments.</li></ul><h4>When to Use BrowserRouter</h4><p>BrowserRouter is a powerful and commonly used router in React applications, and it’s ideal for web applications that require clean, SEO-friendly URLs and rely on server-side routing.</p><ul><li><strong>Hosting on a Web Server with Proper Routing: </strong><a href="https://www.geeksforgeeks.org/reactjs/browserrouter-in-react/">BrowserRouter</a> works best when your app is hosted on a web server that can handle dynamic URLs (server-side routing).</li><li><strong>Improved SEO:</strong> Since BrowserRouter generates URLs without the hash, search engines can more easily crawl and index your pages.</li><li><strong>Single Page Applications (SPA):</strong> BrowserRouter is commonly used in SPAs, where the entire app runs on a single page.</li><li><strong>Handling Multiple Views or Pages: </strong>If your app includes multiple views or pages BrowserRouter helps manage these views by linking each one to a specific URL.</li></ul><pre>import React from &quot;react&quot;;<br>import { BrowserRouter, Routes, Route, Link } from &quot;react-router-dom&quot;;<br>import Home from &quot;./components/Home&quot;;<br>import About from &quot;./components/About&quot;;<br>import Contact from &quot;./components/Contact&quot;;<br><br>const App = () =&gt; {<br>    return (<br>        &lt;BrowserRouter&gt;<br>            &lt;div style={{ fontFamily: &quot;Arial, sans-serif&quot; }}&gt;<br>                {/* Navigation Bar */}<br>                &lt;nav<br>                    style={{<br>                        backgroundColor: &quot;#333&quot;,<br>                        padding: &quot;10px&quot;,<br>                        display: &quot;flex&quot;,<br>                        justifyContent: &quot;center&quot;,<br>                    }}<br>                &gt;<br>                    &lt;ul<br>                        style={{<br>                            listStyle: &quot;none&quot;,<br>                            display: &quot;flex&quot;,<br>                            gap: &quot;20px&quot;,<br>                            padding: &quot;0&quot;,<br>                            margin: &quot;0&quot;,<br>                        }}<br>                    &gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/&quot; style={linkStyle}&gt;<br>                                Home<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/about&quot; style={linkStyle}&gt;<br>                                About Us<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/contact&quot; style={linkStyle}&gt;<br>                                Contact Us<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                    &lt;/ul&gt;<br>                &lt;/nav&gt;<br><br>                {/* Page Content */}<br>                &lt;div<br>                    style={{ display: &quot;flex&quot;, justifyContent: &quot;center&quot;, padding: &quot;20px&quot; }}<br>                &gt;<br>                    &lt;Routes&gt;<br>                        &lt;Route path=&quot;/&quot; element={&lt;Home /&gt;} /&gt;<br>                        &lt;Route path=&quot;/about&quot; element={&lt;About /&gt;} /&gt;<br>                        &lt;Route path=&quot;/contact&quot; element={&lt;Contact /&gt;} /&gt;<br>                    &lt;/Routes&gt;<br>                &lt;/div&gt;<br>            &lt;/div&gt;<br>        &lt;/BrowserRouter&gt;<br>    );<br>};<br><br>// Style for navigation links<br>const linkStyle = {<br>    textDecoration: &quot;none&quot;,<br>    color: &quot;white&quot;,<br>    fontSize: &quot;18px&quot;,<br>    fontWeight: &quot;bold&quot;,<br>};<br><br>export default App;</pre><p><strong>Output</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/0*_AgWdiWn0O_oRp2J.gif" /></figure><p><strong>In this code</strong></p><ul><li><strong>App.js: </strong>Uses BrowserRouter for navigation with clean URLs (e.g., /about). It defines routes and a navigation menu.</li><li><strong>Home.js:</strong> Displays a simple home page with a welcome message.</li><li><strong>About.js:</strong> Shows an “About Us” section with a GeeksforGeeks link.</li><li><strong>Contact.js:</strong> Displays contact details with the GeeksforGeeks Noida address.</li></ul><h3>2. Memory Router</h3><p>Memory Router is used when there is no web browser, like in testing or mobile apps. It remembers the navigation history inside the app but does not change the URL. This makes it helpful for testing and non-browser environments.</p><ul><li><strong>No URL Change:</strong> Unlike Browser Router or HashRouter, <a href="https://www.geeksforgeeks.org/reactjs/explain-memoryrouter-in-concept-of-react-router/">MemoryRouter</a> does not change the browser’s URL. It stores the location state internally.</li><li><strong>In-memory history:</strong> It maintains history in memory, not in the URL or browser history, making it ideal for non-browser environments.</li></ul><h4>When to Use Memory Router</h4><p>Here are some use cases of Memory Router</p><ul><li><strong>Server-Side Rendering (SSR): </strong>When rendering React components on the server, where there is no URL to manage.</li><li><strong>Testing: </strong>Ideal for unit tests, allowing routing logic to be tested without modifying the browser’s URL.</li><li><strong>React Native:</strong> Since React Native doesn’t rely on URLs, Memory Router helps manage navigation in mobile apps.</li><li><strong>Non-Browser Environments:</strong> Useful in applications like Electron where the app does not interact with a browser’s URL.</li><li><strong>When URL Doesn’t Matter:</strong> If you don’t need to reflect state changes in the URL, Memory Router can manage routing internally</li></ul><pre>import React from &quot;react&quot;;<br>import { MemoryRouter, Routes, Route, Link } from &quot;react-router-dom&quot;;<br>import Home from &quot;./components/Home&quot;;<br>import About from &quot;./components/About&quot;;<br>import Contact from &quot;./components/Contact&quot;;<br><br>const App = () =&gt; {<br>    return (<br>        &lt;MemoryRouter&gt;<br>            &lt;div style={{ fontFamily: &quot;Arial, sans-serif&quot; }}&gt;<br>                {/* Navigation Bar */}<br>                &lt;nav<br>                    style={{<br>                        backgroundColor: &quot;#333&quot;,<br>                        padding: &quot;10px&quot;,<br>                        display: &quot;flex&quot;,<br>                        justifyContent: &quot;center&quot;,<br>                    }}<br>                &gt;<br>                    &lt;ul<br>                        style={{<br>                            listStyle: &quot;none&quot;,<br>                            display: &quot;flex&quot;,<br>                            gap: &quot;20px&quot;,<br>                            padding: &quot;0&quot;,<br>                            margin: &quot;0&quot;,<br>                        }}<br>                    &gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/&quot; style={linkStyle}&gt;<br>                                Home<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/about&quot; style={linkStyle}&gt;<br>                                About Us<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/contact&quot; style={linkStyle}&gt;<br>                                Contact Us<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                    &lt;/ul&gt;<br>                &lt;/nav&gt;<br><br>                {/* Page Content */}<br>                &lt;div<br>                    style={{ display: &quot;flex&quot;, justifyContent: &quot;center&quot;, padding: &quot;20px&quot; }}<br>                &gt;<br>                    &lt;Routes&gt;<br>                        &lt;Route path=&quot;/&quot; element={&lt;Home /&gt;} /&gt;<br>                        &lt;Route path=&quot;/about&quot; element={&lt;About /&gt;} /&gt;<br>                        &lt;Route path=&quot;/contact&quot; element={&lt;Contact /&gt;} /&gt;<br>                    &lt;/Routes&gt;<br>                &lt;/div&gt;<br>            &lt;/div&gt;<br>        &lt;/MemoryRouter&gt;<br>    );<br>};<br><br>// Style for navigation links<br>const linkStyle = {<br>    textDecoration: &quot;none&quot;,<br>    color: &quot;white&quot;,<br>    fontSize: &quot;18px&quot;,<br>    fontWeight: &quot;bold&quot;,<br>};<br><br>export default App;</pre><p><strong>Output</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/0*ghX6yTy9OPdLcwZw.gif" /></figure><p><strong>In this code</strong></p><ul><li>Contact.js: Displays a “Contact Us” section with an address (GeeksforGeeks Noida) in a bold, formatted style.</li><li>About.js: Shows an “About Us” section with a brief description of GeeksforGeeks and a clickable link to its website.</li><li>When linked in React Router, they render on /contact and /about routes.</li></ul><h3>3. Hash Router</h3><p>A Hash Router is another type of router used in React applications. It works by using the hash portion of the URL (the part that comes after the # symbol) to manage navigation.</p><ul><li>It uses URL hash (#) to represent different routes (e.g., <a href="http://example.com/#/home).">http://example.com/#/home).</a></li><li>The hash part is not sent to the server but is used to change the displayed content in the browser.</li><li>It’s useful for handling navigation in environments where you can’t use regular URLs (like in static websites or when there’s no server-side routing).</li></ul><h4>When to Use Hash Router</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rAiCamNOfrrYJ3GC" /></figure><p>HashRouter is a useful and simple router for React applications that rely on URL hashes for navigation, especially in environments where server-side routing is not available.</p><ul><li><strong>Hosting on Static File Servers:</strong> HashRouter works best when your app is hosted on static file servers, like <a href="https://www.geeksforgeeks.org/git/github-pages/">GitHub Pages</a>, that cannot handle dynamic routing or need the URL to stay static.</li><li><strong>No Server-Side Routing: </strong>Ideal for situations where server-side routing is not set up or you don’t have access to configure it. It keeps the routing within the client-side, without needing the server to manage different routes.</li><li><strong>Simpler Projects:</strong> For smaller, simpler projects or prototypes that don’t require clean URLs or SEO optimization,<a href="https://www.geeksforgeeks.org/reactjs/hashrouter-in-react-router/"> HashRouter</a> offers an easy solution for adding routing</li></ul><pre>import React from &quot;react&quot;;<br>import { HashRouter, Routes, Route, Link } from &quot;react-router-dom&quot;;<br>import Home from &quot;./components/Home&quot;;<br>import About from &quot;./components/About&quot;;<br>import Contact from &quot;./components/Contact&quot;;<br><br>const App = () =&gt; {<br>    return (<br>        &lt;HashRouter&gt;<br>            &lt;div style={{ fontFamily: &quot;Arial, sans-serif&quot; }}&gt;<br>                {/* Navigation Bar */}<br>                &lt;nav<br>                    style={{<br>                        backgroundColor: &quot;#333&quot;,<br>                        padding: &quot;10px&quot;,<br>                        display: &quot;flex&quot;,<br>                        justifyContent: &quot;center&quot;,<br>                    }}<br>                &gt;<br>                    &lt;ul<br>                        style={{<br>                            listStyle: &quot;none&quot;,<br>                            display: &quot;flex&quot;,<br>                            gap: &quot;20px&quot;,<br>                            padding: &quot;0&quot;,<br>                            margin: &quot;0&quot;,<br>                        }}<br>                    &gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/&quot; style={linkStyle}&gt;<br>                                Home<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/about&quot; style={linkStyle}&gt;<br>                                About Us<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                        &lt;li&gt;<br>                            &lt;Link to=&quot;/contact&quot; style={linkStyle}&gt;<br>                                Contact Us<br>                            &lt;/Link&gt;<br>                        &lt;/li&gt;<br>                    &lt;/ul&gt;<br>                &lt;/nav&gt;<br><br>                {/* Page Content */}<br>                &lt;div<br>                    style={{ display: &quot;flex&quot;, justifyContent: &quot;center&quot;, padding: &quot;20px&quot; }}<br>                &gt;<br>                    &lt;Routes&gt;<br>                        &lt;Route path=&quot;/&quot; element={&lt;Home /&gt;} /&gt;<br>                        &lt;Route path=&quot;/about&quot; element={&lt;About /&gt;} /&gt;<br>                        &lt;Route path=&quot;/contact&quot; element={&lt;Contact /&gt;} /&gt;<br>                    &lt;/Routes&gt;<br>                &lt;/div&gt;<br>            &lt;/div&gt;<br>        &lt;/HashRouter&gt;<br>    );<br>};<br><br>// Style for navigation links<br>const linkStyle = {<br>    textDecoration: &quot;none&quot;,<br>    color: &quot;white&quot;,<br>    fontSize: &quot;18px&quot;,<br>    fontWeight: &quot;bold&quot;,<br>};<br><br>export default App;</pre><p><strong>output</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/0*-IeQEyCS90gj8JCT.gif" /></figure><p><strong>In this code</strong></p><ul><li><strong>App.js:</strong> Uses HashRouter for navigation. It contains a navigation bar with links and defines routes for Home, About, and Contact pages.</li><li><strong>Home.js:</strong> Displays a simple Home Page with a heading and a welcome message.</li><li><strong>About.js:</strong> Shows an “About Us” section describing GeeksforGeeks with a clickable link.</li><li><strong>Contact.js:</strong> Displays a “Contact Us” section with the GeeksforGeeks Noida address.</li></ul><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pjVERQVYN5GwL4hF" /></figure><p><strong>Routing</strong> is a fundamental concept in <strong>React</strong> that allows you to create interactive and<strong> dynamic applications</strong>.</p><p>Understanding the different types of routers, like <strong>BrowserRouter </strong>and<strong> HashRouter</strong>, will help you choose the right approach based on your project’s requirements.</p><blockquote>Each router has its use case, and picking the one that suits your application’s needs will ensure a smooth and error-free experience.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f861b30aec2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next.js Functions: generateStaticParams with Examples Explanation]]></title>
            <link>https://medium.com/@fatima02/next-js-functions-generatestaticparams-with-examples-explanation-811dfb30b7aa?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/811dfb30b7aa</guid>
            <category><![CDATA[generatestaticparams]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 06:24:41 GMT</pubDate>
            <atom:updated>2026-01-30T06:24:41.044Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*psCfPI9YoIPg7iwW" /></figure><p><strong>“generateStaticParams</strong>” is a function name or identifier used as a placeholder in the context of NextJS development. It doesn’t represent a built-in or standard function in NextJS itself.</p><blockquote>Instead, it seems to be a hypothetical function name that could be used to illustrate the process of generating static parameters in a NextJS application.</blockquote><h3>generateStaticParams:</h3><p>The generateStaticParams function allows for the static generation of routes during the build process, when used alongside dynamic route segments, rather than dynamically generating them upon request.”</p><pre>export async function generateStaticParams() {<br>  const posts = await fetch(&#39;https://.../posts&#39;).then((res) =&gt; res.json())<br> <br>  return posts.map((post) =&gt; ({<br>    slug: post.slug,<br>  }))<br>}<br> <br>// using the `params` returned by `generateStaticParams`<br>export default function Page({ params }) {<br>  const { slug } = params<br>  // ...<br>}</pre><p><strong>Parameters</strong></p><ul><li>When multiple dynamic segments in a route utilize generateStaticParams, the child generateStaticParams function is triggered for each set of parameters generated by the parent.</li><li>The params object holds the populated parameters from the parent generateStaticParams, enabling their utilization for generating parameters within a child segment.</li></ul><p><strong>Return Type</strong></p><ul><li>generateStaticParams needs to give back a list of items. Each item in the list should represent a dynamic part of the route that’s been filled with data.</li><li>In each item, there should be a part that represents the name of the dynamic segment, and another part that holds the actual value to fill in for that segment.</li></ul><h3>Single Dynamic Segment</h3><pre>export function generateStaticParams() {<br>  return [{ id: &#39;a&#39; }, { id: &#39;b&#39; }, { id: &#39;c&#39; }]<br>}<br> <br>export default function Page({ params }: { params: { id: string } }) {<br>  const { id } = params<br>}</pre><p>In this example, the route is `app/student/[id]/page.tsx`, featuring a single dynamic segment `[id]`. The `generateStaticParams` function provides an array with three objects, each containing a different `id` value.</p><p>Consequently, three versions of this page will be statically generated, accessible via the URLs `/student/1`, `/student/2`, and `/student/3`. Within the `Page` component, the `id` is obtained from the `params` object, facilitating its usage for further processing.</p><h3>Multiple Dynamic Segments</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NDGvJvXxiUrZwh62" /></figure><pre>export function generateStaticParams() {<br>  return [<br>    { name: &#39;a&#39;, subject: &#39;english&#39; },<br>    { name: &#39;b&#39;, subject: &#39;hindi&#39; },<br>    { name: &#39;c&#39;, subject: &#39;maths&#39; },<br>  ]<br>}<br> <br><br>export default function Page({<br>  params,<br>}: {<br>  params: { category: string; product: string }<br>}) {<br>  const { category, product } = params<br>  // ...<br>}</pre><p>In this scenario, the route is app/student/[name]/[subject]/page.tsx, comprising two dynamic segments [name] and [subject]. The generateStaticParams function returns an array of objects, each specifying various combinations of name and subject.</p><p>As a result, three versions of this page will be statically generated, accessible via URLs like /student/a/english, /student/b/hindi, and /student/c/maths. Inside the Page component, the params object should contain properties for both name and subject, allowing us to extract and utilize these values for further processing.</p><h3>Catch-all Dynamic Segment</h3><pre>export function generateStaticParams() {<br>  return [{ slug: [&#39;a&#39;, &#39;english&#39;] }, { slug: [&#39;b&#39;, &#39;hindi] }, { slug: [&#39;c&#39;, &#39;maths&#39;] }]<br>}<br> <br><br>export default function Page({ params }: { params: { slug: string[] } }) {<br>  const { slug } = params<br>  // ...<br>}</pre><p>In this example, the route is `app/student/[…slug]/page.tsx`, featuring a catch-all dynamic segment `[…slug]`, allowing for variable path lengths.</p><p>The `generateStaticParams` function returns an array of objects, each containing an array within the `slug` property, representing different combinations of values. Consequently, multiple versions of this page will be statically generated, with URLs like `/student/a/english`, `/student/b/hindi`, and `/student/c/maths`.</p><p>Inside the `Page` component, the `params` object includes an array `slug`, enabling us to access and utilize the variable path segments for further processing.</p><h3>Generate params from the bottom up</h3><pre>export async function generateStaticParams() {<br>  const products = await fetch(&#39;https://.../products&#39;).then((res) =&gt; res.json())<br> <br>  return products.map((product) =&gt; ({<br>    category: product.category.slug,<br>    product: product.id,<br>  }))<br>}<br> <br>export default function Page({<br>  params,<br>}: {<br>  params: { category: string; product: string }<br>}) {<br>  // ...<br>}</pre><p>Dynamic segments starting from the child route segment and moving towards the parent route segment.</p><p>For example, in the route app/products/[category]/[product]/page.tsx, we want to generate params for both [category] and [product]. To achieve this, we utilize the generateStaticParams function.</p><blockquote>This function asynchronously fetches product data from an API and maps each product to an object containing category and product properties. These properties represent dynamic segments that will populate the route.</blockquote><p>Inside the Page component, we receive category and product as parameters from the params object, enabling us to use them for rendering content related to specific product categories and products.</p><h3>Generate params from the top down:</h3><pre>export async function generateStaticParams({<br>  params: { category },<br>}: {<br>  params: { category: string }<br>}) {<br>  const products = await fetch(<br>    `https://.../products?category=${category}`<br>  ).then((res) =&gt; res.json())<br> <br>  return products.map((product) =&gt; ({<br>    product: product.id,<br>  }))<br>}<br> <br>export default function Page({<br>  params,<br>}: {<br>  params: { category: string; product: string }<br>}) {<br>  // ...<br>}</pre><p>Generating params from the top down means first creating the parent route segment and then using it to create the child route segment.</p><p>For example, let’s consider the route app/products/[category]/layout.tsx. Here, we want to generate parameters for the [category] segment. The generateStaticParams function fetches product data and creates an object for each product with its category.</p><p>In the Layout component, we receive the category as a parameter from the params object. This allows us to show content specific to product categories.</p><p>In the child route segment app/products/[category]/[product]/page.tsx, the generateStaticParams function runs for each category created by the parent. It fetches product data based on the category received from the parent.</p><p>As a result, the Page component gets both category and product parameters from the params object, helping us display content for specific products within their respective categories.</p><h3>Generate only a subset of params</h3><pre>export const dynamicParams = false<br> <br>export async function generateStaticParams() {<br>  const posts = await fetch(&#39;https://.../posts&#39;).then((res) =&gt; res.json())<br>  const topPosts = posts.slice(0, 10)<br> <br>  return topPosts.map((post) =&gt; ({<br>    slug: post.slug,<br>  }))<br>}</pre><p>Generating only a subset of params for a route involves returning an array of objects with specific dynamic segments. By using the dynamicParams segment config option, you can manage what occurs when a dynamic segment is accessed that wasn’t generated with generateStaticParams.</p><p>For instance, in the route app/blog/[slug]/page.js, we limit the params to show only the top 10 posts. We set dynamicParams to false, indicating that any dynamic segment beyond the top 10 posts will result in a 404 error.</p><p>The generateStaticParams function fetches posts and selects the top 10. It then creates an array of objects, each containing the slug of a post. This array serves as the subset of params for the route.</p><blockquote>As a result, only the top 10 posts will have dynamically generated pages, while accessing other posts will lead to a 404 error.</blockquote><h3>Purpose</h3><ul><li>Next.js allows you to generate pages statically at build time using data from external sources like APIs or databases.</li><li>Static generation helps improve performance by pre-rendering pages with data that doesn’t change frequently.</li></ul><h3>Static Paths</h3><ul><li>When a Next.js application is built, it needs to know what pages to generate statically.</li><li>The getStaticPaths function is used to define a list of paths that should be statically generated based on dynamic data.</li><li>Each path can include parameters, allowing for dynamic content generation.</li></ul><h3>Dynamic Routes</h3><ul><li>Next.js supports dynamic routes, where parts of the URL are treated as parameters.</li><li>For example, in /posts/[id], [id] is a parameter representing a dynamic value.</li><li>By generating static paths with parameters, Next.js can pre-render pages for all possible parameter values.</li></ul><h3>Data Fetching</h3><ul><li>Once the static paths are defined, Next.js needs to fetch data for each path to pre-render the pages.</li><li>The getStaticProps function is used to fetch data for a specific path based on its parameters.</li><li>This function runs at build time and receives the parameters of the current path as input.</li></ul><h3>Rendering Process</h3><ul><li>During the build process, Next.js first calls getStaticPaths to determine the list of paths to pre-render.</li><li>For each path, it then calls getStaticProps to fetch data and pre-render the page.</li><li>The pre-rendered pages are saved as static HTML files, which are served to users for improved performance.</li></ul><h3>What we are going to do</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5sufwUvG0se6U-bj" /></figure><ul><li>We’re going to build a Next.js application that implements dynamic routing for blog posts. Initially, we’ll fetch the blog post data dynamically from an external API (https://jsonplaceholder.typicode.com/posts). Each blog post will have a unique slug in the URL, such as /blog/[slug], where the slug represents the ID of the blog post. We’ll start by setting up dynamic routing to render the blog post content based on the slug parameter in the URL.</li><li>After successfully implementing dynamic routing, we’ll optimize our application by using static parameter generation. This involves pre-generating the pages for all possible blog post slugs during the build process, improving performance by serving pre-rendered pages instead of fetching data dynamically on each request.</li><li>To achieve this, we’ll use Next.js’s getStaticPaths and getStaticProps functions. We’ll modify our existing dynamic routing setup to use static parameter generation, ensuring that the blog post pages are pre-rendered at build time. This approach enhances the user experience by reducing loading times and server load, resulting in a faster and more responsive application.</li></ul><p><strong>Step 1: </strong>Initialize a NextJS Project:</p><pre>npx create-next-app my-next-app</pre><p><strong>Step 2:</strong> Create the Blog Post Page</p><p>Inside the app directory, create a new directory named blog. and then create a new directory named [slug] inside the blog then create a file as page.js</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/311/0*boUDUk_QPrSsCrEK.png" /></figure><p><strong>Step 3: </strong>Fetch Blog Post Data Dynamically:</p><p>With this code, we’ve established dynamic routes for blog posts. When a user visits a page, the component fetches data from an external API to display the corresponding blog post.</p><blockquote>However, each time the page is loaded, it triggers a new API call, leading to redundant requests if the same URL is accessed repeatedly. Add this in page.js that you have created</blockquote><pre>export default async function BlogPost({ params }) {<br><br>    const { slug } = params;<br>    console.log(params.slug)<br>    const data1 = await fetch(<br>`https://jsonplaceholder.typicode.com/posts/$%7Bparams.slug%7D%60)<br>    const udata = await data1.json()<br><br>    return (<br>        &lt;div&gt;<br>            &lt;h1&gt;Blog Post&lt;/h1&gt;<br>            &lt;div&gt;<br>                &lt;h1&gt;{udata.title}&lt;/h1&gt;<br>                &lt;div&gt;{udata.body}&lt;/div&gt;<br>            &lt;/div&gt;<br>        &lt;/div&gt;<br>    );<br>}</pre><h3>Step 4: Implementing generateStaticParams:</h3><p>To address above issue, we’ll implement generateStaticParams in Next.js, a feature known as static parameter generation.</p><p>This allows us to pre-generate all possible blog post pages during the build process, ensuring that each page is readily available without the need for additional API calls.</p><p>By doing so, we optimize performance by serving pre-rendered pages, eliminating the need to hit the API every time a user accesses a blog post URL.</p><pre>export async function generateStaticParams() {<br><br>  const product = await fetch(&#39;https://jsonplaceholder.typicode.com/posts&#39;);<br>  const posts = await  product.json();<br>  return posts.map((i)=&gt;({<br>        slug : i.id.toString(),<br>    }))<br> <br>}<br><br>export default async function BlogPost({ params }  ) {<br><br>  const { slug } = params;<br>  console.log(params.slug)<br>  const data1 = await fetch(`<br> https://jsonplaceholder.typicode.com/posts/$%7Bparams.slug%7D%60)<br>  const udata = await data1.json()<br>  <br>  <br>  return (<br>    &lt;div&gt;<br>      &lt;h1&gt;Blog Post&lt;/h1&gt;<br>      &lt;div&gt;<br>        &lt;h1&gt;{udata.title}&lt;/h1&gt;<br>        &lt;div&gt;{udata.body}&lt;/div&gt;<br>      &lt;/div&gt;<br>    &lt;/div&gt;<br>  );<br>}</pre><p><strong>Step 5: Build the Project: </strong>Run the build command to generate the optimized production build of the Next.js project.</p><pre>npm run build</pre><blockquote>By building the project, Next.js generates the generateStaticParams at build time, saving them in the .next folder.</blockquote><p>This means that the HTML files for each blog post page are pre-generated during the build process. As a result, when a user accesses a blog post page, the content is immediately available without the need for additional API calls.</p><blockquote>This optimization significantly reduces loading times and minimizes the number of API requests, enhancing the overall performance and user experience of the website.</blockquote><p><strong>Start the Development Server:</strong></p><pre>npm run dev</pre><p><strong>Output</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*b4rILDx32KK61NE8.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=811dfb30b7aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[⚡ Why Next.js Feels Like the Superpower You Didn’t Know You Needed ✨]]></title>
            <link>https://medium.com/@fatima02/why-next-js-feels-like-the-superpower-you-didnt-know-you-needed-098d614411fd?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/098d614411fd</guid>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[superpowers]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 07:15:00 GMT</pubDate>
            <atom:updated>2026-01-28T07:15:00.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UF4drGBT1f4XS_Ac" /></figure><p>You’re a React developer. You love components, hooks, and the freedom of the front end .</p><p>But then reality hits:</p><ul><li>Routing is a mess.</li><li>SEO? Good luck.</li><li>Code splitting? Sounds fancy but hard to do.</li><li>You need a backend. But also don’t want to leave React.</li></ul><p>That’s when you meet <strong>Next.js</strong> — and it changes everything.</p><blockquote><em>“React gave us components.<br> Next.js gave us </em><strong><em>structure</em></strong><em>.” 💪</em></blockquote><p>Let’s walk through <strong>why Next.js is not just a framework, but a game-changer</strong> — and how you can master it for real-world projects in 2024 and beyond.</p><h3>🌍 1. Routing Without the Headache</h3><p>With React Router, you manually define every route.<br> With Next.js?</p><p>📁 Your folder structure <em>is</em> your router:</p><pre>pages/<br>  index.js       → /<br>  about.js       → /about<br>  blog/[slug].js → /blog/:slug</pre><p>✅ No need for Switch or Route components.<br> ✅ Dynamic routes out of the box.<br> ✅ File-based simplicity = scalable routing.</p><h3>🚀 2. SEO That Actually Works</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ux6SW7n_YoNN48fC" /></figure><p>React is great for interactive UIs… but bad for SEO out of the box. 🫠</p><p>Next.js gives you:</p><ul><li>Server-side rendering (SSR)</li><li>Static generation (SSG)</li><li>getServerSideProps, getStaticProps, and getStaticPaths</li></ul><p>📈 That means:</p><ul><li>Pages are pre-rendered</li><li>Search engines can index real content</li><li>You rank better</li><li>Pages load faster</li></ul><p>✅ Add &lt;Head&gt; from next/head to control titles, meta tags, Open Graph, etc.</p><h3>⚙️ 3. API Routes Built In</h3><p>Need a backend? A contact form? A webhook?</p><p>You don’t have to set up Express, deploy a server, or leave your project.</p><p>📁 Just drop this in:</p><pre>pages/api/submit.js</pre><p>And boom — you have an API route at /api/submit.</p><p>Use it for:</p><ul><li>Forms</li><li>Auth</li><li>Webhooks</li><li>Fetching external data</li></ul><p>✅ Fully serverless and deploys with your app. Clean. 🔥</p><h3>📦 4. Fullstack, But Not Frustrating</h3><p>With Next.js 13+ and the <strong>App Router</strong>, you get a modern fullstack experience:</p><ul><li>app/ directory with React Server Components (RSC)</li><li>Streaming with Suspense</li><li>Layouts + nested routes</li><li>Server-side actions (server.js functions inside components)</li></ul><p>It’s React + Backend + Deployment — all in <strong>one project</strong>.</p><p>No more:</p><ul><li>“Client side or server side?”</li><li>“Where do I fetch this?”</li><li>“Do I need Redux?”</li></ul><h3>🧠 5. Built for Performance and Developer Happiness</h3><p>Next.js comes with:</p><ul><li>Image optimization (next/image)</li><li>Font optimization</li><li>Automatic code splitting</li><li>Incremental Static Regeneration</li><li>Built-in ESLint, TypeScript, and Tailwind support</li></ul><p>It’s not just fast for users.<br> It’s <strong>fun</strong> for developers.</p><h3>🧱 6. Component + Page Design That Just Makes Sense</h3><p>React gave us components.</p><p>Next.js gave us <strong>page layouts</strong>, <strong>shared loading states</strong>, <strong>nested navigation</strong>, and clean project structure.</p><p>✅ Shared layout.js files for persistence<br> ✅ loading.js and error.js for every route<br> ✅ middleware.ts for auth, redirects, headers</p><p>It’s <strong>structured React</strong> — finally.</p><h3>🔐 7. Auth, Databases &amp; Deployments — All Play Nice</h3><p>Next.js plays well with:</p><ul><li><strong>NextAuth.js</strong> — Auth with providers (Google, GitHub, email, etc.)</li><li><strong>Prisma</strong> — Fullstack TypeScript ORM</li><li><strong>PlanetScale / Supabase / MongoDB Atlas</strong> — Easily plug in databases</li><li><strong>Vercel</strong> — One-click deployment, previews, edge functions</li></ul><p>The ecosystem is designed to <strong>work together</strong> — so you spend less time configuring, more time building.</p><h3>🛠️ 8. Real-World Use Cases</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RZLkCn4ul0OxxYc7" /></figure><p>What you can build with Next.js:</p><p>🛍 <strong>E-commerce store</strong> (with server actions &amp; dynamic routes)<br> 📰 <strong>Blog / CMS</strong> (using getStaticProps + Markdown + CMS)<br> 📊 <strong>Admin dashboards</strong> (with auth and server-rendered charts)<br> 📱 <strong>Landing pages</strong> (with perfect SEO and fast load times)<br> 👩‍💼 <strong>Portfolios</strong> (optimized images, animated routes, fast deployment)</p><p>All in one stack. All deployable in seconds.</p><h3>💬 9. So… Should You Learn Next.js in 2024?</h3><p>If you’re already using React and want to:</p><ul><li>Build faster apps</li><li>Have backend + frontend in one place</li><li>Rank on Google</li><li>Avoid routing and bundling headaches</li><li>Work on real-world projects or startup ideas</li></ul><p>Then YES — Next.js is one of the <strong>smartest skills</strong> to level up with. 📈⚛️</p><h3>✨ Final Thoughts — React Is the Engine. Next.js Is the Car. 🏎️</h3><p>React is powerful — but on its own, it’s just a view library.<br> Next.js is the glue. It brings everything together: SEO, routing, APIs, auth, deployment, performance — in one elegant package.</p><p>So if you’ve ever thought:</p><blockquote><em>“I wish React could just do more…”</em></blockquote><p>It can.<br> It does.<br> It’s called <strong>Next.js</strong>.</p><p>Welcome to the next level. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=098d614411fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node.js with WebAssembly in 2026]]></title>
            <link>https://medium.com/@fatima02/node-js-with-webassembly-in-2026-78645fb80071?source=rss-45010bb911c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/78645fb80071</guid>
            <category><![CDATA[webassembly]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Fatima✨]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 08:26:04 GMT</pubDate>
            <atom:updated>2026-01-22T08:26:04.229Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oG22dO2fDb37HXDV" /></figure><p>WebAssembly is a high-performance assembly-like language that can be compiled from various languages, including C/C++, Rust, and AssemblyScript. Currently, it is supported by Chrome, Firefox, Safari, Edge, and Node.js!</p><blockquote>The WebAssembly specification details two file formats, a binary format called a WebAssembly Module with a .wasm extension and corresponding text representation called WebAssembly Text format with a .wat extension.</blockquote><h3>Key Concepts</h3><ul><li>Module — A compiled WebAssembly binary, i.e. a .wasm file.</li><li>Memory — A resizable ArrayBuffer.</li><li>Table — A resizable typed array of references not stored in Memory.</li><li>Instance — An instantiation of a Module with its Memory, Table, and variables.</li></ul><blockquote>In order to use WebAssembly, you need a .wasm binary file and a set of APIs to communicate with WebAssembly. Node.js provides the necessary APIs via the global WebAssembly object.</blockquote><pre>console.log(WebAssembly);<br>/*<br>Object [WebAssembly] {<br>  compile: [Function: compile],<br>  validate: [Function: validate],<br>  instantiate: [Function: instantiate]<br>}<br>*/</pre><h3>Generating WebAssembly Modules</h3><p>There are multiple methods available to generate WebAssembly binary files including:</p><ul><li>Writing WebAssembly (.wat) by hand and converting to binary format using tools such as <a href="https://github.com/webassembly/wabt">wabt</a></li><li>Using emscripten with a C/C++ application</li><li>Using wasm-pack with a Rust application</li><li>Using AssemblyScript if you prefer a TypeScript-like experience</li></ul><blockquote><em>Some of these tools generate not only the binary file, but the JavaScript “glue” code and corresponding HTML files to run in the browser.</em></blockquote><h3><a href="https://nodejs.org/en/learn/getting-started/nodejs-with-webassembly#how-to-use-it">How to use it</a></h3><p>Once you have a WebAssembly module, you can use the Node.js WebAssembly object to instantiate it.</p><pre>// Assume add.wasm file exists that contains a single function adding 2 provided arguments<br>const fs = require(&#39;node:fs&#39;);<br><br>// Use the readFileSync function to read the contents of the &quot;add.wasm&quot; file<br>const wasmBuffer = fs.readFileSync(&#39;/path/to/add.wasm&#39;);<br><br>// Use the WebAssembly.instantiate method to instantiate the WebAssembly module<br>WebAssembly.instantiate(wasmBuffer).then(wasmModule =&gt; {<br>  // Exported function lives under instance.exports object<br>  const { add } = wasmModule.instance.exports;<br>  const sum = add(5, 6);<br>  console.log(sum); // Outputs: 11<br>});</pre><h3><a href="https://nodejs.org/en/learn/getting-started/nodejs-with-webassembly#interacting-with-the-os">Interacting with the OS</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sw7nl-NRFiirzMjB" /></figure><p>WebAssembly modules cannot directly access OS functionality on its own. A third-party tool <a href="https://docs.wasmtime.dev/">Wasmtime</a> can be used to access this functionality. Wasmtime utilizes the <a href="https://wasi.dev/">WASI</a> API to access the OS functionality</p><h3>Happy coding!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78645fb80071" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>