<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Poonam Biradar</title>
    <description>The latest articles on DEV Community by Poonam Biradar (@poonambuilds).</description>
    <link>https://dev.to/poonambuilds</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4200078%2F725b51a9-2280-456f-8bba-04530d90ad66.jpg</url>
      <title>DEV Community: Poonam Biradar</title>
      <link>https://dev.to/poonambuilds</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/poonambuilds"/>
    <language>en</language>
    <item>
      <title>AI Helps Us Build Faster. Are We Learning Enough?</title>
      <dc:creator>Poonam Biradar</dc:creator>
      <pubDate>Sat, 24 Oct 2026 07:32:06 +0000</pubDate>
      <link>https://dev.to/poonambuilds/ai-helps-us-build-faster-are-we-learning-enough-53dh</link>
      <guid>https://dev.to/poonambuilds/ai-helps-us-build-faster-are-we-learning-enough-53dh</guid>
      <description>&lt;p&gt;You finish a feature with AI.&lt;/p&gt;

&lt;p&gt;The page loads. The API responds. The error is gone.&lt;/p&gt;

&lt;p&gt;Then a requirement changes, and you’re unsure which part of the code to touch.&lt;/p&gt;

&lt;p&gt;Does that mean using AI was a mistake? Not necessarily. But it raises a question worth asking:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Did the task leave you with a working feature, a better understanding—or both?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As developers, we need to deliver work. We also need to develop the judgment to maintain it. Those goals can support each other, but they don’t automatically move at the same speed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Faster at the task isn’t the same as better at the skill
&lt;/h2&gt;

&lt;p&gt;Imagine asking AI to build a product filter.&lt;/p&gt;

&lt;p&gt;It adds a dropdown, stores the selected category, and filters the list. You try a few categories. Everything works.&lt;/p&gt;

&lt;p&gt;Now the requirement changes:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Keep the filter selected after a refresh, and let users share the filtered page.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Can you explain where the current selection lives? Can you decide whether it belongs in the URL, browser storage, or somewhere else?&lt;/p&gt;

&lt;p&gt;You can still consult documentation or ask for help. The useful question is whether you can reason about the change before requesting another implementation.&lt;/p&gt;

&lt;p&gt;A completed feature shows that a solution exists. Adapting it gives you more evidence of what you understand.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the research actually says
&lt;/h2&gt;

&lt;p&gt;A January 2026 study by Anthropic researchers examined developers learning Trio, an unfamiliar Python library.&lt;/p&gt;

&lt;p&gt;The researchers recruited 52 mostly junior engineers. Participants completed coding tasks with or without AI assistance, then took an assessment. Average scores were &lt;strong&gt;50% in the AI-assisted group and 67% in the group without AI assistance&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The difference in completion time was not statistically significant.&lt;/p&gt;

&lt;p&gt;That deserves attention, but it needs context: this was a short experiment involving one unfamiliar library and an immediate assessment. It doesn’t establish that every use of AI weakens learning, or tell us what happens across years of professional work.&lt;/p&gt;

&lt;p&gt;The researchers also observed different interaction patterns. Participants who asked conceptual questions or worked through explanations tended to show stronger understanding than those who heavily delegated the work.&lt;/p&gt;

&lt;p&gt;Those patterns were observational, not separately randomized. They suggest useful questions about our habits; they don’t prove that a particular prompting technique guarantees learning.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.anthropic.com/research/AI-assistance-coding-skills" rel="noopener noreferrer"&gt;Read the study summary and its limitations.&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The gap can hide inside a convincing explanation
&lt;/h2&gt;

&lt;p&gt;AI can explain code clearly. That’s helpful.&lt;/p&gt;

&lt;p&gt;But an explanation making sense while you read it isn’t the same as being able to apply the idea later.&lt;/p&gt;

&lt;p&gt;Consider authentication. You read an explanation of access tokens and think you understand the flow.&lt;/p&gt;

&lt;p&gt;Then a token expires halfway through a session.&lt;/p&gt;

&lt;p&gt;Where does the failure appear? What should the frontend do? Which part belongs on the server? Could a retry repeat an operation?&lt;/p&gt;

&lt;p&gt;You don’t need every answer immediately. Being able to identify what you need to investigate is already valuable.&lt;/p&gt;

&lt;p&gt;One way to check your understanding is to make a prediction before running the code:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“If the API returns an empty array, this component should show the empty state.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then test it.&lt;/p&gt;

&lt;p&gt;When the result differs from your prediction, you’ve found something specific to learn.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical habit: explain, change, investigate
&lt;/h2&gt;

&lt;p&gt;You don’t need to stop using AI or rebuild every feature from memory. Try this with one unfamiliar part of your next task.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Explain the flow without reopening the chat
&lt;/h3&gt;

&lt;p&gt;Write a short explanation in your own words.&lt;/p&gt;

&lt;p&gt;For a form, describe:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where the input is stored&lt;/li&gt;
&lt;li&gt;Where validation happens&lt;/li&gt;
&lt;li&gt;What the request sends&lt;/li&gt;
&lt;li&gt;What changes on the backend&lt;/li&gt;
&lt;li&gt;How success and failure reach the user&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;“I’m not sure what happens here” is a useful finding. It’s more actionable than “I need to get better at backend development.”&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Make one small change
&lt;/h3&gt;

