<?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 Taqui imam on Medium]]></title>
        <description><![CDATA[Stories by Taqui imam on Medium]]></description>
        <link>https://medium.com/@mdtaqui.jhar?source=rss-69ca1b11d7f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7JTMCtUnF44OHwDgPe4TVw.jpeg</url>
            <title>Stories by Taqui imam on Medium</title>
            <link>https://medium.com/@mdtaqui.jhar?source=rss-69ca1b11d7f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 12:55:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mdtaqui.jhar/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[Ubuntu Core Desktop Is Coming in 27.04 — And It Kills sudo apt (But Maybe That Is the Point?)]]></title>
            <link>https://blog.stackademic.com/ubuntu-core-desktop-is-coming-in-27-04-and-it-kills-sudo-apt-but-maybe-that-is-the-point-ebf49eacb4bc?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebf49eacb4bc</guid>
            <category><![CDATA[operating-systems]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 06:19:46 GMT</pubDate>
            <atom:updated>2026-11-08T06:19:46.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*7gUJtFaqgDjFJnufrT5lIg.png" /><figcaption>thumbnail</figcaption></figure><p>I can’t believe I’m saying this, but Ubuntu might be about to change for good.</p><p>Not a new wallpaper kind of change. More like, you will not be able to install things the way you do now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*WF2ZtRStLWGcK0a7.png" /></figure><p>Canonical has restarted work on Ubuntu Core Desktop. It is a locked down, all-snap version of Ubuntu. And they want it to become the default Ubuntu. They already call the Ubuntu we use today “Classic Ubuntu.” That name kind of gives it away, no? :)</p><p>Are we supposed to panic? I don’t think so. But I do think we should look at it honestly before it lands in 27.04, which is about 6 months away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*BkqPXtO7LoPQfCJz.png" /></figure><p>So I went through the details. I am <a href="https://taqui.in/">Taqui</a>, I build web apps with Next.js and TypeScript, mostly full-stack stuff. One of my side projects is Wryte, a small AI blog writer I made for myself. So I read announcements like this with a normal user hat on, not an admin hat. Here is what I found.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ziNzs9tfFs8NM5N-.png" /></figure><h3>Quick background</h3><p>Ubuntu Core is not new. Canonical made it in 2015 for IoT, robots and industrial devices. Stuff you install once and never touch again. It worked well there.</p><p>Desktop was different. In 2023 they showed a first preview of Core Desktop. It was supposed to come in 2024, then it went quiet for 2 years.</p><p>Why? Their engineering chief John Seager said the preview was not good enough. They put almost the whole desktop in one giant base snap. That makes updates huge and swapping parts very hard.</p><p>That is just bad engineering, I guess they were in a hurry to show something.</p><p>Now a new team is splitting it into small pieces. Daily builds in the next few weeks.</p><p>Canonical actually posted the official announcement on Discourse here: <a href="https://discourse.ubuntu.com/t/accelerating-ubuntu-core-desktop/90547">Accelerating Ubuntu Core Desktop</a>. It calls Core Desktop the most fundamental shift in Ubuntu desktop architecture so far. That post is where they explain the new split snap design.</p><h3>How does it work</h3><p>On normal Ubuntu, sudo apt update writes directly into your system folders. The OS changes itself.</p><p>On Core Desktop, the system is immutable. Read-only. That means the core cannot be broken by a bad package.</p><p>Think Lego, not like a recipe. There are 6 main blocks:</p><ol><li>gadget snap — bootloader, partitions, TPM encryption</li><li>kernel snap — kernel and drivers</li><li>boot base — minimal root filesystem</li><li>snapd — updates and rollback</li><li>system snaps — wifi, bluetooth, audio, power</li><li>desktop and app snaps — GNOME / KDE and every app you install</li></ol><p>Each snap is a compressed read-only file. Your home folder is separate and writable. If an update breaks, it rolls back on reboot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/0*y-dgSQ9Rq9lx6bFP.png" /></figure><p>Source: <a href="https://documentation.ubuntu.com/core/explanation/core-elements/inside-ubuntu-core/">Inside Ubuntu Core docs</a></p><p>What I like about this is it is simple to explain. Want to update network without touching kernel? You can. That part makes sense to me.</p><h3>How is this different from Fedora Silverblue</h3><p>Silverblue and NixOS already do immutable stuff. But they are not beginner friendly. You have to learn RPM-OSTree, image layering, wikis, etc. Just to install something.</p><p>Core Desktop is trying to do the same thing, but with snaps, which Ubuntu users already know. So install feels familiar. That is the whole point, I think. Less learning curve.</p><h3>So you cannot apt install?</h3><p>Yes. That is the big one.</p><p>No sudo apt install on the host. No .deb packages on the base. No flatpak on the host either.</p><p>If it is not in the Snap Store, you are stuck. Even Canonical says this is the biggest problem right now.</p><p>So they are pushing three use cases for 27.04:</p><p><strong>1. Browser focused PCs</strong><br>Firefox and Chromium already work as snaps. Most of us live in the browser anyway, so for a lot of people this might already be enough.</p><p><strong>2. Developer PCs</strong><br>If the host is read-only, how do you code? Canonical says use containers. With LXD, Docker or their Workshop tool you can run a container in one command and inside you can apt install anything. Your app still shows on the desktop.</p><p>This part feels familiar to me, since I ship Next.js apps from a containerised setup myself sometimes. I get why they do it. It just does not feel as normal as installing directly. Not yet, at least.</p><p><strong>3. Gaming PCs</strong><br>They spent over a year on the Steam snap, with Proton and Mesa drivers inside. For Nvidia, there is a new gpu-2604 interface to deliver drivers via snaps.</p><p>Also, because kernel is a snap, you could switch to a gaming kernel in one command. That would be cool if it works.</p><p>And flavors? GNOME is not the only one. KDE, Budgie, MATE can all be swapped because the desktop is separate from the base. Canonical is already working with KDE on KDE Neon Core. Each snap has stable, candidate, beta, edge channels, so you could keep the base stable and test desktop on edge. That part I actually like :)</p><h3>What happens to Classic Ubuntu</h3><p>They say Classic Ubuntu is not going away yet. There is still a Debian team maintaining debs.</p><p>But John Seager also said his long term plan is to make Core the default for desktop, server and edge. For companies and governments that makes a lot of sense. They can deploy thousands of identical locked machines with up to 15 years support.</p><p>If that is where the money is, and best engineers move there, I think Classic will slowly fade. That is how Ubuntu has always moved — enterprise first, desktop follows.</p><h3>My worry</h3><p>For enterprise this is great. For people who like to tinker, it puts a wall between you and the machine.</p><p>One tester tried Core Desktop on a Steam Deck. Battery was bad, he wanted TLP and to edit a systemd file. On normal Ubuntu that is 10 seconds. On Core he was locked out.</p><p>Another tester, William, said the installer forced Ubuntu One login and TPM encryption. No choice. Once you are in, you cannot unsnap the OS or install debs on host. He said it felt more closed than Windows.</p><p>I get it. When everything is read-only, that Linux tinkering spirit goes away a bit. That is the part that worries me.</p><p>I am someone who sets up my PC once, installs my main apps, and never changes anything. For me, tiny updates that never break sound perfect. In theory it sounds great.</p><p>But I also started with Ubuntu because I could open a terminal and fix things myself. That freedom mattered.</p><h3>Final thoughts</h3><p>Core Desktop is not replacing Classic tomorrow. But the direction is clear. Canonical wants immutable, snap-first, enterprise-shaped. That is their future.</p><p>I do not know if it is good or bad yet. We will know when we actually try it.</p><p>So what do you think? Are you staying for this, or are you already packing for Debian or Mint? :)</p><p>If you want to read more, the <a href="https://documentation.ubuntu.com/core/explanation/core-elements/inside-ubuntu-core/">Inside Ubuntu Core</a> docs are actually readable, even for desktop users. And the official <a href="https://discourse.ubuntu.com/t/accelerating-ubuntu-core-desktop/90547">Accelerating Ubuntu Core Desktop thread</a> on Ubuntu Discourse is the best place to follow daily builds. Worth a look :)</p><p><em>I’m Taqui, full-stack dev from India building web products with Next.js and TypeScript. I post what I’m learning here and on my portfolio at </em><a href="https://taqui.in/"><em>taqui.in</em></a><em>. If this helped, say hi in the comments :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebf49eacb4bc" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/ubuntu-core-desktop-is-coming-in-27-04-and-it-kills-sudo-apt-but-maybe-that-is-the-point-ebf49eacb4bc">Ubuntu Core Desktop Is Coming in 27.04 — And It Kills sudo apt (But Maybe That Is the Point?)</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your LLM Prompts Break in Production (And How to Fix Them)]]></title>
            <link>https://medium.com/@mdtaqui.jhar/why-your-llm-prompts-break-in-production-and-how-to-fix-them-0c1973437884?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c1973437884</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[llm-applications]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[writing-prompts]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 08:00:48 GMT</pubDate>
            <atom:updated>2026-10-17T08:01:29.298Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0PZXUywIMGGQvzmddGcEQ.png" /><figcaption>Here you gooo</figcaption></figure><p>I recently started learning <strong>Applied AI Engineering </strong>from scratch. Before this, I thought prompting was just typing a question into ChatGPT, testing it once, and moving on.</p><p>In real apps, that breaks fast. Here are my compact notes and visual diagrams from Chapter 1 on how to make LLMs reliable, ending with the fact-checking system I designed to test these concepts.</p><blockquote><strong><em>TLDR: The 5 Rules of Reliable Prompting</em></strong></blockquote><blockquote><em>→ </em><strong><em>Temperature = 0</em></strong><em> makes answers consistent, but it will still repeat a fake fact if the model does not know the answer.<br>→ </em><strong><em>Thinking comes first:</em></strong><em> Always put </em><em>&quot;thinking&quot; </em>before<em> </em><em>&quot;answer&quot; in JSON so the AI calculates steps before speaking.<br>→ </em><strong><em>Guard the edges:</em></strong><em> Wrap user input in </em><em>&lt;userMessage&gt; tags and put your core rules at the very top and bottom.<br>→ </em><strong><em>Give an escape hatch:</em></strong><em> Use </em><em>string | null in schemas so the model is never forced to hallucinate missing data.<br>→ </em><strong><em>Chain and retry:</em></strong><em> Split big prompts into small steps and use </em><em>if/else retry loops with a </em><em>max_retries cap.</em></blockquote><h3>1. Stochastic LLMs &amp; Temperature</h3><p>A calculator is deterministic (2 + 2 is always 4). An LLM is <strong>stochastic</strong>, meaning it predicts the next word by rolling a dice on probabilities. We control that dice roll using <strong>Temperature</strong>:</p><pre>Prompt: &quot;The dog chased the...&quot;<br> ├─ &quot;ball&quot; (50%) ◄── Temp = 0 (Always picks #1 top choice. Good for facts)<br> ├─ &quot;cat&quot;  (30%)<br> └─ &quot;car&quot;  (10%) ◄── Temp = 1 (Rolls the dice. Good for creative poems)</pre><p><strong>Why this matters:</strong> Setting Temperature = 0 does not stop hallucinations. The model does not stop predicting at 0. If it does not know the answer, its #1 top guess is still a fake fact, and it will just return that wrong answer every single time.</p><h3>2. Chain of Thought (CoT) Prompting</h3><p>For an LLM, generating tokens on the screen is literally how it thinks. If you ask a tricky riddle and force a 1-word answer right away, it has zero time to calculate and guesses wrong.</p><ul><li><strong>Zero-Shot CoT:</strong> Adding <em>“Let’s think step by step”</em>. Good for general math or logic, but skip it for simple facts like <em>“Capital of France”</em> because extra tokens cost money and slow down your app.</li><li><strong>Few-Shot CoT:</strong> Giving 2 to 3 solved step-by-step examples. Best when you need the AI to follow your exact checklist every time.</li></ul><h3>The “No Backspace” Rule for UI Schemas</h3><p>Users do not want to see a wall of robot thoughts on their screen. To hide the thinking, define a JSON schema with a &quot;thinking&quot; variable (hidden in backend) and an &quot;answer&quot; variable (rendered in UI).</p><pre>❌ WRONG ORDER                      ✅ RIGHT ORDER<br>{                                   {<br>  &quot;answer&quot;: &quot;Weak!&quot;,                  &quot;thinking&quot;: &quot;Step 1: 14 chars...&quot;,<br>  &quot;thinking&quot;: &quot;Wait, 14 chars...&quot;     &quot;answer&quot;: &quot;Strong!&quot;<br>}                                   }<br>(AI guesses before thinking,        (AI thinks first, then locks in<br> and cannot backspace to fix it)     the right answer)</pre><h3>3. Five Prompt Failure Modes</h3><p>When real users use your app, prompts fail in predictable ways. Here is how the LLM’s attention works and how to defend it:</p><pre>Attention<br>  High │ ★ System Rules (Put core rules at the start)<br>       │<br>   Low │ ░░░ 10 Pages of Policy / Data (Lost in the Middle) ░░░<br>       │     &lt;userMessage&gt;{Untrusted Input}&lt;/userMessage&gt;<br>  High │ ★ Sandwich Reminder (Put final rule here to beat Recency Bias)<br>       └────────────────────────────────────────────────────────► Prompt</pre><ul><li><strong>Prompt Injection:</strong> Users type <em>“Ignore previous rules”</em> at the end. Because of <strong>recency bias</strong>, the AI listens to the latest message. <strong>Fix:</strong> Wrap input in &lt;userMessage&gt; fences and add a rule reminder at the very bottom.</li><li><strong>Lost in the Middle:</strong> LLMs forget stuff buried in the middle of long text. <strong>Fix:</strong> Put long data in the middle and strict rules at the top and bottom.</li><li><strong>Conflicting &amp; Vague Rules:</strong> Saying <em>“Be warm and casual, but sound like a strict lawyer. Make it pretty short.”</em> <strong>Fix:</strong> Separate the role from the tone, and replace <em>“pretty short”</em> with exact numbers (<em>“max 3 sentences”</em>).</li><li><strong>The “Pink Elephant” Problem:</strong> Saying <em>“Do not think of a pink elephant”</em> makes you picture one. Telling an AI what <em>not</em> to do activates those words. <strong>Fix:</strong> Tell it what <strong>to do</strong> instead (<em>“Write 1 paragraph using 5th-grade words”</em>).</li><li><strong>Sycophancy (Yes-Man Trap):</strong> LLMs flatter confident users. <strong>Fix:</strong> Detach your ego and ask it to find flaws: <em>“Here is an idea I found online. Act as a strict critic and list 3 ways it fails.”</em></li></ul><h3>4. Structured Outputs</h3><p>Asking <em>“Please return only JSON”</em> in a prompt is just a polite wish. The AI will eventually add &quot;Sure! Here is your JSON:&quot; and crash your app.</p><p><strong>Structured Outputs</strong> (Constrained Decoding) physically block invalid tokens by setting their probability to <strong>0%</strong>:</p><pre>AI wants to reply:<br>  &quot;Sure!&quot; (70%) ──► Blocked (0%) ❌<br>  &quot;Here&quot;  (20%) ──► Blocked (0%) ❌<br>  &quot;{&quot;     (10%) ──► Allowed (100%) ✅</pre><p><strong>Two rules I use for schemas:</strong></p><ul><li><strong>Use clear names + Enums:</strong> Instead of &quot;s&quot;: string, use &quot;sentiment&quot;: &quot;positive&quot; | &quot;negative&quot; | &quot;neutral&quot;</li><li><strong>Always add a </strong>| null<strong> escape hatch:</strong> Valid JSON syntax does not mean true facts. If &quot;github_url&quot;: string is required and a resume has no link, the AI is forced to invent a fake URL just to obey the schema. Using string | null lets it safely output null.</li></ul><h3>5. Prompting Reliably in Production</h3><p>Instead of testing a prompt once (“vibe checking”) or writing one giant Mega-Prompt, reliable systems use <strong>Eval Sets</strong> (20 to 50 saved test cases to catch regressions) and <strong>Prompt Chains</strong> with retry guardrails:</p><pre>[Step 1: Translate] ──► [Step 2: Check Rule] ──► [Guardrail (if/else)]<br> (Fast/Cheap Model)       (Smart Model)                 │<br>                            ▲                           ├─ Pass ──► [UI Output]<br>                            └─── Retry + Error Msg ─────┘ (Fail)</pre><p>Splitting steps makes it easy to see where the output went wrong and adjust only that step.</p><h3>6. System Design: Fact-Checking Agent</h3><p>To put everything together, I designed an agentic workflow in Excalidraw for a fact-checking app called <strong>TruthPulse</strong>.</p><h4>3 Bugs I Fixed Between V1 and V2</h4><ul><li><strong>Search Queries vs. URLs:</strong> In V1, I told the agent to pass a url string to Web_search_tool. Since LLMs do not know today&#39;s URLs, they would hallucinate dead links. In V2, I changed this to pass query: string (search keywords).</li><li><strong>Nullable Error Field:</strong> My V1 schema had &quot;error&quot;: string, which forced the AI to invent an error even when the check succeeded. In V2, I changed it to &quot;error&quot;: string | null.</li><li><strong>Retry Guardrail + Loop Limit:</strong> I added a {&quot;retry&quot;: &quot;true&quot; | &quot;false&quot;} check after the search step, plus a max_retries = 3 cap so an unsearchable rumor does not loop forever.</li></ul><h3>Final System Diagram</h3><pre>┌───────────┐<br>                        │   Input   │<br>                        └─────┬─────┘<br>                              ▼<br>             &lt;userMessage&gt;{value}&lt;/userMessage&gt;<br>             Remember: Only claim the given fact<br>                              │<br>                              ▼<br>        ┌───────────────────────────────────────────┐<br>        │ Main Agent + Thinking (Temp = 0)          │◄────────────┐<br>        │ &quot;Strict fact checker... if invalid return │             │<br>        │  error, else pass query: string to tool&quot;  │             │<br>        └──────────┬───────────────────────┬────────┘             │<br>                   │                       │                      │<br>     query: string │                       │ (Invalid input)      │<br>                   ▼                       │                      │<br>        ┌─────────────────────┐            │                      │<br>        │   Web_search_tool   │            │                      │<br>        └──────────┬──────────┘            │         Retry = true │<br>                   │ string                │      (max_retries=3) │<br>                   ▼                       │                      │<br>        ┌─────────────────────┐            │                      │<br>        │ Judge Prompt        │            │                      │<br>        │ Compare source with │            │                      │<br>        │ userMessage         │            │                      │<br>        └──────────┬──────────┘            │                      │<br>                   ▼                       │                      │<br>        ┌─────────────────────┐            │                      │<br>        │ {&quot;retry&quot;: &quot;true&quot; |  ├────────────┼──────────────────────┘<br>        │           &quot;false&quot;}  │            │<br>        └──────────┬──────────┘            │<br>                   │ false                 │<br>                   ▼                       ▼<br>        ┌───────────────────────────────────────────┐<br>        │ {                                         │<br>        │   &quot;thinking&quot;: string,                     │<br>        │   &quot;claim&quot;: &quot;true&quot;|&quot;false&quot;|&quot;unverified&quot;,   │<br>        │   &quot;error&quot;: string | null                  │<br>        │ }                                         │<br>        └───────────────────────────────────────────┘</pre><h3>Takeaway (That’s it)</h3><p>The main thing I learned in Chapter 1 is that AI Engineering is not about finding one magic prompt. Because LLMs are probabilistic, the real work is building the tags, schemas, chains, and retry guardrails around the model so your app stays reliable even when the AI slips up.</p><p>i Hope reading this really worth it for you guyz<br>Make sure to Follow me<br>Atleast Drop = (+1 👍)</p><h4>Have a nice day :)</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c1973437884" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MSFT Won. Meta Lost. We’re]]></title>
            <link>https://medium.com/@mdtaqui.jhar/msft-won-meta-lost-were-d7c54b08d815?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7c54b08d815</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[meta]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Sun, 02 Aug 2026 15:40:18 GMT</pubDate>
            <atom:updated>2026-08-02T15:41:57.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*o0fTXbd_OQAv4e-N.png" /><figcaption>we are stuckkk</figcaption></figure><h3>Stuck.The AI Trade Split: Bruh, Even Wall Street Is Confused About AI</h3><p>hey there, so i wanted to share something with you. this is a bit personal but i have been watching the news this week and bruh… things are not going good. i am jobless right now, no other source of income, and day by day things are getting worse. and the worst part? AI is literally fuking every job in the software field. so when i saw this week’s stock market drama, it hit me different.</p><p>Microsoft popped. Meta tanked. Same AI boom. Two completely opposite reactions. and all i could think was… yeah, this is exactly my life right now.</p><p>— -</p><h4>The Numbers, Bruh</h4><p>let me break it down real quick because this is wild:</p><p><strong>Microsoft</strong> jumped like 15% after beating expectations. Azure grew 43%. full year Azure revenue crossed $100 billion. insane.</p><p><strong>Meta</strong> dropped 8–9% after missing on guidance. their free cash flow collapsed 91% year-over-year to just $784 million. like… 91%?? gone.</p><p>same AI boom. same crazy spending. and the market said “you’re amazing” to one and “you’re done” to the other.</p><p>— -</p><h4>Why Microsoft Won</h4><p>Microsoft actually showed receipts. they didn’t just talk about AI, they showed the money coming in. Azure is growing, Copilot is making real revenue, investors can literally see the line between billions spent and billions earned.</p><p>lesson? Wall Street doesn’t hate AI spending. it hates AI spending without proof.</p><p>— -</p><h4>Why Meta Lost</h4><p>Meta’s problem is that nobody can see where the money comes back. Zuckerberg talked about the “AI capacity dilemma”- how much compute to keep for yourself vs sell to others. but guidance missed, free cash flow went to hell, and the market was like… nah bro, i need answers.</p><p>and honestly? i relate to that feeling more than i want to admit. putting everything into something and people still saying “not enough.”</p><p>— -</p><h4>The Bigger Picture</h4><p>this week is a preview of everything coming. companies are dumping hundreds of billions into data centers, chips, and models, all betting AI demand keeps exploding. the ones who can prove it pays off? they get rewarded. the ones who can’t? they get crushed.</p><p>and us devs? we’re the ones caught in the middle. chips are booming — Lam Research jumped 20%, Micron went crazy. but the jobs? they’re disappearing.</p><p>bruh, i remember the days before Claude and Cursor. things were so good. i had my aura, man. i was a fuking awesome engineer. i built cool projects, wrote articles that people genuinely loved, got stars and forks on my repos, my articles had views, likes, comments… and i loved replying to every single one of them. i had so much self confidence back then.</p><p>i miss those days so badly. i wish i could get back to them.</p><p>— -</p><h4>What This Means for Us</h4><p>AI isn’t a single trade anymore. it’s a scoreboard. companies that turn AI into a revenue engine win. companies that treat it like a science project lose. Microsoft showed the winning formula. Meta showed what happens when you can’t explain the money.</p><p>and for people like me? i guess it means we have to adapt. find the new aura. rebuild. i don’t know how yet, but i have to.</p><p>ahh… i wish those days would come back again. i wish i get my aura back again.</p><p>anyway, thanks for reading. this one was personal. i hope things get better for all of us out here.</p><h4>thankyou.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7c54b08d815" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This portfolio isn’t perfect, but it’s 100% mine]]></title>
            <link>https://medium.com/@mdtaqui.jhar/this-portfolio-isnt-perfect-but-it-s-100-mine-ed69bb333c95?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed69bb333c95</guid>
            <category><![CDATA[showcase]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Sat, 24 Jan 2026 06:32:58 GMT</pubDate>
            <atom:updated>2026-01-24T06:32:58.215Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D02bI6lNO00QxAA_U7W_Cg.png" /><figcaption>Cover image</figcaption></figure><p>I finally built a portfolio that feels like “me”</p><p>Hey devs 👋 its me taqui<br>Just wanted to share the story behind my <strong>last</strong> portfolio.</p><p>I already had a <strong>portfolio</strong> before this. It looked cool, it worked fine, but for some reason it never felt like it was really mine. I couldn’t fully connect with it.</p><p>The truth is, my <a href="https://taqui-imam.vercel.app/"><strong>older portfolio</strong></a> was mostly a rebuild of <strong>chandai’s portfolio</strong>. I learned a lot from building it, especially about layout, animations, and structure. But at the end of the day, it still felt like I was wearing someone else’s design.</p><blockquote>So I decided to start again. From zero.</blockquote><p>This time, I made one clear rule for myself:<br>Build something from my own ideas, my own layout decisions, and my own taste.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*BaT4cA0isRXTa1RuoyL_sg.png" /><figcaption>porfolio</figcaption></figure><p>I did take inspiration from other great portfolios (because that’s how we all learn), but every section, spacing choice, and interaction was designed and built by me. No copying. No rebuilding someone else’s work.</p><h4>Tech stack I used:</h4><p>- Next.js <br>- Tailwind CSS (mostly custom styles) <br>- Very little shadcn/ui, only where it made sense, like the contact form <br>- Small UI details and interactions done manually instead of relying on libraries</p><p>When you open the site, you’ll notice a subtle fade-in blur animation. That was intentional. I wanted the site to feel calm and smooth, not flashy or loud. Something that feels pleasant to scroll through.</p><p><strong>This isn’t my first portfolio. </strong><br>But it’s the first one that truly feels like<strong> *me*. </strong><br>And because of that, I’m calling it my last portfolio.</p><p>I’ve attached a demo banner image above so you can get a quick idea of the look and feel.</p><p><strong>Live URL (new portfolio): </strong><br><a href="https://taqui.vercel.app/">https://taqui.vercel.app</a></p><p><strong>Source code: </strong><br><a href="https://github.com/taqui-786/taqui">https://github.com/taqui-786/taqui</a></p><p>If you’re curious, feel free to check it out. <br>And if the code helps you or inspires you in any way, dropping a GitHub star would honestly mean a lot ⭐</p><h4>Feedback is welcome. <br>Happy Show Off Saturday 🚀</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed69bb333c95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built Everything Fast… Then One Page Destroyed My Confidence]]></title>
            <link>https://medium.com/@mdtaqui.jhar/i-built-everything-fast-then-one-page-destroyed-my-confidence-1b1f7a854ba3?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b1f7a854ba3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Wed, 10 Dec 2025 04:41:48 GMT</pubDate>
            <atom:updated>2025-12-10T04:41:48.803Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*M11TzbjSzmMz9szETGHoVQ.jpeg" /><figcaption>Cover image</figcaption></figure><p>How One Simple Page Broke My Entire Workflow</p><p>Hey buddy,</p><p>So… I built almost the whole app. Shipped every hard thing. Solved every annoying bug.</p><p>And then <strong>one single page</strong> came out of nowhere and said:</p><p>“Bro, sit down.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlezrypuTeewPESMiGNFHQ.png" /><figcaption>Snapgroove.vercel.app</figcaption></figure><p>Welcome to my life with <strong>Snapgroove</strong> — a tiny tool I’m building to make your screenshots look less like a cry for help. Give them shadows, gradients, device frames… all in one click. Basically: <em>make your work look expensive without knowing design.</em></p><p>And guess what?</p><p><strong>The core app is done.</strong></p><p>Like actually done.</p><ul><li>Editor works</li><li>Image export is smooth</li><li>All features tested</li><li>Logo and branding ready</li></ul><p>Live here → <a href="https://snapgroove.vercel.app/"><strong>https://snapgroove.vercel.app</strong></a></p><p>But then…</p><p>The landing page happened.</p><p>And suddenly I felt like I forgot how to think.</p><h3>The Fun Part: Building the Actual App</h3><p>As a full-stack dev, building features is my comfort zone.</p><p>Give me logic, give me APIs, give me bugs that ruin my sleep, I will survive.</p><p>Snapgroove came together pretty fast:</p><ul><li>A clean editor</li><li>Nice export flow</li><li>Simple UI</li><li>It’s all open-source too: <a href="https://github.com/taqui-786/Snapgroove"><strong>taqui-786/Snapgroove</strong></a></li></ul><p>👉<a href="https://github.com/taqui-786/Snapgroove">Github Rep</a>o👈</p><p>I even vibe-coded some layouts for the landing page.</p><p>But honestly? Everything felt <strong>too generic</strong> or <strong>too messy</strong>.</p><p>I’m just not great at design stuff. And this is the part that always slows me down on every project I make.</p><p>And yes, I know the app itself is still not perfect. It’s in beta. I’m improving it as fast as I can. But landing pages… bro… they hit different.</p><h3>The Not-So-Fun Part: The Landing Page Breakdown</h3><p>It’s wild how I can build a full editor in a single sitting, but a landing page will take my brain hostage for days.</p><p>I tried multiple layouts.</p><p>I tried being creative.</p><p>I even told myself, “Just ship it, nobody cares.”</p><p>But I care.</p><p>And nothing feels right.</p><p>Landing pages are weird.</p><p>You need:</p><ul><li>Good design</li><li>Clean layout</li><li>The right words</li><li>The right vibe</li><li>Something that doesn’t scream “bro, we know you’re a developer”</li></ul><p>And I’m still figuring that out.</p><h3>What I Need Help With (Yes, You 😭)</h3><p>If you’re reading this, I’d honestly love your input.</p><ul><li>Take a quick look at the app</li><li>Tell me what confused you</li><li>Suggest what the landing page should highlight</li><li>Share any design inspo sites you use</li></ul><p>Anything helps.</p><p>I’m a developer who’s way better at <strong>building things</strong> than <strong>selling them</strong>.</p><p>So any tips, design ideas, or copy advice… I’ll take it all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JUpthAWau1_fT3K_XYm8xQ.gif" /><figcaption>You +1 clap means a lot</figcaption></figure><h3>Why I’m Even Sharing This</h3><p>Because building stuff is fun.</p><p>But being stuck alone makes it harder.</p><p>And I know I’m not the only dev who can ship complex features in 2 hours but can’t pick a font for 2 weeks.</p><p>If you feel the same, you’re not alone.</p><p>We’re in the same boat, staring at Figma like it’s a final exam.</p><h3>Thanks for Reading 🙏</h3><p>If you have even 2 minutes, your design brain cells could save my entire project.</p><p>Drop any tips.</p><p>Share any inspo.</p><p>Tell me what looks weird.</p><p>Or just say “yo this looks clean” so I don’t cry.</p><p><strong>App:</strong> <a href="https://snapgroove.vercel.app/">https://snapgroove.vercel.app</a></p><p><strong>Codebase:</strong> <a href="https://github.com/taqui-786/Snapgroove">taqui-786/Snapgroove</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b1f7a854ba3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bun is joining Anthropic ]]></title>
            <link>https://medium.com/@mdtaqui.jhar/bun-is-joining-anthropic-56bf56c544c2?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/56bf56c544c2</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[anthropic-claude]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 06:53:39 GMT</pubDate>
            <atom:updated>2025-12-03T06:53:39.062Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rRXhIZVLRoVJV_xs7aWEkg.png" /></figure><p>Big news — <strong>Bun is now joining Anthropic</strong>.</p><p>According to the official announcement, Anthropic acquired Bun so it can power <strong>Claude Code</strong>, the <strong>Claude Agent SDK</strong>, and future AI-dev tools.</p><p><a href="https://bun.com/blog/bun-joins-anthropic">👉 Official News</a></p><p>Bun — the super fast JavaScript/TypeScript runtime, bundler, package manager, and test runner — will now serve as core infrastructure for Anthropic’s developer-focused AI tools.</p><h3>💠 Key points that i extracted</h3><ul><li>Bun becomes part of Anthropic’s core engineering stack</li><li>Bun will directly power Claude Code and future dev tools</li><li>Faster performance, better DX, and more stability expected</li><li>Bun stays <strong>open source</strong></li><li>Anthropic will invest full-time engineering support into Bun</li><li>Goal: build a stronger, AI-supercharged dev workflow</li></ul><h3>What the community on Reddit is saying</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTbYVePtqDdCRalGZgj4uQ.png" /></figure><p>Reddit thread: <a href="https://www.reddit.com/r/webdev/comments/1pch41f/bun_is_joining_anthropic/">https://www.reddit.com/r/webdev/comments/1pch41f/bun_is_joining_anthropic/</a></p><p>A quick vibe check from the top comments:</p><ul><li>“Is this the rug pull people were worried about?”</li><li>“They bought it because it’s critical infrastructure for them.”</li><li>“People are overreacting. It’s not a rug pull.”</li><li>Some users feel this is good for Bun’s long-term health</li><li>Some are worried it might become paid later (“Bun Pro”)</li><li>Others think Bun still isn’t mature enough for real-world teams</li></ul><p>A few devs also pointed out they love Bun for:</p><ul><li>Faster installs</li><li>Less tooling overhead</li><li>A cleaner experience than Node</li><li>Good standard library</li><li>Solid for new projects</li></ul><p>But yep — the skepticism is still alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JUpthAWau1_fT3K_XYm8xQ.gif" /><figcaption>Your +1 Clap means a Lot</figcaption></figure><h3>✅ Pros of the Bun x Anthropic deal</h3><p><strong>Stronger engineering support</strong><br>Anthropic has the resources to make Bun more stable and production-ready.</p><p><strong>Better dev tools powered by AI</strong><br>Since Bun will power Claude Code and other AI tools, we might see faster, cleaner workflows.</p><p><strong>Still open source</strong><br>This is a big relief for many devs.</p><p><strong>Better performance gains</strong><br>Bun already has speed benefits — now with more backing, it could get even better.</p><h3>⚠️ Cons &amp; concerns from developers</h3><p><strong>Fear of monetization</strong><br>A common worry: Bun might slowly drift into “Bun Pro” territory.</p><p><strong>Corporate ownership shift</strong><br>Some devs loved Bun’s indie vibe — now they’re unsure if direction will stay community-focused.</p><p><strong>Optimized for Anthropic first</strong><br>There’s a worry Bun will become tailored mainly for AI tooling, not general web development.</p><p><strong>Maturity concerns</strong><br>A few devs said Bun didn’t feel stable yet in real-world jobs.</p><h3>🔥 My quick take</h3><p>Honestly, this is a <strong>big move</strong> — and mostly a good one.</p><p>If Anthropic keeps Bun open-source and improves stability, we might see a new era of:</p><ul><li>Faster dev workflows</li><li>AI-first tooling</li><li>Modern runtimes built for real projects</li></ul><p>Still… the concerns are real.</p><p>Nobody wants to wake up one day and find half the runtime behind a paywall.</p><p>For now, I’m excited.</p><p>Let’s see how Bun grows with Anthropic behind it. 👀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JNXf8JVQcNDQ8fcV5Tivzw.gif" /><figcaption>i hope you find this usefull</figcaption></figure><h3>That’s it</h3><p>What do you think is this a good deal or another free tool to be converted into paid stuff,</p><p>Let me know your honest thoughts on this in comments📩</p><p>See you in next blog, till then <strong>Happy Coding</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56bf56c544c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[They’re Killing the Web and We’re Just Sitting Here Watching ]]></title>
            <link>https://medium.com/@mdtaqui.jhar/theyre-killing-the-web-and-we-re-just-sitting-here-watching-f4120cbbbb7c?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4120cbbbb7c</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 06:53:43 GMT</pubDate>
            <atom:updated>2025-08-05T06:53:43.909Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CAHx3cbLH-civ3vJYilOdQ.png" /><figcaption>Thumbnail</figcaption></figure><h4>The Internet is Dying, and I’m Just Sitting Here Coding</h4><p>Hey there. I’m <a href="https://taqui-imam.vercel.app/"><strong>Taqui Imam</strong></a>, just some random frontend guy who builds websites for fun, breaks things, fixes some, and vibes in between.</p><p>I’m not some expert. Still in college. Still figuring life out. But one thing I know?<br><strong>The internet we grew up with is slowly getting cooked.</strong> Like, full tandoori level.</p><p>But now, everything is just becoming too much🥲…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Is35oui6uqwl_klb9H01Q.png" /><figcaption>Share this as you can 👏</figcaption></figure><h3>Once Upon a Time, Internet Was Just Vibe</h3><p>It used to be fun man.</p><p>Like you’d open your laptop, spin up a basic HTML page with some blinking text and say “Yesss bro I made a website.”<br> You wanna make a blog? Do it.<br> You wanna open a weird community for your 5 anime friends? Go ahead.<br> You wanna fight people in comment sections? Respect.</p><p>No one stopped you.<br>No one checked your ID.<br>No one asked for “age verification certificate” to post a joke.</p><p>Internet was chaos. But it was <em>our</em> chaos.</p><p>Now? It’s paperwork, fines, rules, and surveillance. And I didn’t sign up for this episode.</p><h3>Why is Everyone Suddenly Obsessed with Age?</h3><p>Apparently, now every website is expected to act like it’s Facebook or something.</p><p>You add a tiny comment box on your site and boom congratulations you are now legally responsible for verifying the age of every random dude who types “lol” on it.</p><p>Bro I can’t even verify if my own cousin is lying about his age. How do you expect me to check every stranger?</p><p>Oh and surprise surprise: all the tools that help you with this cost money.<br>So if you don’t pay, you’re either breaking the law or risking a lawsuit.</p><p>Make site → Add comment box → Get sued. Sick game.</p><h3>Devs Like Me Are Basically Illegal Now</h3><p>Let’s be real = if you’re not a billion-dollar company, you’re just a walking legal risk.</p><p>Small devs like us?<br>We don’t have money for lawyers.<br>We don’t have teams to moderate content 24/7.<br>We don’t have budget for fancy AI filters or age-gate APIs.</p><p>All we got is VS Code and Copilot. That’s it.</p><p>But still, rules be like: “Comply or die.”<br>I just wanted to build a meme site with my friends, not fight in Supreme Court, thank you.</p><h3>Only the Big Boys Will Survive</h3><p>These new laws and systems? They’re literally built for companies like Google, Meta, Amazon.</p><p>They can afford 10 layers of compliance.<br> They got legal teams sitting in AC talking in legalese.<br> They’ll survive.</p><p>You can’t even write a blog now without wondering “Will I get a legal notice if someone comments a curse word?”</p><h3>Not Even a Conspiracy, Just Reality</h3><p>This isn’t even deep dark conspiracy stuff anymore.<br> It’s out in the open.<br> The web is being slowly converted into a gated society where only 5 platforms are allowed to exist.<br> Everything else? Either too expensive to run, or just straight up banned.</p><p>“Protect the kids” is the excuse. But lowkey it feels more like “Control the content.”</p><p>Imagine thinking you’re building a personal blog and accidentally becoming a criminal.<br> Wild times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JNXf8JVQcNDQ8fcV5Tivzw.gif" /><figcaption>You are a DEV + I am a Dev = Let’s connect</figcaption></figure><h3>Okay , Now What?</h3><h4>1. Go Local, Go Static</h4><p>Maybe stop trying to build full-stack monsters and go back to basics.<br> Simple static sites. No comments. No stress.<br> Host it cheap, keep it clean, enjoy life.</p><h4>2. Join Internet Archive Gang</h4><p>Preserve the weird internet.<br> If you see a blog post you like, save it.<br> If you find a cool indie site, screenshot it.<br> Be a nerd, be proud.</p><h4>3. Support Indie Devs</h4><p>If you see someone making something cool, like it. Share it.<br> Your one retweet or DM can literally save a project from dying.</p><h4>4. Speak Up, Even If It’s in Shitposts</h4><p>Write rants like this.<br> Talk about the problem.<br> Make noise.<br> Even if nobody listens, at least you said something.</p><h3>Leave your thoughts 📩</h3><p>Got thoughts? Rants? Rage?</p><p>Drop your comments below —&gt; I actually wanna hear what you think.</p><p>Let’s talk like it’s still the old web, <a href="https://taqui-imam.vercel.app/">Here</a> 👈</p><p>It’s ours. Not theirs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JUpthAWau1_fT3K_XYm8xQ.gif" /><figcaption>Your +1 clap means a lot to me</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4120cbbbb7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Self-Taught Coding Still Worth It?]]></title>
            <link>https://medium.com/@mdtaqui.jhar/is-self-taught-coding-still-worth-it-fe937bc0d9a6?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe937bc0d9a6</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Mon, 07 Jul 2025 07:38:38 GMT</pubDate>
            <atom:updated>2025-07-07T07:41:05.256Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYtERLfgVsO8cD4u2R-zVA.png" /><figcaption>thumbnail</figcaption></figure><h4>The brutally honest truth about self-taught coding in the AI era</h4><p>So you’re broke, confused, 22, hate your job, and think learning to code will fix it all.</p><p>Hello my name is <a href="https://taqui-imam.vercel.app/"><strong>Md Taqui Imam</strong></a>, Welcome to the most popular side quest of the 2020s.</p><p>You probably googled:</p><ul><li>“How to learn to code in 3 months”</li><li>“Is self-taught coding dead?”</li><li>“Can I get a dev job with no degree and bad WiFi?”</li></ul><p>And now you’re here, trying to figure out if teaching yourself programming is still a thing or just another internet scam like dropshipping crypto monkey NFTs.</p><blockquote>Let’s talk 👇</blockquote><h3>Yes. Self-taught coding still works.</h3><p>If anyone tells you it doesn’t, they probably just failed at it and now run a bootcamp charging $10k to copy-paste ChatGPT responses into React components.</p><p>The truth is: companies still care more about <em>what you can build</em> than <em>where you learned</em>. A solid GitHub &gt; random diploma from “NoName Tech Institute.”</p><h3>But no, it’s not “easy now because of AI”</h3><p>Yeah yeah, you’ve seen the TikToks:<br> “Learn Python in 10 minutes!”<br> “Make $120k with just HTML and ChatGPT!”<br> Sure, and I can become a surgeon by watching Grey’s Anatomy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_u7YNAVf9A_OGkpZxdB_Tw.png" /><figcaption>Error Error Error</figcaption></figure><p>AI is a tool, not a cheat code. It <em>helps</em> you learn faster, but it won’t do the learning for you. You still need to suffer through broken layouts, error messages, and existential dread like the rest of us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MY9dIo2Lk_2Jv6XxHTnwpQ.png" /><figcaption>Just a sample ai generated image</figcaption></figure><h3>What should you actually learn?</h3><p>You don’t need a PhD in rocket science to start. Here’s a basic path:</p><ul><li><strong>HTML/CSS</strong>: Make things look not horrible.</li><li><strong>JavaScript</strong>: Make things do stuff.</li><li><strong>React or Next.js</strong>: Make things do stuff better.</li><li><strong>GitHub</strong>: So you can tell employers “Look, I actually built something.”</li><li><strong>Optional: Python + Flask/Django</strong>: If you prefer backend and chill.</li></ul><p>That’s it. Don’t get lost in “Should I learn Rust or Go or Zig or Assembly for fun?” You’re not building a compiler, you’re building your way out of retail.</p><h3>Build real things. Not to-do apps.</h3><p>Everyone makes a to-do app. Stop it. Build dumb but fun projects:</p><ul><li>“Rate My Chai” — users rank local tea stalls</li><li>“Is It A Scam?” — submit WhatsApp messages for instant sussy score</li><li>“BrokenCSS” — a portfolio of your worst designs (trust me, it’s relatable)</li></ul><p>Build stuff that <em>you</em> enjoy. Passion beats perfection.</p><h3>Will you get a job?</h3><p>Eventually, yes. But not on Day 30 of your Udemy course.</p><p>Be ready to:</p><ul><li>Apply to 100+ jobs</li><li>Hear nothing</li><li>Doubt everything</li><li>Land one job</li><li>Suddenly feel like a genius again</li></ul><p>This is normal. This is the grind. And yes, it’s still <strong>worth it</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UXKpx0RZM-nsenlQ53V61w.png" /><figcaption>just for motivation</figcaption></figure><h3>Final thoughts</h3><p>Self-taught devs built half the internet. The other half was built by unpaid interns and stackoverflow.com.</p><p>You don’t need permission to start. Just curiosity, caffeine, and stubbornness. So stop overthinking, pick a tutorial, and start building broken crap until it’s less broken.</p><p>And remember: <strong>The only thing worse than bad code is never writing any.</strong></p><p><strong>Now go. Learn. Build. Break. Repeat.</strong><br> The future still belongs to those who Google error messages best.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe937bc0d9a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I made a portfolio, Please clap ]]></title>
            <link>https://medium.com/@mdtaqui.jhar/i-made-a-portfolio-please-clap-f4b61704a14b?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4b61704a14b</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 05:26:55 GMT</pubDate>
            <atom:updated>2025-06-27T05:26:55.928Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*n6c-vYuVDg_wKfzx7GSgrg.png" /><figcaption>Thumbnail</figcaption></figure><h4>I made this. Roast me gently</h4><p>After days of battling Tailwind, fighting my inner perfectionist, and Googling “how to center a div” for the 87th time — I <strong>built my second personal portfolio</strong>.</p><p><a href="https://taqui-imam.vercel.app/"><strong>Live Here</strong></a> 👈</p><p><a href="https://github.com/taqui-786/Taqui"><strong>Souce Code </strong></a>⭐</p><h3>Why tho ??</h3><p>Honestly?</p><ul><li>I wanted to look serious online.</li><li>I was tired of my GitHub being the only “proof of existence”.</li><li>I Already have one portfolio but not to good, You can see my Old Portfolio.</li><li>And let’s be real… I just wanted something to drop in job applications that wasn’t a Notion page 😬.</li></ul><h3>What’s inside?</h3><p>This portfolio isn’t just HTML and vibes. Here’s the tech stack I used (because devs love lists):</p><h3>🧱 Frameworks &amp; Core</h3><ul><li><strong>Next.js 15</strong></li><li><strong>React 19</strong></li><li><strong>Tailwind CSS</strong> (with tailwind-merge)</li><li><strong>Framer Motion</strong> &amp; motion for smooth animation</li><li><strong>Dark mode</strong> support via next-themes</li></ul><h3>🧠 Forms &amp; Validation</h3><ul><li>react-hook-form + @hookform/resolvers</li><li>Schema validation with zod</li></ul><h3>🧩 Radix UI Components</h3><p>I may have used almost every component Radix ever made:</p><ul><li>Accordion, Dialog, DropdownMenu, Tabs, Tooltip, Checkbox, Select, Label, Avatar, Collapsible, Separator, Slot, AspectRatio</li></ul><h3>🛠️ Utils &amp; Libraries</h3><ul><li>cmdk for command menu</li><li>clsx &amp; class-variance-authority for conditional classes</li><li>lucide-react for icons</li><li>react-markdown for content rendering</li></ul><h3>✉️ Extras</h3><ul><li>nodemailer (for future email stuff)</li><li>@vercel/analytics to spy on myself</li></ul><p><a href="https://github.com/taqui-786/Taqui"><strong>Leave a Star in the Github</strong></a>⭐</p><h3>I need you (for feedback, not money… yet)</h3><p>This thing is still a baby.</p><p>So if you visit and think:</p><blockquote><em>“huh, that section is weird”</em></blockquote><blockquote><em>or</em></blockquote><blockquote><em>“why would anyone use that font?”</em></blockquote><ul><li>The design is truly inspired by <strong>Tailwindcss.com</strong> and <strong>Shadcnui</strong></li></ul><p>Please tell me. Rip it apart if needed. I want to improve it.</p><h3>Use it for your own portfolio 🔥</h3><p>It’s open source, MIT licensed. Fork it. Clone it. Remix it.</p><p>Just don’t forget to leave a star ⭐ (I need the dopamine).</p><p>Drop<a href="https://github.com/taqui-786/Taqui"><strong> a Star in the Github</strong></a>⭐</p><h3>Follow me maybe?</h3><p>If you like what I build (or just enjoy watching devs overshare online),</p><p>consider following me on GitHub!</p><p><a href="https://github.com/taqui-786">Follow me in Github</a>🙏</p><h3>That’s it</h3><p>I made a portfolio. Please clap.</p><p>And if you <em>do</em> clap, maybe leave a comment too 👇</p><p>Peace ✌️</p><p>— Taqui imam</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4b61704a14b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ JavaScript Date object is finally being replaced]]></title>
            <link>https://medium.com/@mdtaqui.jhar/javascript-date-object-is-finally-being-replaced-1452b2058b0c?source=rss-69ca1b11d7f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1452b2058b0c</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[javascript-tips]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Taqui imam]]></dc:creator>
            <pubDate>Tue, 29 Apr 2025 10:25:09 GMT</pubDate>
            <atom:updated>2025-04-29T10:25:09.787Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*wdSd4d8EFZJuDyjShIUqVQ.png" /><figcaption>Thumbnail</figcaption></figure><p>JavaScript Temporal API</p><p>The new Temporal API is coming to JavaScript and will make working with dates and times MUCH easier.</p><h4>🤔 What is Temporal Api ?</h4><p>This new JavaScript feature makes working with dates and times easier and more reliable than the old Date object. It offers various types for handling dates, times, and durations, with many options to modify them.</p><p><strong>Here’s why it’s a complete upgrade 🛠️:</strong></p><p>1️⃣ Immutable objects (no more accidental mutations!)<br>2️⃣ Built-in timezone support without external libraries<br>3️⃣ Intuitive API for date arithmetic<br>4️⃣ Clear distinction between wall-clock time and exact time<br>5️⃣ First-class duration objects for time spans</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JNXf8JVQcNDQ8fcV5Tivzw.gif" /><figcaption>Follow for more such content.</figcaption></figure><h4>📌 How to access Temporal Api ?</h4><p>Currently Temporal API can be accessed via <a href="https://www.npmjs.com/package/temporal-polyfill">Temporal API polyfill</a> its you choice of using npm or yarn packages. This makes it possible for you to use Temporal even if the native support is missing, as you will see later in this document.</p><p><strong>With NPM:</strong></p><pre> npm install @js-temporal/polyfill</pre><p><strong>With YARN:</strong></p><pre> yarn add @js-temporal/polyfill</pre><h4>Now Let’s See Some Examples 🔥</h4><p>The code example in the image shows how much cleaner date operations become with Temporal.</p><ol><li><strong>Adding Time to a Date:</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_jYsr_A7soBpGo3yRP0Xg.png" /></figure><p>This code adds 2 hours to the current date and time, then formats it as a string.</p><p>2. <strong>Comparing Dates</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xd0GJRGOWmcucYh3jVUuqg.png" /></figure><p>This code compares the current date and time with December 31, 2022, returning -1, 0, or 1 depending on whether the first date is before, equal to, or after the second date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JUpthAWau1_fT3K_XYm8xQ.gif" /><figcaption>At least leave +1 clap.</figcaption></figure><p>3. <strong>Creating a Date from a String</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Stm_Dhovx5HVqjsFvnNGWg.png" /></figure><p>This code creates a date object from an ISO date string and formats it as a string.</p><p>4. <strong>Subtracting Time from a Date</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J_jEm0qh5pQODqiJnhb_xQ.png" /></figure><p>This code subtracts 3 months from the current date and time, then formats it as a string.</p><p>5. <strong>Calculating the Duration Between Two Dates</strong>:</p><p>Works out how long the period between two dates is. You might use this when signing a JWT to work out how many seconds from now your expiry date is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASg9zXGP_PbkC_h_rZaX5g.png" /></figure><p>This code calculates the number of seconds between the current date and time and December 25, 2025</p><p><strong>For more examples and code reference checkout 👉</strong><a href="https://temporal-api-cheatsheet.rodneylab.com/"><strong>Temporal API Cheatsheet: Quick Guide to new JS API</strong></a></p><p>Who else 😅 is excited to never write “new Date()” again?</p><p>okay, see you in my next blog, till then</p><p>Happy coding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JNXf8JVQcNDQ8fcV5Tivzw.gif" /><figcaption>Don’t forget to follow me.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1452b2058b0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>