DEV Community: Simran ✦ Web Developer

DSA, Web Dev, or AI — What Should Beginners REALLY Learn First?

Simran ✦ Web Developer — Mon, 23 Feb 2026 06:14:59 +0000

Introduction: The Beginner’s Confusion

If you’re new to tech, you’ve probably heard these three words everywhere:

DSA. Web Development. AI.

Everyone online has an opinion.

One person says: “Do DSA first.”

Another says: “Build projects, do web dev.”

Another says: “AI is the future, learn AI now.”

As a beginner, this creates confusion, pressure, and fear of choosing the “wrong path.”

Here’s the truth:

There is no single correct answer, but there is a smart order.

This blog will help you understand:

What each field actually means
What beginners think they are
What beginners should learn first
How to choose based on your goals

Understanding the Three Paths

1. DSA (Data Structures & Algorithms)

What it really is:

Logical problem-solving using arrays, strings, recursion, trees, graphs, and algorithms.

What beginners think:

“DSA = coding interviews.”

Reality:

DSA trains your thinking, not just your coding.

It builds:

Logical reasoning
Problem-solving mindset
Pattern recognition
Code efficiency

DSA doesn’t make apps.

DSA doesn’t build websites.

DSA builds brains.

2. Web Development

What it really is:

Building real products: websites, apps, platforms, dashboards, systems.

What beginners think:

“Web dev = HTML + CSS only.”

Reality:

Web dev teaches:

System thinking
Real-world problem solving
APIs
Databases
Authentication
Architecture
Debugging
Product building

Web dev builds visible results.

3. AI / Machine Learning

What it really is:

Math + data + programming + statistics + models + logic.

What beginners think:

“AI = using ChatGPT or tools.”

Reality:

AI requires:

Programming foundations
Data handling
Algorithms
Math
Probability
Logic
Structured thinking

AI is not beginner-friendly without foundations.

The Biggest Lie Beginners Are Told

“You must choose one path at the start.”

This is wrong.

Tech is not a single-lane road.

It’s a layered system.

You don’t choose one,

You build in layers.

The Smart Learning Order (Beginner Friendly)

Here’s the most practical path for beginners:

Step 1: Programming Fundamentals

Before anything else:

One language (Python / JavaScript / Java / C++)
Variables
Loops
Conditions
Functions
Basic logic
Input/output

No foundation = no growth.

Step 2: Basic DSA + Problem Solving

Not hardcore competitive coding, but:

Arrays
Strings
Basic recursion
Searching
Sorting
Pattern problems
Logical thinking

This builds thinking ability.

Step 3: Web Development (Project Building Phase)

Now start building:

HTML, CSS, JS
Frontend frameworks
Backend basics
Databases
APIs
Authentication
Real projects

This builds confidence + skill + portfolio.

Step 4: AI / ML (When Foundation Is Ready)

Now AI makes sense:

Data handling
Python
Logic
Algorithms
Math foundations
Real understanding of models

Without foundation, AI becomes copy-paste learning.

So What Should Beginners Actually Learn First?

The honest answer:

Learn how to think, then learn how to build, then learn how to specialize.

In simple words:

Learn programming basics
Learn problem-solving (DSA basics)
Build real projects (Web Dev)
Then choose specialization (AI, ML, Data, DevOps, etc.)

Different Goals = Different Focus

If your goal is jobs:

Programming
DSA
Web dev projects
System understanding

If your goal is startups:

Web dev
Product building
Systems
Scaling thinking

If your goal is research/AI:

Math
Programming
Algorithms
Data
Then AI/ML

Final Truth Beginners Need to Hear

You don’t need to rush into AI.

You don’t need to master DSA on day one.

You don’t need to build startups immediately.

What you need is:

Clarity
Consistency
Foundations
Patience
Daily progress

Because in tech:

Skills compound. Knowledge stacks. Progress multiplies.

Closing Thought