&lt;p&gt;Change a requirement in a development branch.&lt;/p&gt;

&lt;p&gt;For the product filter, make the selected category appear in the URL. Before implementing it, decide what should happen when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Someone opens a shared link&lt;/li&gt;
&lt;li&gt;The category doesn’t exist&lt;/li&gt;
&lt;li&gt;The user clears the filter&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use documentation. Ask questions. But form an initial approach before accepting a generated one.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Investigate one failure
&lt;/h3&gt;

&lt;p&gt;Use a disposable example or development environment.&lt;/p&gt;

&lt;p&gt;Send invalid input, return an empty result, or simulate a failed request. Before asking AI to fix it, record:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What you expected&lt;/li&gt;
&lt;li&gt;What actually happened&lt;/li&gt;
&lt;li&gt;One possible cause&lt;/li&gt;
&lt;li&gt;How you could check that cause&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This isn’t an exam. It’s a way to discover whether the implementation matches your mental model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask AI to support the investigation
&lt;/h2&gt;

&lt;p&gt;“Fix this” is sometimes an appropriate request. It just shouldn’t be the only interaction available to you.&lt;/p&gt;

&lt;p&gt;Try:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Don’t edit the code yet. Identify two plausible causes and suggest how I can distinguish between them.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Or:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Here is my explanation of this function. Which parts are inaccurate or missing?”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;For a new concept:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Give me a small exercise using this idea. Let me attempt it before showing a solution.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Check the answers against documentation and observed behaviour. An explanation can be wrong even when it sounds coherent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Not every task needs to become a lesson
&lt;/h2&gt;

&lt;p&gt;There’s a reasonable counterargument: work has deadlines. Spending an hour studying familiar boilerplate may add little value.&lt;/p&gt;

&lt;p&gt;That’s fair.&lt;/p&gt;

&lt;p&gt;The point isn’t to maximize manual effort. It’s to be deliberate about where understanding matters.&lt;/p&gt;

&lt;p&gt;If you already understand the pattern, delegating repetitive implementation can be sensible. If the feature introduces unfamiliar permissions, payment behaviour, database updates, or failure handling, reserve time to review and test those decisions.&lt;/p&gt;

&lt;p&gt;Teams have a role here too. Expecting juniors to deliver faster while removing time for questions, review, and practice creates a difficult learning environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure what stays with you
&lt;/h2&gt;

&lt;p&gt;Counting completed tasks won’t tell you everything about your development.&lt;/p&gt;

&lt;p&gt;Occasionally ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Can I explain a decision I previously couldn’t?&lt;/li&gt;
&lt;li&gt;Can I modify the feature without replacing the entire implementation?&lt;/li&gt;
&lt;li&gt;Can I narrow down a bug before requesting a fix?&lt;/li&gt;
&lt;li&gt;Can I recognize when a suggested solution doesn’t fit the requirement?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can use AI and still make progress on all four.&lt;/p&gt;

&lt;p&gt;The goal is to finish work while retaining enough understanding to take responsibility for it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Think of one feature you recently built with AI: what could you now explain or change that you couldn’t before? What part still feels unclear?&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Reference
&lt;/h2&gt;

&lt;p&gt;Shen, J. H., and Tamkin, A. &lt;em&gt;How AI Impacts Skill Formation&lt;/em&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.anthropic.com/research/AI-assistance-coding-skills" rel="noopener noreferrer"&gt;Research summary&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://arxiv.org/abs/2601.20245" rel="noopener noreferrer"&gt;Full paper&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;The workflow suggested in this article is a practical recommendation, not a validated learning intervention.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>discuss</category>
      <category>learning</category>
    </item>
    <item>
      <title>Works in Postman, Fails in the Browser: Where to Start Debugging</title>
      <dc:creator>Poonam Biradar</dc:creator>
      <pubDate>Thu, 22 Oct 2026 09:36:41 +0000</pubDate>
      <link>https://dev.to/poonambuilds/works-in-postman-fails-in-the-browser-where-to-start-debugging-24cf</link>
      <guid>https://dev.to/poonambuilds/works-in-postman-fails-in-the-browser-where-to-start-debugging-24cf</guid>
      <description>&lt;p&gt;An API returns &lt;code&gt;200 OK&lt;/code&gt; in Postman, but the frontend can’t load the data.&lt;/p&gt;

&lt;p&gt;Where do you start?&lt;/p&gt;

&lt;p&gt;CORS is one possibility. But before changing server settings, check whether your frontend is sending the same request you tested in Postman.&lt;/p&gt;

&lt;p&gt;Here are three checks that help narrow it down.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Compare what you actually sent
&lt;/h2&gt;

&lt;p&gt;Consider this example.&lt;/p&gt;

