<?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: Srinaadd Pemmasani</title>
    <description>The latest articles on DEV Community by Srinaadd Pemmasani (@srinaadd_pemmasani_28999b).</description>
    <link>https://dev.to/srinaadd_pemmasani_28999b</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3943769%2F559a795f-1a9c-4905-b506-3fc14634b6c0.jpg</url>
      <title>DEV Community: Srinaadd Pemmasani</title>
      <link>https://dev.to/srinaadd_pemmasani_28999b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/srinaadd_pemmasani_28999b"/>
    <language>en</language>
    <item>
      <title>HOW DO YOU FEEL??</title>
      <dc:creator>Srinaadd Pemmasani</dc:creator>
      <pubDate>Thu, 21 May 2026 09:57:40 +0000</pubDate>
      <link>https://dev.to/srinaadd_pemmasani_28999b/how-do-you-feel-4n5d</link>
      <guid>https://dev.to/srinaadd_pemmasani_28999b/how-do-you-feel-4n5d</guid>
      <description>&lt;p&gt;Quick context before I get into it :— second year at IIT Guwahati, MnC branch, applying for SWE internships. I had one SQL course and one lab before this. Everything else I'd be figuring out while building.&lt;br&gt;
-I want to be upfront: I haven't built this yet. I'm posting before I start because I've seen people waste time on projects that they later think are useless. So help me if possible.&lt;br&gt;
What I'm planning ::-&lt;br&gt;
-An analytics engine on the complete IPL ball-by-ball dataset (~200k delivery records, 2008–2024). The angle is SQL depth — not a dashboard, not a MERN app, just genuinely hard database work.&lt;br&gt;
The things I want to implement:&lt;/p&gt;

&lt;p&gt;Window functions — rolling batting form with ROWS BETWEEN frame clauses, milestone tracking, partnership analysis using LAG()&lt;br&gt;
Recursive CTE for winning streaks (gaps and islands problem)&lt;br&gt;
AFTER INSERT trigger keeping a pre-aggregated stats table in sync so career totals don't need full recomputation on reads&lt;br&gt;
EXPLAIN-based index optimization with actual before/after benchmarks&lt;br&gt;
A small Python pipeline pulling from Cricsheet's raw JSON (not the cleaned Kaggle CSV) with extract, validate, load steps&lt;br&gt;
Four FastAPI endpoints wrapping the stored procedures so there's something you can actually hit&lt;/p&gt;

&lt;p&gt;Why I think this might be worth it&lt;br&gt;
-- The stuff I listed above — recursive CTEs, trigger-based materialization, covering index strategies — I don't see that often in undergrad portfolios. I might be wrong about that.&lt;/p&gt;

&lt;p&gt;Why I'm not sure&lt;br&gt;
The IPL dataset is genuinely overused. I know that. The Cricsheet pivot helps a bit since the raw JSON needs actual transformation work, but it's still cricket data which every analytics tutorial seems to use.&lt;br&gt;
I'm also not sure whether "deep SQL" reads as impressive to an SWE hiring manager or whether they just want to see another React project.&lt;br&gt;
:::so help me to decide weather this is worth keeping in resume:::&lt;br&gt;
What I'm actually asking&lt;br&gt;
Is SQL depth a differentiator in 2025 intern resumes or is it invisible to most SWE hiring managers? Would you shortlist this or skip it?&lt;br&gt;
If the consensus is skip it, I'd genuinely rather know now.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>sql</category>
    </item>
  </channel>
</rss>