If you’re a beginner and confused between DSA, Web Dev, and AI, remember this:

Strong foundations create strong careers.

Strong thinking creates strong coders.

Strong systems create strong builders.

Start simple.

Build slowly.

Grow deeply.

And choose smartly.

Which Is Harder: Frontend or Backend? My Honest Experience + What I Found After Research

Simran ✦ Web Developer — Fri, 05 Dec 2025 05:43:57 +0000

A few days ago, a discussion started trending on X about which side of web development is harder : Frontend or Backend.

Developers from diverse backgrounds shared their opinions, and the responses were surprisingly divided.

As I went through the different tweets, I noticed the same points coming up again and again.

Some developers said frontend development feels tougher because of design work, UI consistency, and how quickly tools change.
Others argued that backend development is the real challenge because it involves deeper logic, databases, and system-level thinking.

It reminded me of my own learning journey, where I was learning full-stack development and making projects. Trying them myself made the differences a lot clearer, and honestly, both have their own kind of difficulty.

Here’s what stood out to me during that journey.

My Experience With Frontend:

When I first wrote HTML and CSS, I genuinely thought:

“Frontend is so easy.
This looks fun.
I can do this all day.”

Adding interactivity with JavaScript also felt exciting, because who doesn't like building and seeing beautiful UIs on their browser?

Where Frontend Started Feeling Hard

But as I started learning React, I realised,

Managing state is harder than it looks.
Every framework has a new version by the time you finish learning the old one.
Your UI looks perfect on your laptop, but needs to be set according to your phone and tablet too.
Advanced CSS can make you question whether to make that little change or just leave it as it is.

I once spent a few hours trying to fix a single button that looked misaligned. I changed padding, margin, display types, everything. Then I discovered I forgot to remove one old CSS line from the top of the file which was overriding my new styles.

Frontend humbles you in ways you don’t expect.

But the happiness when something finally becomes responsive?Peak dopamine.

My Experience With Backend:

When I first started learning backend development, I felt surprisingly confident. Everything looked logical and structured, and I thought:

“Okay, this makes sense.
Just routes, data, and some functions.
I can handle this.”

Building my first simple API even made me feel like I had unlocked a new level of “real programming.”

Where Backend Started Feeling Hard

But as I continued learning and working on projects, I quickly realised backend has its own challenges:

One tiny mistake can break an entire route.
Databases need proper structure, relationships, and planning.
Authentication and security feel like a separate subject altogether.
Debugging isn’t visual, you don’t “see” what’s wrong, things just silently fail.
Errors don’t always explain themselves… sometimes they don’t appear at all.

There was this one time when I was working on a simple login API. Everything looked perfect, the route was set, the controller was clean, and the database was connected (at least I thought it was).

But no matter what I tried, the login request kept failing. Postman was just returning an empty object. Not even an error message.

I checked the code line by line. I rewrote the route. I restarted the server at least five times.

And after almost an hour of frustration, I found the real issue:

I had spelled "password" as "passwrod" in the database model.

One tiny typo. In one field. Hidden deep inside the schema.

That moment was a perfect reminder of what backend really is:
A small mistake in the wrong place can confuse the entire system.

But when you finally fix it and everything starts working, the login succeeds, the data flows correctly, the server responds, it feels incredibly satisfying.

A different kind of victory compared to frontend, but just as rewarding.

What I Realized After Trying Both + Researching

