<?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: Ipshita Bhardwaj</title>
    <description>The latest articles on DEV Community by Ipshita Bhardwaj (@ipshita_bhardwaj).</description>
    <link>https://dev.to/ipshita_bhardwaj</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%2F2527862%2Fd83153c2-89b7-4a4b-97cc-bc5cd434b600.png</url>
      <title>DEV Community: Ipshita Bhardwaj</title>
      <link>https://dev.to/ipshita_bhardwaj</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ipshita_bhardwaj"/>
    <language>en</language>
    <item>
      <title>I Wish I Could See Your ChatGPT History.</title>
      <dc:creator>Ipshita Bhardwaj</dc:creator>
      <pubDate>Wed, 18 Nov 2026 19:28:07 +0000</pubDate>
      <link>https://dev.to/ipshita_bhardwaj/i-wish-i-could-see-your-chatgpt-history-22f5</link>
      <guid>https://dev.to/ipshita_bhardwaj/i-wish-i-could-see-your-chatgpt-history-22f5</guid>
      <description>&lt;p&gt;If you really wanted to understand how someone thinks, would you rather read a hundred of their answers or a hundred of their questions?&lt;/p&gt;

&lt;p&gt;I think I'd choose the questions.&lt;/p&gt;

&lt;p&gt;Sometimes, when I come across a particularly impressive developer on GitHub, I find myself wondering what their ChatGPT history looks like. Not because I'm interested in how much of their code was written by AI, but because I'm curious about the things they don't understand.&lt;/p&gt;

&lt;p&gt;There's something rather comforting about the possibility that someone whose work I find incredibly sophisticated might have spent an entire afternoon struggling with something I happen to find simple.&lt;/p&gt;

&lt;p&gt;Of course, if someone were to direct that same curiosity towards my conversation history, they would probably find some very entertaining things.&lt;/p&gt;

&lt;p&gt;But it has made me think about how little we actually know about the way other people learn, particularly now that so much of our learning happens in conversations nobody else gets to see.&lt;/p&gt;

&lt;h2&gt;
  
  
  Learning to code in the age of AI
&lt;/h2&gt;

&lt;p&gt;I'm currently in my third year of engineering, which puts me in a rather interesting generation of developers. By the time I seriously entered software development, generative AI was already available. I never really had to rely on Stack Overflow in the way that many experienced developers describe having done.&lt;/p&gt;

&lt;p&gt;For me, AI wasn't a disruption to an established way of learning. It was part of how I learned in the first place.&lt;/p&gt;

&lt;p&gt;I can ask a question without necessarily knowing how to articulate it. I can interrupt an explanation because something halfway through doesn't make sense. I can ask the same question three different ways and, occasionally, discover that what I thought I was confused about wasn't actually the source of my confusion.&lt;/p&gt;

&lt;p&gt;I sometimes wonder what those experiences would have looked like had I started programming ten years earlier.&lt;/p&gt;

&lt;p&gt;Perhaps some of my questions would have ended up on a public forum. Someone might have responded, someone else might have disagreed, and years later, another student struggling with the same thing might have stumbled across that conversation.&lt;/p&gt;

&lt;p&gt;Instead, most of my questions have served exactly one person: me.&lt;/p&gt;

&lt;p&gt;There's every possibility that someone somewhere has spent an evening trying to understand the exact same thing I have, made the same incorrect assumptions, and eventually arrived at the same understanding through a remarkably similar conversation with AI.&lt;/p&gt;

&lt;p&gt;We could have had quite an interesting conversation with each other.&lt;/p&gt;

&lt;p&gt;Instead, we both closed our respective chat windows and moved on.&lt;/p&gt;

&lt;p&gt;I wouldn't necessarily call that a bad thing. The accessibility of personalised technical help is something I wouldn't willingly give up. But I do find it fascinating that two people can share an almost identical learning experience without ever knowing the other exists.&lt;/p&gt;

&lt;h2&gt;
  
  
  How strange it is to look at someone else's GitHub
&lt;/h2&gt;

&lt;p&gt;One of my favourite ways of discovering new technologies is looking through other people's projects. Unfortunately, it's also a remarkably efficient way of discovering several new reasons to feel behind.&lt;/p&gt;

&lt;p&gt;I'll come across someone my age working with a technology I've barely heard of, follow a few links, and somehow end up with another five things on my already unreasonable list of things to learn.&lt;/p&gt;

&lt;p&gt;What I rarely consider in those moments is that somebody looking through my work might be doing exactly the same thing.&lt;/p&gt;

