<?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 Srikanth Velpuri on Medium]]></title>
        <description><![CDATA[Stories by Srikanth Velpuri on Medium]]></description>
        <link>https://medium.com/@srikanthvelpuri?source=rss-872bb9e0f5a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wE9UBAQxe2zL-5w0.</url>
            <title>Stories by Srikanth Velpuri on Medium</title>
            <link>https://medium.com/@srikanthvelpuri?source=rss-872bb9e0f5a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:53:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srikanthvelpuri/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[How AI Is Changing the World, One Ordinary Day at a Time]]></title>
            <link>https://medium.com/@srikanthvelpuri/how-ai-is-changing-the-world-one-ordinary-day-at-a-time-95162cab461b?source=rss-872bb9e0f5a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/95162cab461b</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Srikanth Velpuri]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 19:11:08 GMT</pubDate>
            <atom:updated>2026-10-30T19:11:08.379Z</atom:updated>
            <content:encoded><![CDATA[<p>As a software developer, a daily learner, and a tech enthusiast, I am watching AI change what I believe I can achieve. I used to imagine advances like this as something far in the future. Now I can work with them every day, and the experience is beyond what I once thought possible.</p><p>The change feels personal. With AI, I feel capable of delivering architecture work at a level I once associated with the best software architects in the world. Work that would have felt impossible for me to tackle independently in the past now feels within reach. That shift in confidence and capability is how I see AI changing the world, one ordinary day at a time.</p><h3>Thinking beyond the code</h3><p>The most exciting part for me is the chance to think more deeply about the whole system. Writing code is one part of development. Architecture asks how the pieces fit together, which trade-offs are acceptable, and whether the design will still serve its purpose as requirements change.</p><p>AI gives me a way to explore those questions. I can bring it a requirement, compare possible designs, and ask it to challenge the assumptions behind an approach. Questions about data flow, service boundaries, security, reliability, and cost become easier to investigate together.</p><p>For me, this feels like access to a depth of technical discussion that would once have been difficult to find on demand. I can move from an idea toward a design, examine alternatives, and work toward an implementation with much more support than I had before.</p><p>When I say this brings world-class architecture work within reach, I am describing how much my own sense of possibility has expanded. The quality still has to be demonstrated: the design must fit the requirements, the code must be reviewed and tested, and the system must hold up in practice. I remain responsible for what I deliver.</p><h3>From a blank page to a starting point</h3><p>One of the clearest examples is writing. A blank page can hold up an idea before it has a chance to develop. AI offers a way to begin: a rough outline, a different opening, or a question that helps clarify what we actually mean.</p><p>This blog itself is part of that change. Asking AI to help express a thought shows how the distance between having an idea and putting it into words is shrinking. But the words still need a person behind them. I want the finished piece to reflect something I believe, rather than simply sound polished.</p><p>That distinction matters to me. Producing more text is easy. Saying something worth reading still takes attention, honesty, and a point of view.</p><h3>A different relationship with learning</h3><p>As a daily learner, I find this just as exciting as the development work itself. I can take an unfamiliar technical concept and keep asking questions: Why would this design work? Where could it fail? What would change at a larger scale? I can ask for a simpler explanation, then go deeper into the details.</p><p>That makes learning feel connected to building. An unfamiliar idea can become a small experiment, and the experiment can reveal the next question. I want to use that cycle to strengthen my own understanding, so that each project leaves me more capable than the one before it.</p><p>At the same time, an answer that sounds clear can still be wrong. For me, learning with AI should include checking sources, testing an explanation, and knowing when to ask someone with relevant expertise. Understanding requires more than accepting a confident response.</p><h3>What happens when starting gets easier?</h3><p>When I consider the tools that can help draft, summarize, translate, or explore an idea, I see a broader possibility: more people may be able to attempt work they once found intimidating. Someone with an idea can get a little further before getting stuck.</p><p>That possibility is exciting. It also raises a question I keep returning to: what will we do with the time and effort these tools save? We could fill our days with more output. Or we could spend more time deciding what deserves to be made, improving the result, and paying attention to other people.</p><p>I hope we choose thoughtfully. Speed is useful, but it is not the only measure of progress.</p><h3>When ambitious ideas become real experiments</h3><p>Two developments this October capture the sense of possibility I feel. After launching its Project Suncatcher prototype on October 1, <a href="https://blog.google/innovation-and-ai/models-and-research/google-research/project-suncatcher-satellite-response/">Google announced on October 30, 2026, that it had received an AI response generated by a data-center-class TPU in orbit</a>. Its onboard Gemma 4 model answered a prompt asking for a haiku about being in space. As a developer, I find that extraordinary: this is AI hardware executing a real workload beyond Earth. Google says further tests will examine thermal stress and radiation exposure, with two interconnected satellites planned for 2027. It is a meaningful experimental milestone, while large-scale commercial AI infrastructure in orbit remains a longer-term goal.</p><p>Meanwhile, <a href="https://www.foxbusiness.com/technology/teslas-new-roadster-makes-flying-debut-hitting-60-mph-under-second">reporting on Tesla’s October 15 Roadster demonstration</a> described a prototype performing airborne stunts with compressed-gas thrusters. The distinction matters: a controlled demonstration does not establish a practical flying car for everyday use. <a href="https://www.motor1.com/news/812195/tesla-roadster-stunt-2028-production/">Production was targeted for 2028</a>, and the eventual capabilities and availability still need to be demonstrated.</p><p>The Google project directly concerns AI computing; the Roadster demonstration is a separate example of ambitious engineering. I do not take the car stunt as proof that AI made it possible. Together, these stories remind me why I love technology: ideas that once sounded remote can become experiments we can examine, question, and learn from.</p><h3>Excited about the technology, worried about the people</h3><p>Alongside my excitement, I worry about job security at Microsoft and other major technology companies. The prospect of voluntary buyouts and layoffs makes the future feel less certain, even as the tools themselves become more powerful. Behind every role is a person with responsibilities, plans, and years spent building a career.</p><p>As a developer, I feel the tension personally. I am amazed by how much more I can accomplish with AI. But that same experience makes me ask a difficult question: if one person can do more, will companies use that capacity to build more ambitious products, or decide they need fewer people? I do not know how that choice will play out across the industry.</p><p>I also cannot assume AI explains every buyout or layoff. Understanding any particular decision requires evidence about the company and its circumstances. My concern is about the direction we choose as this technology develops, and whether employees will share in the benefits of the productivity they help create.</p><p>Continuous learning feels more important to me in this environment, but individuals cannot carry the whole responsibility for the transition. I want to see companies invest in helping people adapt, create paths into new roles, and treat those affected by workforce changes with transparency and respect. My hope is that the progress I experience as a builder also becomes progress for the people building alongside me.</p><h3>The concerns belong in the conversation</h3><p>I cannot think about AI only in terms of convenience. Questions about jobs, privacy, ownership, and trust belong alongside the enthusiasm. A tool that helps one person may create uncertainty for another. An image or message that looks convincing may deserve a closer look.</p><p>I do not have a neat answer to every concern. My own standard is to stay curious without giving up judgment: be careful about what I share, verify things that matter, and be honest about where AI has helped.</p><h3>The world I see taking shape</h3><p>The biggest change, to me, is the growing expectation that we can ask a machine for help with an unfinished thought. That changes how we begin tasks and what we imagine we might be able to do.</p><p>As a tech enthusiast, I find that possibility extraordinary. As a developer, I want to turn it into useful, reliable systems. As a daily learner, I want to keep understanding more of what I build. Those three perspectives make this moment feel bigger than a new set of tools: it is a change in the scale of what I can imagine attempting.</p><p>For me, that is where the story of AI becomes personal. The world changes through the habits we build each day: what we ask, what we question, what we create, and what we decide to take responsibility for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95162cab461b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>