After actually doing both sides (and Googling people's opinions), here’s what I understood:

Frontend feels harder when:

You hate design
You get irritated by layout shifts
You prefer logical tasks over creative ones

Backend feels harder when:

You don’t enjoy pure logic
Databases confuse you
You want visual feedback

There’s no universal “harder”.There’s only which one fits your brain better.

Which One Should You Choose?

Here’s the simplest breakdown:

Choose Frontend if

You enjoy making things look good
You love UI/UX
Animations excite you
You want fast results on screen

Choose Backend if

You prefer logic
You like working with data
You want to build the “brains” behind apps
You enjoy problem-solving deeply

Choose Full-Stack if

You want to be the villain who suffers both sides, and you enjoy both logic and design.

My Final Verdict

After trying both, I can confidently say:

Neither is harder. They’re just different types of hard.

Frontend comes with design problems. Backend comes with logic.

Pick the kind of pain you’re okay with. That’s literally it.

And personally, I prefer Frontend, not because it’s easier (trust me, it’s not), but because it just clicks with how I like to work. I love seeing beautiful UIs, different layouts, playing with colours, and building different types of websites.

There’s something really satisfying about taking an empty page and turning it into something that actually looks and feels good. The instant visual feedback just keeps me motivated to keep experimenting and improving.

[Boost]

Simran ✦ Web Developer — Mon, 10 Nov 2025 13:19:37 +0000

Lightning Developer

Nov 10 '25

From Localhost to Live: Sharing Django Projects Seamlessly

#webdev #django #pinggy #tutorial

Comments 1

4 min read

The Truth About ‘Building in Public’: What No One Tells You

Simran ✦ Web Developer — Sat, 08 Nov 2025 05:52:13 +0000

Everyone says:

Build in public.
Share your journey.
Be transparent.

But no one talks about how it actually feels.

In the beginning, I used to post like I was talking to myself —

No likes, no responses.

And honestly?
That’s where most people quit.

We see the big wins shared online:

“Just landed 1,000 users!”
“Launched my MVP!”
“Hit my first revenue milestone!”

Building in public looks like a badge of authenticity.

But behind those updates is a much quieter, more complicated emotional experience —

One that rarely makes it to the timeline.

So let’s talk about the part no one explains.

What Does “Building in Public” Actually Mean?

Building in public is a storytelling strategy.

It means sharing your journey, your wins, your mistakes, your experiments, as they happen.

Building in Public is:

Sharing stories (wins/losses)
Being vulnerable and transparent
Inspiring a community through honesty

Building in Public is not:

A shortcut to fame
A growth hack to go viral
A trick to get users fast

Why “Building in Public” Took Over the Internet

Around 2020–2021, something shifted.

Indie hackers and solo founders began sharing:

Revenue dashboards
Feature releases
Weekly learnings
MRR breakdowns

People like Pieter Levels, Arvid Kahl, and the Indie Hackers community didn’t just build products —

They built audiences by sharing the process.

Why did it resonate?

Authenticity felt refreshing compared to polished PR
It created accountability for solo builders
It formed communities around products before launch

From the outside, it looked like a cheat code:

"Share progress → Gain followers → Grow fast."

But if you’ve actually tried it, you know:

It’s never that simple.

The Hidden Pressure Behind Transparency

When you build in public, your journey stops being just yours.

You start documenting progress daily.

It creates an invisible pressure to keep proving you're still building.

When I started posting updates daily on X, it felt exciting.

But soon, something changed:

I wasn’t just building anymore.
I was performing progress.
On days I coded for hours but had nothing “tweet-worthy,” I felt like I had failed.
I wondered if the small audience watching me thought I had given up.

When Sharing Becomes the Work

This was the hardest realization:

The more you think about what to share, the less you actually build.

I once spent 40 minutes crafting a tweet about a feature that took 10 minutes to code.

Not because the tweet mattered —

But because I wanted it to look like progress.

Soon, my decisions were influenced by metrics:

“Should I build this?” → Will this make a good update?
“Should I rest today?” → What if people think I stopped?

To fix this, I shifted from daily updates to weekly reflections.
Less pressure.
More meaning.
More real.

The Fear of Failing Publicly

When you fail privately, you close the tab and move on.

When you fail publicly, you feel like you have to announce your failure too.

And reality check:

Wins → get engagement
Failures → get silence

But here’s the truth:

A publicly shared failure teaches more than a polished success ever will.

Someone needs to see the part where you didn’t know what you were doing.

The Real Benefits (When Done Gently)

When approached with intention, building in public can be life-changing:

You attract people who resonate with your story.
You get feedback before launching.
You build trust, not hype.
You find collaborators, mentors, friends.

Once, I posted about something I was struggling with.

Someone DMed me:

“Thank you for saying this. I thought I was the only one.”

That felt more meaningful than any retweet count.

Build With the Public, Not For the Public

This is the shift:

Don’t share to impress.
Share to connect.

What you learned today
What broke and how you fixed it
A thought process behind a decision
Why you scrapped a feature

Your journey is supposed to inspire and support people, not drain you!

Final Thoughts

Building in public isn’t for everyone, and that’s okay.

Some seasons require silence.
Some require privacy.
Some require slow, unbroadcasted growth.

The key is to remember:

Build for yourself.
Share for others.
But never let the audience decide your pace.

Your Turn

Have you tried building in public?

Did it feel:

Exciting?
Exhausting?
Or both?

Share your experience below. I’d love to read it 👇

Exploring Web Development with Python: A Beginner’s Journey to Building Dynamic Websites

Simran ✦ Web Developer — Sat, 12 Apr 2025 06:21:58 +0000

👉 Introduction

Web development is an exciting field, and my journey into it has been a rewarding one. I’ve always been fascinated by how websites and applications come to life. After learning HTML, CSS, and JavaScript, I was unsure which language to choose for the backend that would allow me to dive deeper and become more versatile — that’s when I decided to go with Python.

👉 What I Learned in Web Development with Python

🔹 Core Concepts

One of the first things I learned was the importance of web development fundamentals:

Understanding HTTP and the request-response cycle
How web servers work
The importance of writing clean and maintainable code

I also strengthened my Python basics, including:

Data types & control structures (lists, dictionaries, loops, conditionals)
Functions and modules
File handling and error handling
Object-Oriented Programming (OOP) – especially useful with Django

🔹 Frameworks

Choosing the right framework is key. I picked Django for its:

Built-in ORM for working with databases
Admin interface for easy management
Form handling and validation system

What I loved about Django:

URL Routing System – Clean and flexible
Authentication System – Login, logout, password resets, and permissions
Middleware Support – Sessions, CSRF protection, etc.
Security and Scalability – Best practices by default (XSS, CSRF, SQL injection protection)

🔹 Frontend Integration

After understanding how Django works behind the scenes, I learned how it connects with the frontend using:

Django templates ({% %} and {{ }} tags)
Dynamic data rendering from views to templates
Combining frontend (HTML/CSS/JS) with backend logic

This helped me build full-fledged, dynamic web applications.

🔹 Database Management

One of the most impactful lessons was learning to manage databases using Django's ORM.

Worked with MySQL, SQLite, and PostgreSQL
Avoided manual SQL queries
Used Python code to interact with the database efficiently

👉 Learning Resources I Used

My learning journey was guided by a mix of structured courses and online content:

📘 Django Official Documentation
🌐 MDN Web Docs (Django Tutorial)
📺 YouTube Channel: CodeWithHarry
🏫 Web Development Course at Netmax, Chandigarh > This course gave me hands-on practice, mentorship, mini-projects, and real-time feedback. If you’re in Chandigarh, I highly recommend it!

👉 How Data Flows in a Python Web App (Using Django)

Understanding the request-response cycle was a game-changer:

User sends a request via the browser
Django receives and routes it to the appropriate view
View interacts with the model/database
Data is processed and sent to the template
Template renders dynamic content and sends a response back to the browser

👉 Benefits of Using Python for Web Development

1) Readable & Clean Syntax

