<?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: SAVITA WADJE</title>
    <description>The latest articles on DEV Community by SAVITA WADJE (@savitawadje).</description>
    <link>https://dev.to/savitawadje</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%2F4086885%2F29c3732d-7dfc-4297-932e-3ca520588b2a.jpg</url>
      <title>DEV Community: SAVITA WADJE</title>
      <link>https://dev.to/savitawadje</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/savitawadje"/>
    <language>en</language>
    <item>
      <title>Why I Left a Good Job in India to Study in Germany at 5+ Years Into My Career</title>
      <dc:creator>SAVITA WADJE</dc:creator>
      <pubDate>Fri, 21 Aug 2026 11:48:37 +0000</pubDate>
      <link>https://dev.to/savitawadje/why-i-left-a-good-job-in-india-to-study-in-germany-at-5-years-into-my-career-5g7n</link>
      <guid>https://dev.to/savitawadje/why-i-left-a-good-job-in-india-to-study-in-germany-at-5-years-into-my-career-5g7n</guid>
      <description>&lt;p&gt;This one is not a coding post. It is a story I have wanted to write for a while.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Everything was going well, but something was missing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I had almost 5 years of experience working in India, and honestly, my job was going well. Good team, good work, nothing to complain about. But somewhere inside, I was not fully satisfied.&lt;/p&gt;

&lt;p&gt;I always had this small dream of doing my Masters. It stayed in the back of my mind for years, quietly. Slowly, that dream started fading, the way dreams do when life gets busy and comfortable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The conversation that changed things&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One day I was talking to a close friend, just casually, and it hit me that it might be too late to chase that dream now. But then I thought, it is not impossible. It is just late. And honestly, it is better to be late than to spend years regretting that I never tried.&lt;/p&gt;

&lt;p&gt;So I took the risk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why Germany specifically&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I started applying, and the question everyone asked me was, why Germany? For me it came down to job security. The job market here felt more stable, and wherever I was going to move, I wanted to land somewhere that gave me a real chance to build a life, not just a degree on paper.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It was more spontaneous than planned&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Because I was still working full time at my last organization, I genuinely did not have the time to apply to multiple universities the way most people do. I applied to just one. And I got lucky, I got the admit.&lt;/p&gt;

&lt;p&gt;Looking back, it feels like such a spontaneous decision for something this big. But sometimes that is just how life works out.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Life here, and what it taught me&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now I am studying alongside a lot of Gen Z students, and I learn so much just being around them, not just academically but life skills too, survival skills you only pick up when you are figuring things out on your own in a new country.&lt;/p&gt;

&lt;p&gt;I live alone here, and that alone has given me a kind of confidence I did not have before. I have also done quite a few solo trips since moving here, and every single one has taught me something new.&lt;/p&gt;

&lt;p&gt;Every day feels like I am building a new version of myself. New experiences, new lessons, sometimes uncomfortable ones, but all of it adding up to someone I am genuinely proud of becoming.&lt;/p&gt;

</description>
      <category>career</category>
      <category>education</category>
      <category>learning</category>
    </item>
    <item>
      <title>From MEAN Stack Beginner to Falling in Love with Frontend 💻</title>
      <dc:creator>SAVITA WADJE</dc:creator>
      <pubDate>Fri, 21 Aug 2026 11:23:31 +0000</pubDate>
      <link>https://dev.to/savitawadje/from-mean-stack-beginner-to-falling-in-love-with-frontend-34f3</link>
      <guid>https://dev.to/savitawadje/from-mean-stack-beginner-to-falling-in-love-with-frontend-34f3</guid>
      <description>&lt;p&gt;Every developer has that one moment where something just clicks. This is mine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where it all started&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I began my career at a small company as a MEAN stack developer. It was a small team, so you end up touching a bit of everything. That's actually where I got properly introduced to frontend development.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why frontend hooked me&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Honestly? It was the instant feedback. Whatever I wrote, I could see it right there on the browser, immediately. No waiting around, no guessing if it worked. It made me feel like I was actually building something real, not just writing code that disappears into a file somewhere.&lt;/p&gt;