&lt;p&gt;In Postman, you configure bearer authentication and successfully request a list of orders:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;GET https://api.example.com/api/orders
Authorization: Bearer YOUR_ACCESS_TOKEN
Accept: application/json
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then you write this in your frontend:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;https://api.example.com/api/orders&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Same endpoint. Different request.&lt;/p&gt;

&lt;p&gt;The frontend isn’t sending the authorization header. Postman’s saved token doesn’t carry over to your application.&lt;/p&gt;

&lt;p&gt;For an API that requires bearer authentication, the request could look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;getOrders&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;accessToken&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;https://api.example.com/api/orders&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="na"&gt;Accept&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;Authorization&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`Bearer &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;accessToken&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;

  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;ok&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;throw&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Error&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;`Request failed: &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;status&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The URL above is a placeholder. Use your endpoint and a valid user access token from your authentication flow.&lt;/p&gt;

&lt;p&gt;Also compare the method, query parameters, and request body. If the token is present, check whether it has expired.&lt;/p&gt;

&lt;p&gt;Notice the &lt;code&gt;response.ok&lt;/code&gt; check: &lt;code&gt;fetch()&lt;/code&gt; doesn’t automatically throw when the server returns an HTTP error such as &lt;code&gt;401&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Read the browser’s request
&lt;/h2&gt;

&lt;p&gt;Instead of relying only on an error message in the UI, open:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Developer Tools → Network&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Trigger the request again and select it.&lt;/p&gt;

&lt;p&gt;Start with four questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is this the URL I expected?&lt;/li&gt;
&lt;li&gt;Did the authorization header get sent?&lt;/li&gt;
&lt;li&gt;What status came back?&lt;/li&gt;
&lt;li&gt;What does the response body say?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, a readable &lt;code&gt;401&lt;/code&gt; response gives you a reason to investigate authentication. An HTML response where you expected JSON might be a login page or an error page.&lt;/p&gt;

&lt;p&gt;Check the Console too. If it reports a CORS error, move to the next check.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Check whether the browser can read the response
&lt;/h2&gt;

&lt;p&gt;Suppose your application uses these addresses:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Frontend: http://localhost:3000
API:      http://localhost:8000
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;They have different ports, so they are different origins.&lt;/p&gt;

&lt;p&gt;For browser-side JavaScript to read that API response, the server needs to allow the frontend’s origin through CORS.&lt;/p&gt;

&lt;p&gt;Postman’s desktop client doesn’t enforce the browser’s same-origin restrictions. A successful request there doesn’t confirm that browser access is configured.&lt;/p&gt;

&lt;p&gt;For this local setup, the server might return:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;Access-Control-Allow-Origin: http://localhost:3000
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is a &lt;strong&gt;response header set by the server&lt;/strong&gt;. Adding it to your frontend request won’t grant permission.&lt;/p&gt;

&lt;p&gt;And a CORS error doesn’t always mean the API received nothing. The server may have responded while the browser prevented your JavaScript from reading the response.&lt;/p&gt;

&lt;h3&gt;
  
  
  What about the OPTIONS request?
&lt;/h3&gt;

&lt;p&gt;A cross-origin request containing an &lt;code&gt;Authorization&lt;/code&gt; header generally triggers a preflight.&lt;/p&gt;

&lt;p&gt;You’ll see an &lt;code&gt;OPTIONS&lt;/code&gt; request in the Network tab before the intended request. The browser uses it to check whether the method and headers are allowed.&lt;/p&gt;

&lt;p&gt;If that check fails, the intended request won’t be sent.&lt;/p&gt;

&lt;p&gt;Check your server’s CORS settings and whether middleware or a proxy is rejecting &lt;code&gt;OPTIONS&lt;/code&gt;. The actual response needs the appropriate CORS headers too.&lt;/p&gt;

&lt;p&gt;Avoid treating this as a fix:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;mode&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;no-cors&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For a normal JSON API integration, it leaves you with a response your JavaScript cannot read normally.&lt;/p&gt;

&lt;h2&gt;
  
  
  One distinction if you use Next.js
&lt;/h2&gt;

&lt;p&gt;These browser restrictions apply when the request runs in the browser.&lt;/p&gt;

&lt;p&gt;A request from a Next.js server route runs on the server, where browser CORS enforcement doesn’t apply. Authentication, network access, and the API’s own restrictions still matter.&lt;/p&gt;

&lt;p&gt;So check &lt;strong&gt;where the request executes&lt;/strong&gt;, not just which framework you’re using.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where I’d start
&lt;/h2&gt;

&lt;p&gt;Before changing the backend, compare the working Postman request with the request shown in the browser’s Network tab.&lt;/p&gt;

&lt;p&gt;That comparison helps separate three different problems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The frontend sent something different.&lt;/li&gt;
&lt;li&gt;The API rejected the request.&lt;/li&gt;
&lt;li&gt;The browser wouldn’t let JavaScript read the response.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each needs a different fix.&lt;/p&gt;

&lt;p&gt;If you’ve run into this mismatch, what turned out to be different?&lt;/p&gt;




&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS" rel="noopener noreferrer"&gt;MDN: Cross-Origin Resource Sharing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch" rel="noopener noreferrer"&gt;MDN: Using the Fetch API&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>api</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