Python’s simplicity and readability make it ideal for both beginners and experienced developers.

2) Versatility & Full-Stack Potential

Python isn’t limited to web dev — it excels in data analysis, automation, and AI/ML, making it perfect for full-stack development.

3) Rich Ecosystem

Django and Flask for web frameworks
Requests, Celery, etc., for added functionality
Save time with fewer lines of code

4) Community Support

A large and active community means endless tutorials, forums, and documentation to help you overcome challenges and grow your skills.

5) Integration with Data Science & AI

Python’s tools like Pandas, NumPy, Scikit-Learn, and TensorFlow make it a powerful choice for developers looking to integrate AI/data features into web apps.

👉 Conclusion

Web development with Python has been an incredibly rewarding journey. The language’s simplicity, powerful frameworks, and community support helped me build real-world applications and level up as a developer.

If you’re starting your web development journey or want to expand your skills, give Python a try. It’s not just great for building websites — it’s a gateway into the future of data-driven and AI-powered applications.

💬 Have You Used Python for Web Development?

What tips or challenges did you face in your journey? I'd love to hear your experience!

Building a Quiz App with Python and Tkinter – Step-by-Step Guide

Simran ✦ Web Developer — Wed, 05 Mar 2025 13:33:09 +0000

📝 Introduction

Building a Quiz App using Python and Tkinter was an exciting journey! I wanted to create a project that not only strengthens my Python programming skills but also provides an interactive user experience. A quiz app is a great way to combine GUI development, database management, and logical programming into a single project.

