The latest articles on DEV Community by Aadit Bhatia (@aaditbhatia1). https://dev.to/aaditbhatia1 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3843565%2Fd2a08a13-7a61-42dd-9a0a-c9125f9929f0.jpeg https://dev.to/aaditbhatia1 en Aadit Bhatia Tue, 19 May 2026 15:28:05 +0000 https://dev.to/aaditbhatia1/my-first-day-as-an-swe-intern-at-a-startup-the-importance-of-qa-kcp https://dev.to/aaditbhatia1/my-first-day-as-an-swe-intern-at-a-startup-the-importance-of-qa-kcp <p>Hi everyone! </p> <p>Yesterday was my first day of work at my first internship, and I have a few thoughts I want to get off my chest. I'm currently working at Treevah as an SWE intern, entirely remote.</p> <p>The first thing I've realized after just a day is that QA work(something I thought to be entirely separate from SWE work) is very intertwined with what I'll be doing in the near future. My first task has been simply getting used to the app itself and playing around with it, seeing if I can find bugs related to coreflow blockages, UI/UX issues, and other issues I can find on a P0-P3 framework. </p> <p>For the first hour or so of work, I thought it was pretty easy work, if not a little boring. But it wasn't until I got deeper into the app that I realized just how important QA work is, not just for the client but for the developers behind the product as well. </p> <p>QA work is obviously important to ensure that your client is receiving a polished version of a product, but what I've come to understand in a short time is that QA work gives developers the "mindset" needed to create solid products. Specifically, it allows SWEs to understand all of the different criteria that must be checked off in order for a product to be considered "polished". </p> <p>To put it in more polished terms, doing QA work, in my eyes, allows developers to create work that's able to adhere more to the design-by-contract design philosophy.</p> <p>I came into this internship expecting to start off with learning the company's stack and how to use it, but the first day ended up being something even more valuable: I began to learn how to <em>think</em> like an engineer!</p> qa programming beginners career Aadit Bhatia Wed, 22 Apr 2026 20:57:52 +0000 https://dev.to/aaditbhatia1/from-the-ground-up-a-journey-2el6 https://dev.to/aaditbhatia1/from-the-ground-up-a-journey-2el6 <p>Hi! My name is Aadit Bhatia, and I'm a freshman at The Ohio State University studying Computer Engineering. As someone trying to enter a job market currently dominated by talks of either the glory of AI or the doom that it'll bring us, it becomes very tempting to rely on tools like Claude Code for everything. However, that's not how you learn, and my view is that if you replace junior developers with AI, you'll never get a senior developer. </p> <p>Therefore, I'm starting a series to document my entire journey of learning software, hardware, and everything in between! You'll get to see the good, the bad, the clean, and the dirty parts of software development, all in the hopeful goal of showing that AI can't replace you if you're good enough.</p> <p>I'll be documenting my journey in learning web dev tools(React.js, Node.js, Microsoft Azure), then move to other parts of software development and even hardware development in the future. See you soon!</p> <p>-Aadit Bhatia </p> webdev learning beginners