&lt;p&gt;That feeling is what made me fall in love with frontend from the start.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Then JavaScript happened 🧠&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For a while, I could make things work, but I didn't always know why they worked. That changed once I went deeper into JavaScript.&lt;/p&gt;

&lt;p&gt;Suddenly I could actually picture what was happening in the browser. Like, you click one button, and now I could trace it: which event fires, what it triggers, how everything reacts after. That mental picture becoming clear was such a good feeling. Frontend stopped being magic and started making sense.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The path that got me here&lt;/strong&gt;&lt;br&gt;
Nothing planned, it just happened in this order:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;HTML for the structure&lt;/li&gt;
&lt;li&gt;CSS for making it look alive&lt;/li&gt;
&lt;li&gt;JavaScript for making it behave&lt;/li&gt;
&lt;li&gt;Frameworks &amp;amp; libraries for building on top of all that&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each one made the next easier to get. I'm glad I didn't skip around.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Still learning, still building&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'm nowhere near done, still figuring things out as I go, still learning new stuff. &lt;/p&gt;

</description>
      <category>beginners</category>
      <category>career</category>
      <category>frontend</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Angular vs React: How I Decide Which to Use for a New Project</title>
      <dc:creator>SAVITA WADJE</dc:creator>
      <pubDate>Thu, 20 Aug 2026 15:15:22 +0000</pubDate>
      <link>https://dev.to/savitawadje/angular-vs-react-how-i-decide-which-to-use-for-a-new-project-309b</link>
      <guid>https://dev.to/savitawadje/angular-vs-react-how-i-decide-which-to-use-for-a-new-project-309b</guid>
      <description>&lt;p&gt;&lt;strong&gt;The wrong question&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;"Angular vs React, which is better?" is the wrong question. Both are mature, well-supported, and can build the same things. The better question is: which one fits this specific project, team, and timeline? Here's how I actually think about it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When I reach for Angular&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Large, long-lived enterprise apps — Angular's opinionated structure (modules, services, DI) pays off when a team of 10+ devs needs consistency over years, not just weeks.&lt;/li&gt;
&lt;li&gt;Teams that want batteries included — routing, forms, HTTP client, and testing tools all come built-in. Less time spent choosing libraries, more time building.&lt;/li&gt;
&lt;li&gt;TypeScript-first teams — Angular is TypeScript by default, so if your team already thinks in strict typing, it feels native rather than bolted on.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;When I reach for React&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fast-moving products, startups, MVPs — React's flexibility means you can ship quickly without committing to a rigid structure upfront.&lt;/li&gt;
&lt;li&gt;Teams that want to pick their own stack — state management, routing, styling — React lets you choose (Redux vs Zustand, React Router, Tailwind vs CSS-in-JS), which is powerful if your team has strong opinions.&lt;/li&gt;
&lt;li&gt;Hiring pool matters — React's ecosystem is larger, so if you're scaling a team fast, there's usually a deeper talent pool to pull from.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The trade-off nobody talks about enough&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Angular's structure feels restrictive early on but saves you from "a thousand ways to do the same thing" chaos later. React's flexibility feels great early on but can turn into inconsistency across a codebase if the team doesn't agree on conventions upfront.&lt;/p&gt;

&lt;p&gt;In other words: Angular front-loads discipline. React front-loads speed — and asks you to add discipline yourself, later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My rule of thumb&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Enterprise app, long timeline, larger team → Angular&lt;/li&gt;
&lt;li&gt;MVP, startup, small team, need to move fast → React&lt;/li&gt;
&lt;li&gt;Not sure? Default to whichever your team already knows well — consistency beats "the better tool" almost every time.&lt;/li&gt;
&lt;li&gt;What's your experience?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'd love to hear how others make this call — especially if you've switched from one to the other mid-project. Drop your take in the comments.&lt;/p&gt;

</description>
      <category>angular</category>
      <category>frontend</category>
      <category>react</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
