<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python on Gaurav.dev</title><link>/tags/python/</link><description>Recent content in Python on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Choose a Modern Web Stack Without Regretting It</title><link>/posts/choosing-modern-web-stack/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate><guid>/posts/choosing-modern-web-stack/</guid><description>&lt;p&gt;The best technology stack is rarely the one with the longest feature list. It is the one your team can operate confidently while the product changes around it.&lt;/p&gt;&#10;&lt;h2 id="start-with-constraints"&gt;Start with constraints&lt;/h2&gt;&#10;&lt;p&gt;Before comparing frameworks, write down the facts: expected traffic, search requirements, real-time behaviour, integrations, compliance, team experience, delivery date, and operating budget. These constraints eliminate more options than a benchmark ever will.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Next.js&lt;/strong&gt; is a strong default for content-rich products that also need application behaviour. It offers flexible rendering, a broad React ecosystem, and a straightforward path to full-stack TypeScript. Its flexibility also means the team must be disciplined about caching and server/client boundaries.&lt;/p&gt;</description></item><item><title>Django or FastAPI? Choosing the Right Python API Foundation</title><link>/posts/python-api-django-fastapi/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>/posts/python-api-django-fastapi/</guid><description>&lt;p&gt;Django and FastAPI can both power serious APIs. The more useful question is not which framework is faster; it is which one removes the most risk from your particular product.&lt;/p&gt;&#10;&lt;h2 id="choose-django-for-an-integrated-product-platform"&gt;Choose Django for an integrated product platform&lt;/h2&gt;&#10;&lt;p&gt;Django brings an ORM, migrations, authentication, administration, security defaults, and a mature ecosystem. It shines when the API sits inside a business application with users, permissions, editorial workflows, relational data, and operational staff.&lt;/p&gt;</description></item><item><title>Flask, FastAPI, or Bottle: Choosing a Python Microframework</title><link>/posts/flask-fastapi-bottle-python-api/</link><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><guid>/posts/flask-fastapi-bottle-python-api/</guid><description>&lt;p&gt;Python gives API teams an unusual amount of choice. Flask, FastAPI, and Bottle can all expose an HTTP endpoint in a few lines, but they optimise for different kinds of simplicity. Choosing well means looking beyond the first route and asking how the service will be validated, tested, deployed, and changed.&lt;/p&gt;&#10;&lt;h2 id="flask-flexible-and-proven"&gt;Flask: flexible and proven&lt;/h2&gt;&#10;&lt;p&gt;Flask is the dependable general-purpose option. Its request model is easy to understand, its extension ecosystem is mature, and experienced Python developers can recognise a Flask application quickly. It works especially well for internal tools, integration services, conventional REST APIs, and products that need freedom without inventing the entire HTTP layer.&lt;/p&gt;</description></item><item><title>Building a Python Full Stack for Generative AI Products</title><link>/posts/python-full-stack-generative-ai/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>/posts/python-full-stack-generative-ai/</guid><description>&lt;p&gt;An AI product is still a product. It needs authentication, permissions, billing, data ownership, reliable jobs, observable failures, and an interface that helps users judge uncertain results. A practical Python full stack handles those concerns without forcing model code into every layer.&lt;/p&gt;&#10;&lt;h2 id="choose-the-application-centre"&gt;Choose the application centre&lt;/h2&gt;&#10;&lt;p&gt;Use Django when the product needs an integrated business platform: relational workflows, administration, users, permissions, and substantial back-office operations. Django’s conventions reduce the number of infrastructure decisions and give operations teams useful interfaces early.&lt;/p&gt;</description></item></channel></rss>