Amit | SQL • JS • Python

I'm a CA student learning tech to move into Data Analytics. Currently learning: • SQL • Python for data analysis • JavaScript Also working on discipline through fitness. Sharing the journey and lessons along the way.

@PythonDvz b)

Comment your answer

@shedbody Attention gets the opening weekend. Story gets the long-term success. A great trailer should spark curiosity, not spoil the plot. 👀

@AmitKumarDev_ Fair point 😄 But some average stories have become massive openings purely because the trailer nailed the hype. What matters more for a trailer: getting attention or revealing a great story? 🤔

AI just analyzed the biggest Spy Universe clash yet. ⚔️ War 2 vs Alpha 🤖 PlotPoint AI Verdict: 🏆 Winner: Alpha Battle Score: Alpha 42 - 41 War 2 Agree with the AI or is War 2 still the stronger contender? Vote: 🔥 Alpha ⚡ War 2 plotpoint.amitforge.com #Alpha #War2 #PlotPoint

@shedbody Story > Hype > Action > Music A great trailer can create hype, but only a great story survives opening weekend. 👀🔥

@AmitKumarDev_ What factor matters most to you when judging a movie trailer? Hype, Story, Music, Action, or Rewatch Potential?

@GithubProjects github.com/Amit-K-Dev

|￣￣￣￣￣￣￣￣￣￣￣￣￣￣| | Share your GitHub profile | |＿＿＿＿＿＿＿＿＿＿＿＿＿＿| \ (•◡•) / \ / —— | | |_ |_

@DataCamp Which window function do people find themselves using most often in real projects: LAG(), LEAD(), or ROW_NUMBER()? For me it's usually ROW_NUMBER().

SQL window functions will change how you write queries. RANK(), LAG(), LEAD(), ROW_NUMBER()—one line each, no subquery needed. What they do: → ROW_NUMBER = unique rank per row → RANK = rank with tie gaps → LAG = previous row value → LEAD = next row value Worth adding to your toolkit. #SQL #DataCamp

After months of learning, rebuilding, and late-night coding… amitforge.com⁠ is officially LIVE. Built with: • Next.js • React • TypeScript • Tailwind CSS • Cloudflare More products coming soon #AmitForge #NextJS #ReactJS #TypeScript #Cloudflare #BuildInPublic

Once this is clear, writing queries becomes much easier. #SQL #DataAnalytics

Instead of starting with SELECT, I now start with questions: • What data do I need? • Where is it stored? • What conditions apply?

A simple mindset shift that made SQL easier for me:

11 weeks of showing up. Not trying to go viral. Not pretending to be an expert. Just building real skills slowly. That’s the focus. #LearningInPublic

Balancing CA, coding, and fitness isn’t about perfect planning. It’s about showing up even on low-energy days. #Consistency #GrowthMindset

This makes both Python and JavaScript much easier to understand. #Coding #JavaScript

Writing the logic in plain English before writing actual code.

One coding habit that is helping me a lot:

For people learning data analytics: What was harder for you? 1. SQL 2. Python 3. Understanding datasets Curious to see different experiences. #SQL #Python #LearningInPublic

If the dataset is confusing, the output will be too. #Python #DataAnalysis

Libraries like pandas are powerful. But they don’t replace understanding the data.

Learning Python for data analysis taught me something important:

SQL becomes easier when you stop memorizing queries and start thinking in questions. What do I need? Where is it? How do I filter it? #SQL #LearningInPublic