🎯 Features

User Authentication: Admin and Player login integrated into the same window.
Question Database: Managed with MySQL to store questions dynamically.
Interactive UI: Tkinter-based graphical interface with smooth transitions.
Real-time Score Tracking: Displays correct/incorrect answers with a progress indicator.
Result Summary: Shows final score and performance analysis.

🛠️ Tech Stack

Python (Core language)
Tkinter (GUI framework)
MySQL (Database for storing questions & user data)

🗄️ Database Setup

Before running the app, make sure to configure your MySQL database:
Step 1 : Create the database

CREATE DATABASE quiz_app;

Step 2 : Create the tables

USE quiz_app;

CREATE TABLE table_name (
    column1 INT AUTO_INCREMENT PRIMARY KEY,
    column2 VARCHAR(50) NOT NULL,
    column3 BOOLEAN NOT NULL
);

Step 3 :Configure Connection in database.py
Inside database.py, set up the MySQL connection with your local credentials:

host : usually localhost
user : your MySQL username
password: your MySQL password
database: quiz_app

Also, make sure to define and export conn, cursor, and mysql so they can be imported in other files.
🛠️ If you see ImportError: cannot import name 'conn' from 'database', it means the connection variables are either not defined or not properly exported in database.py.

🚀 How to Run

Step 1 Clone the repository:

   git clone https://github.com/SIMRAN-202/Tkinter-Quiz-App

Step 2 Install Dependencies:

   pip install mysql-connector-python

Step 3 Run the Application:

   python main.py

🏆 Challenges Faced & Solutions

Issue: Handling database connectivity dynamically.
- Solution: Used MySQL Connector with parameterized queries.
Issue: UI not updating correctly after answering a question.
- Solution: Used Tkinter’s after() method to refresh UI state smoothly.
Issue: Managing different user roles (Admin & Player) in the same window.
- Solution: Implemented a single login window with role-based access control.

🎉 Accomplishments

Successfully built a fully functional quiz app with dynamic questions.
Implemented real-time score tracking and user-friendly UI.
Learned efficient database management and Tkinter best practices.

📌 Future Improvements

Add multiple question types (MCQs, fill-in-the-blanks, etc.).
Implement a leaderboard for competitive play.
Integrate Django for a web-based version in the future.

🤝 Contributing

If you’d like to contribute, feel free to fork the repository and submit a pull request! 🙌

📞 Contact

📧 Email: kaursimrankaur2003@gmail.com
🔗 LinkedIn: https://www.linkedin.com/in/simran-ba0595315/

Built with 💙 by Simran