&lt;p&gt;They might see a machine learning project I've built and assume that I'm comfortable with everything that went into it. They wouldn't know which concepts took me several attempts to understand, which decisions I reconsidered, or which seemingly straightforward parts turned out to be unexpectedly difficult.&lt;/p&gt;

&lt;p&gt;And, naturally, I don't know any of that about them either.&lt;/p&gt;

&lt;p&gt;I think there's an interesting imbalance in how we experience our own competence compared to everyone else's. We have access to every moment of our own confusion, but relatively few moments of anybody else's.&lt;/p&gt;

&lt;p&gt;AI conversations have made that imbalance even more pronounced. Much of the questioning, experimenting and misunderstanding that goes into learning something can now happen entirely in private.&lt;/p&gt;

&lt;p&gt;The resulting project, however, is still public.&lt;/p&gt;

&lt;p&gt;It would be interesting to know how differently we might perceive each other if we could see even a small fraction of what happened before that project appeared on GitHub.&lt;/p&gt;

&lt;h2&gt;
  
  
  The questions that never make it into a commit
&lt;/h2&gt;

&lt;p&gt;One thing I've found particularly amusing about learning software development is how inconsistently knowledge seems to accumulate.&lt;/p&gt;

&lt;p&gt;You can understand something relatively sophisticated and remain completely unfamiliar with something supposedly fundamental. You can spend weeks working with a technology and still discover something about it that makes you wonder how you managed to use it for those weeks.&lt;/p&gt;

&lt;p&gt;Just recently, somewhere among my conversations about software development and machine learning, I asked ChatGPT what Registry Editor in Windows was.&lt;/p&gt;

&lt;p&gt;I rather enjoy the fact that these questions coexist.&lt;/p&gt;

&lt;p&gt;Technical knowledge doesn't seem to organise itself according to the difficulty levels of a programming course. We encounter things as they become relevant to us, develop oddly specific areas of expertise, and sometimes discover fairly elementary gaps much later than we might have expected.&lt;/p&gt;

&lt;p&gt;A résumé has very little room for that nuance. Neither does a GitHub profile.&lt;/p&gt;

&lt;p&gt;But I've also noticed that some of the most valuable time I spend learning doesn't necessarily result in anything I can put on either of them.&lt;/p&gt;

&lt;p&gt;Sometimes, something is already working, and I simply want to understand why. I might spend another hour reading about it, questioning an implementation or following a line of curiosity that has little practical relevance to the project anymore.&lt;/p&gt;

&lt;p&gt;At the end of that hour, there might be no new code to commit. The application works exactly as it did before.&lt;/p&gt;

&lt;p&gt;The only thing that has changed is my understanding of it.&lt;/p&gt;

&lt;p&gt;I find it interesting that, in a profession where we have so many ways of making our progress visible, this particular kind of progress is almost impossible to see from the outside.&lt;/p&gt;

&lt;p&gt;It probably exists somewhere in a conversation titled something extraordinarily unhelpful, like "Explain this."&lt;/p&gt;

&lt;h2&gt;
  
  
  Perhaps the questions are worth sharing, too
&lt;/h2&gt;

&lt;p&gt;I've been thinking about starting a technical blog for a while, and I kept returning to the question of what I knew enough about to write.&lt;/p&gt;

&lt;p&gt;I could explain an algorithm, write about a framework, or put together a tutorial. But whenever I considered doing that, I found myself wondering what would make someone want to read my explanation when they could already get a perfectly reasonable one from an AI.&lt;/p&gt;

&lt;p&gt;The things I find most interesting about other developers are often considerably more personal than their explanations of technology. I'm curious about why they chose to build something, what surprised them along the way, which assumptions they had to reconsider, and what they ended up being curious about afterwards.&lt;/p&gt;

&lt;p&gt;I would particularly love to know what they found difficult. Not because it diminishes anything they've accomplished, but because it gives me a much richer understanding of the person behind the accomplishment.&lt;/p&gt;

&lt;p&gt;Perhaps that's something we could afford to share a little more often.&lt;/p&gt;

&lt;p&gt;And perhaps, rather than waiting until I've understood something well enough to write about it, I could occasionally write about the experience of trying to understand it.&lt;/p&gt;

&lt;p&gt;I'm twenty, and I imagine my thoughts about software engineering will change considerably over the next few years. I'll probably revisit some of what I write here and wonder how I ever arrived at those conclusions.&lt;/p&gt;

&lt;p&gt;I'm rather looking forward to that.&lt;/p&gt;

&lt;p&gt;It would be nice to have somewhere on the internet where I could return, years from now, and recognise the person I was while learning all of this.&lt;/p&gt;

&lt;p&gt;Somewhere other than my ChatGPT history.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>ai</category>
      <category>programming</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
