DEV Community: Ashish prajapati

🚀 Spring Boot Journey – Day 6: Securing My Application with Spring Security

Ashish prajapati — Fri, 17 Jul 2026 15:54:30 +0000

Welcome to Day 6 of my Spring Boot learning journey! 🔐💚

After building a complete Product Management System with a modern UI, it was time to make the application secure.

A real-world application isn't just about displaying data—it also needs to ensure that only authorized users can access sensitive features. Today, I explored Spring Security and learned how to implement Authentication and Authorization in a Spring Boot application.

🛡️ Adding Spring Security

The first step was adding the Spring Security dependency to my project.

Once added, Spring Boot automatically secured the entire application by providing a default login page.

This was my first introduction to how easily Spring Boot can protect web applications with minimal configuration.

🔑 Understanding Authentication

Authentication answers one simple question:

"Who are you?"

Spring Security provides multiple ways to authenticate users.

1️⃣ Default Authentication (Auto Generated)

This is Spring Boot's default behavior.

Username: user
Password: Automatically generated and printed in the console.

Every time the application restarts, a new password is generated.

While useful for testing, this isn't suitable for real applications because the password changes every time.

2️⃣ Username & Password in Properties File

The second approach is to configure credentials directly inside the application's properties file.

This allows developers to define a fixed username and password without relying on randomly generated credentials.

It's simple and useful for small demo projects but still not ideal for production systems.

3️⃣ Custom Authentication

Today I explored two custom authentication strategies:

✅ In-Memory Authentication

With In-Memory Authentication, users are stored directly inside the application.

I created multiple users with different roles such as:

ADMIN
USER

Passwords were encrypted using BCryptPasswordEncoder, ensuring they were stored securely rather than in plain text.

This approach is great for learning, testing, and small applications.

✅ DAO Authentication

The most exciting part of today's session was implementing DAO Authentication.

Instead of hardcoding users, authentication now happens using data stored inside the database.

The application fetches user details dynamically through a custom UserDetailsService.

This approach is much closer to how authentication works in production applications.

🔒 Understanding Authorization

Authentication identifies the user.

Authorization decides what that user is allowed to do.

Using Spring Security, I configured role-based access control.

For example:

👤 USER

View Products
Add Products

👨‍💼 ADMIN

View Products
Add Products
Update Products
Delete Products

This ensures that sensitive operations are restricted to authorized users only.

🔑 Password Encryption

One important lesson today was never storing passwords in plain text.

I used BCryptPasswordEncoder, which hashes passwords before saving or comparing them.

This is one of the most important security practices in modern web applications.

👥 Custom UserDetailsService

To connect Spring Security with the database, I implemented a custom UserDetailsService.

Its responsibilities include:

Searching users in the database
Validating usernames
Returning user information to Spring Security
Loading user roles and permissions

This allows Spring Security to authenticate users using database records instead of hardcoded values.

🗃️ Role-Based Database Design

To support multiple roles, I designed separate database tables for:

Users
Roles

These tables are connected through a relationship table, allowing a user to have one or more roles.

This design is flexible and scalable for real-world applications where permissions may grow over time.

🔄 Security Flow

User Opens Application

⬇️

Spring Security Login Page

⬇️

Authentication

⬇️

Database Verification

⬇️

Load User & Roles

⬇️

Authorization Check

⬇️

Grant or Deny Access

⬇️

Application Dashboard

📚 What I Learned Today

✅ Spring Security

✅ Authentication

✅ Authorization

✅ Default Login Page

✅ In-Memory Authentication

✅ DAO Authentication

✅ UserDetailsService

✅ UserDetails

✅ AuthenticationProvider

✅ BCrypt Password Encoding

✅ Role-Based Authorization

✅ SecurityFilterChain

✅ Access Control

💡 My Biggest Takeaway

Today's session completely changed my understanding of backend development.

Building APIs and beautiful user interfaces is important, but without proper security, an application isn't ready for real users.

Learning how Spring Security handles authentication and authorization gave me a glimpse into how enterprise applications protect sensitive data and manage user access.

With database-backed authentication and role-based authorization, my application now feels much closer to a production-ready system.

🚀 What's Next?

In the next stage of my journey, I plan to explore:

Registration Module
User Signup
Custom Login Page
JWT Authentication
OAuth2
Session Management
Remember Me
Email Verification
Password Reset

Every new concept brings me one step closer to becoming a full-stack Java developer. 💚

#SpringBootJourney Day 6

Today's Achievements:

✔ Spring Security Integration

✔ Authentication

✔ Authorization

✔ Default Login Page

✔ In-Memory Authentication

✔ DAO Authentication

✔ BCrypt Password Encoding

✔ Database Users & Roles

✔ Role-Based Access Control

✔ Secure Product Management System

Security isn't an extra feature—it's the foundation of every modern application. 🔐🚀

🚀 Spring Boot Journey – Day 5: Building a Complete Product Management UI with CRUD Operations

Ashish prajapati — Thu, 16 Jul 2026 17:36:58 +0000

Welcome to Day 5 of my Spring Boot learning journey! 💚

After creating my first user interface with Thymeleaf and Tailwind CSS, today's goal was to make the application fully interactive.

Instead of just displaying products, I implemented a complete Product Management System where users can create, update, delete, search, and even upload product images—all through a clean web interface.

This felt like my first real-world CRUD application.

🎯 What I Built Today

Today's application supports complete CRUD (Create, Read, Update, Delete) operations directly from the browser.

Users can now:

✅ View all products

✅ Add a new product

✅ Update existing products

✅ Delete products

✅ Filter products by category

✅ Upload product images

Everything happens through the UI without needing Postman.

📝 Product Registration Form

One of the biggest additions today was creating a product registration form.

Instead of sending JSON requests manually, users can now enter product details through a web form.

Spring Boot automatically maps the form fields to the Product object using:

@ModelAttribute

This makes form handling simple and eliminates the need for manually extracting request parameters.

🖼️ Image Upload

Today's most exciting feature was adding image upload support.

Using MultipartFile, users can now upload a product image while creating a new product.

The application:

Receives the uploaded image
Creates an uploads directory if it doesn't exist
Generates a unique filename
Saves the image locally
Stores the image path in the database

This was my first experience handling file uploads in Spring Boot, and it made the application feel much more like a real e-commerce system.

✏️ Updating Products

I also implemented the Update functionality.

When the user clicks the Edit button:

The selected product is loaded.
Existing data is displayed in a form.
Users can modify the details.
The updated information is saved back to the database.

This taught me how to pre-fill forms with existing data and update records efficiently.

❌ Delete Functionality

Deleting products became much easier today.

Users can simply click the Delete button, and Spring Boot removes the selected product from the database.

Simple, fast, and user-friendly.

🔍 Category-Based Search

To improve the application further, I added category filtering.

Now users can browse products based on their category instead of scrolling through the entire list.

This feature demonstrates how backend filtering can provide a much better user experience.

🎨 Improving the UI

The project now feels much more complete thanks to Tailwind CSS.

Today's improvements include:

Responsive forms
Styled buttons
Product cards and tables
Better spacing
Hover animations
Cleaner layout
Improved user experience

The application is becoming more polished with every update.

🔄 Complete Application Flow

Browser

⬇️

Thymeleaf Form

⬇️

Controller

⬇️

Service

⬇️

Repository

⬇️

MySQL Database

⬇️

Updated UI

This flow helped me understand how frontend and backend work together in a Spring Boot MVC application.

📚 What I Learned Today

✅ Spring MVC Form Handling

✅ @ModelAttribute

✅ MultipartFile

✅ File Upload in Spring Boot

✅ Local File Storage

✅ CRUD Operations through UI

✅ Update Forms

✅ Delete Operations

✅ Category-Based Filtering

✅ Redirect After Form Submission

✅ Dynamic Thymeleaf Pages

💡 My Biggest Takeaway

Today's session was one of the most rewarding so far.

My application has evolved from a simple REST API into a functional web application where users can interact with data through an intuitive interface.

Adding image uploads, CRUD operations, and search functionality made the project feel much closer to a production-ready product.

Every new feature is helping me understand how full-stack applications are built using Spring Boot.

🚀 What's Next?

In the next phase of my journey, I plan to explore:

User Authentication & Login
Spring Security
Pagination & Sorting
Validation
Exception Handling for UI
Dashboard & Analytics
Deploying the Application

The journey continues—one feature at a time. 💚

#SpringBootJourney Day 5

Today's Achievements:

✔ Complete CRUD UI

✔ Product Registration Form

✔ Image Upload

✔ Edit & Delete Products

✔ Category Filter

✔ Dynamic Thymeleaf Pages

✔ Tailwind CSS Interface

From REST APIs to a fully interactive Product Management System—one step closer to building production-ready web applications. 🚀

🚀 Spring Boot Journey – Day 4: Building My First UI with Thymeleaf & Tailwind CSS

Ashish prajapati — Wed, 15 Jul 2026 17:34:56 +0000

Welcome to Day 4 of my Spring Boot learning journey! 💚

Until now, I had been testing all my REST APIs using Postman. While Postman is an excellent tool for API development and testing, it's not something that end users interact with.

So today, I took the next step toward building a real-world application by creating a web interface using Thymeleaf and Tailwind CSS.

🎯 Why Move Beyond Postman?

REST APIs are the backbone of backend development, but users don't interact with APIs directly.

Instead, they use:

Websites
Dashboards
Admin Panels
E-commerce Applications

To bridge the gap between the backend and the frontend, I integrated Thymeleaf into my Spring Boot project.

🛠️ Setting Up Thymeleaf

The first step was adding the Thymeleaf dependency to my project.

Thymeleaf is a Java template engine that allows us to create dynamic HTML pages by rendering data directly from Spring Boot.

After adding the dependency, I created a new folder named:

src
 └── main
      └── resources
            └── templates

Every HTML page that Spring Boot renders is placed inside the templates folder.

📦 Creating the Product Page

Instead of returning JSON responses, I created a controller that returns an HTML page.

The controller fetches all products from the database, stores them inside the Model, and passes that data to the view.

The flow now looks like this:

Browser Request

⬇️

Controller

⬇️

Service

⬇️

Repository

⬇️

MySQL

⬇️

Model

⬇️

Thymeleaf HTML Page

📄 Displaying Dynamic Data

Using Thymeleaf, I displayed all product records inside an HTML table.

Instead of hardcoding values, I used dynamic expressions to display:

Product ID
Product Title
Price
Description
Category

The th:each attribute made it incredibly easy to loop through every product and generate table rows automatically.

This was my first experience connecting backend data directly to the frontend.

🎨 Styling with Tailwind CSS

A plain HTML table works, but it doesn't look very attractive.

To improve the UI, I integrated Tailwind CSS using the CDN version.

With just utility classes, I created:

Clean table layout
Responsive container
Rounded corners
Hover effects
Modern typography
Better spacing
Shadow effects

Without writing a single line of traditional CSS, the page looked much more professional.

🔄 MVC Architecture in Action

Today's project helped me understand the Model-View-Controller (MVC) pattern.

Model

Contains the data fetched from the database.

View

The Thymeleaf HTML page responsible for displaying the data.

Controller

Receives the request, fetches the data from the Service layer, and sends it to the View.

This architecture keeps the application clean, modular, and easy to maintain.

📚 What I Learned Today

✅ Thymeleaf Template Engine

✅ MVC Architecture

✅ Model Object

✅ Passing Data from Controller to View

✅ Dynamic HTML using Thymeleaf

✅ th:each

✅ th:text

✅ Tailwind CSS Integration

✅ Responsive Table Design

✅ Rendering Database Records on a Web Page

💡 My Biggest Takeaway

Today was an exciting milestone in my Spring Boot journey.

Until yesterday, everything existed only as APIs returning JSON responses.

Today, I transformed those APIs into an actual user interface.

Seeing data from MySQL displayed beautifully inside a browser made the application feel much closer to a real-world product.

This also showed me how Spring Boot and Thymeleaf work seamlessly together to build dynamic web applications.

The combination of Spring Boot + Thymeleaf + Tailwind CSS provides a powerful foundation for creating modern, responsive, and user-friendly applications.

🚀 What's Next?

In the upcoming days, I plan to:

Add forms to insert new products
Edit existing products
Delete products from the UI
Upload product images
Build a complete Product Management Dashboard
Make the interface fully responsive

The journey continues, one project at a time. 💚

#SpringBootJourney Day 4

Today's Progress:

✔ Integrated Thymeleaf

✔ Created Templates Folder

✔ Connected Spring Boot with HTML

✔ Passed Data Using Model

✔ Displayed Dynamic Product Data

✔ Styled the UI with Tailwind CSS

From APIs to beautiful user interfaces—one step closer to building complete full-stack applications. 🚀

🚀 Spring Boot Journey – Day 3: Mastering CRUD Operations, Lombok & JPA Query Methods

Ashish prajapati — Mon, 13 Jul 2026 17:14:37 +0000

Welcome to Day 3 of my Spring Boot learning journey! 💚

Today's session was packed with practical concepts that are used in almost every real-world Spring Boot application. I moved beyond creating simple APIs and started building a complete CRUD application while learning how Spring Boot simplifies backend development.

📌 What I Learned Today

Today I implemented the complete CRUD (Create, Read, Update, Delete) functionality for my Student Management application.

The REST APIs now support:

➕ Create a Student
📖 Read all Students
🔍 Read a single Student
✏️ Update Student details
❌ Delete a Student

I also learned how different HTTP methods map to REST APIs:

POST → Create Data
GET → Fetch Data
PUT → Update Data
DELETE → Remove Data

Understanding these methods helped me see how backend APIs communicate with frontend applications.

📚 Adding Multiple Records

Instead of inserting one record at a time, I learned how to save multiple student records using a single API request.

Spring Data JPA provides the saveAll() method, making bulk insertion extremely simple and efficient.

This feature is especially useful when importing large datasets.

⚡ Making Code Cleaner with Lombok

One of my favorite topics today was Lombok.

Previously, every entity required writing:

Constructors
Getters
Setters
toString()
equals()
hashCode()

Now, with just a few annotations like:

@Data
@NoArgsConstructor
@AllArgsConstructor

Lombok generates all that code automatically.

This makes the project cleaner, shorter, and much easier to maintain.

🗄️ Repository Layer with Spring Data JPA

Today I explored the power of Spring Data JPA.

Instead of writing SQL queries manually, Spring Boot generates queries automatically based on method names.

Some custom repository methods I added include:

Find students by department
Find students whose date of birth is after a given date
Find students whose date of birth is before a given date

It was amazing to see that simply naming methods correctly allows Spring Boot to generate the required SQL behind the scenes.

🔍 JPA Query Methods

Today I learned about Query Method Naming in Spring Data JPA.

Examples include:

findByDepartment()
findByDobAfter()
findByDobBefore()

Spring Boot automatically understands these method names and creates the appropriate database queries without requiring any SQL.

This is one of the features that makes Spring Data JPA so powerful and developer-friendly.

⚠️ Exception Handling

Applications should never fail silently.

To improve my project, I implemented exception handling for situations where a student record doesn't exist.

Now, instead of unexpected behavior, the application returns a meaningful error message when someone tries to access or delete a student that isn't available.

This improves both reliability and user experience.

🏗️ Project Architecture

My project now follows the standard layered architecture:

Client Request

⬇️

Controller

⬇️

Service

⬇️

Repository

⬇️

MySQL Database

⬇️

Response

Keeping responsibilities separated makes the application easier to understand, test, and maintain.

📖 Key Concepts Covered Today

✅ CRUD Operations

✅ HTTP Methods (GET, POST, PUT, DELETE)

✅ Bulk Insert using saveAll()

✅ Lombok Annotations

✅ Spring Data JPA Repository

✅ JPA Query Methods

✅ Filtering Data using Repository Methods

✅ Exception Handling

✅ Layered Architecture

💭 My Takeaway

Today's session made me realize how much Spring Boot reduces repetitive work.

With Lombok, I no longer need to write boilerplate code.

With Spring Data JPA, I can fetch filtered data without writing SQL.

And with proper exception handling, my APIs become much more reliable.

Every day I'm getting closer to building production-ready backend applications, and it's exciting to see how everything connects together.

Looking forward to learning more advanced Spring Boot concepts in the coming days! 🚀

#SpringBootJourney Day 3

Today's progress:

✔ CRUD Operations

✔ Lombok

✔ JPA Repository

✔ Query Methods

✔ Exception Handling

One day. One project. One step closer to becoming a Java Backend Developer. 💚

🚀 Spring Boot Journey – Day 2: Setting Up My Development Environment & Building My First REST API

Ashish prajapati — Sat, 11 Jul 2026 17:23:43 +0000

Welcome to Day 2 of my Spring Boot learning journey! 👋

After understanding the fundamentals of Spring Boot on Day 1, today I moved from theory to practice by setting up my complete development environment and building my very first Spring Boot application.

🛠️ Development Environment

To begin my Spring Boot development, I set up the following tools:

Eclipse IDE – For writing and managing Java code.
MySQL – To store application data.
Spring Boot – The backend framework.
Maven – For dependency management and project building.

With everything installed and configured, I was finally ready to write some code.

📦 Creating My First Entity: Product

The first class I created was a simple Product class.

It contains three fields:

id
name
price

Along with that, I manually wrote:

Constructors
Getters
Setters
toString() method

At first glance, the code looks quite lengthy because Java requires a lot of boilerplate code for a simple class.

💡 Note: In upcoming days, I'll learn Lombok, which automatically generates constructors, getters, setters, and other methods, making the code much cleaner and easier to maintain.

🗂️ Understanding Spring Boot Project Structure

To follow Spring Boot's layered architecture, I created three important layers:

📌 Controller Layer

The Controller acts as the entry point for client requests.

I created two REST endpoints:

GET `/get-all`

Retrieves all products.
Returns a list of products wrapped inside a ResponseEntity.
Sends an HTTP 200 OK status.

POST `/save-prod`

Accepts a Product object using @RequestBody.
Saves the product.
Returns the saved product with HTTP 201 CREATED.

Using ResponseEntity allows us to send both the response data and the appropriate HTTP status code.

📌 Repository Layer

Next, I created a ProductRepository.

Instead of writing SQL queries manually, I simply extended:

JpaRepository<Product, Integer>

This provides several built-in database operations like:

save()
findAll()
findById()
delete()
update()

without writing any implementation code.

That's one of the biggest advantages of Spring Data JPA.

📌 Service Layer

The Service layer contains the application's business logic.

Here, I created methods to:

Fetch all products.
Save a new product.

The service communicates with the repository, while the controller communicates with the service.

This layered architecture keeps the code organized and easier to maintain.

🔄 Request Flow

The complete flow of my application looks like this:

Client Request

⬇️

Controller

⬇️

Service

⬇️

Repository

⬇️

MySQL Database

⬇️

Response Back to Client

This separation of responsibilities is one of the core principles of Spring Boot development.

📚 Concepts I Learned Today

✅ Setting up Eclipse for Spring Boot development

✅ Configuring MySQL

✅ Creating a Spring Boot project

✅ Understanding layered architecture

✅ Creating an Entity class

✅ Building a Repository using JPA

✅ Writing a Service layer

✅ Creating REST APIs using @GetMapping and @PostMapping

✅ Using @RequestBody

✅ Returning responses with ResponseEntity

💭 My Takeaway

Today was my first real step into backend development with Spring Boot.

Although the project is simple, it helped me understand how different layers of a Spring Boot application communicate with each other. I also realized why Spring Boot is so popular—it lets developers focus on application logic instead of writing repetitive code.

There's still a lot to learn, but building something that actually runs and responds to API requests feels incredibly rewarding.

Tomorrow I'll continue exploring more Spring Boot concepts and improve this project step by step.

Thank you for following my journey! 🚀

#SpringBootJourney Day 2

Learning never stops.

One concept.

One project.

One day at a time. 💚

🚀 Spring Boot Journey - Day 1: Introduction to Spring Boot

Ashish prajapati — Fri, 10 Jul 2026 15:50:45 +0000

Today I started my Spring Boot learning journey! 🌱

📌 What is Spring Boot?

Spring Boot is an extension of the Spring Framework that makes it easy to build Java applications quickly. It reduces boilerplate configuration and helps developers create production-ready applications with minimal setup.

Instead of spending hours configuring XML files and dependencies, Spring Boot lets you focus on writing business logic.

✨ Key Features

✅ Auto Configuration
Automatically configures your application based on the dependencies you add.

✅ Starter Dependencies
Provides pre-configured dependency bundles like:

spring-boot-starter-web
spring-boot-starter-data-jpa
spring-boot-starter-security

✅ Embedded Servers
No need to install Tomcat separately. Spring Boot comes with embedded servers like:

Tomcat (Default)
Jetty
Undertow

✅ Production Ready
Includes built-in features like:

Health Checks
Metrics
Monitoring
Logging

✅ Minimal Configuration
Most configurations work out of the box using sensible defaults.

⚙️ How Spring Boot Works

1️⃣ You create a Spring Boot project.
2️⃣ Add the required starter dependencies.
3️⃣ Write Java classes.
4️⃣ Run the main application class.
5️⃣ Spring Boot automatically configures the application and starts the embedded server.
6️⃣ Your application is ready to serve requests.

🎯 Advantages

✔ Faster Development
✔ Less Configuration
✔ Easy Dependency Management
✔ Embedded Web Server
✔ Microservice Friendly
✔ Production Ready
✔ Easy Testing
✔ Large Community Support

📚 What I Learned Today

Difference between Spring and Spring Boot
Why Spring Boot is widely used
Auto Configuration
Starter Dependencies
Embedded Servers
Production-ready features
Basic project structure

This is just Day 1 of my Spring Boot journey. Looking forward to exploring REST APIs, JPA, Hibernate, Microservices, Security, and much more in the coming days! 💻☕

SpringBoot #Java #BackendDevelopment #Programming #LearningInPublic #JavaDeveloper #100DaysOfCode #SoftwareDevelopment #CodingJourney #Developers

My GitHub Streak Broke

Ashish prajapati — Sat, 20 Jun 2026 03:35:21 +0000

My GitHub Streak Broke, and It Taught Me an Important Lesson

Hi, I'm Anticoder03, a developer who genuinely likes seeing GitHub turn green.

I enjoy being consistent, building projects, learning new technologies, and contributing every day. Like many developers, I was dedicated to maintaining my GitHub streak.

But one day, it broke.

Not because I stopped loving development or because I lost motivation. I was simply exhausted from balancing classes, assignments, tests, and everything that comes with being a student.

The streak was gone.

At first, it felt disappointing. After spending so much time keeping it alive, losing it in a single day felt frustrating.

Then I asked myself an important question:

Does a GitHub streak really define me as a developer?

My answer is no.

Don't get me wrong. I know streaks have value. They encourage consistency, discipline, and the habit of showing up every day.

But they also have limits.

A number on GitHub cannot define how good you are as a developer.

I remember there were times when I would make meaningless commits or simply update my profile README just to keep the streak alive.

Looking back, I asked myself:

Did those commits actually matter?

Not really.

We are not bots designed to build streaks every day.

We are human beings.

We get tired.

We experience burnout.

We need breaks.

Sometimes, taking a step away from the screen is more productive than forcing ourselves to make a commit just for the sake of preserving a number.

I was so focused on maintaining the streak that I forgot the real purpose behind it:

Learning. Building. Growing.

So let me ask you another question.

If your streak disappears tomorrow, does that mean you suddenly lose all your value as a developer?

Absolutely not.

You still know the technologies you've learned.

You still know how to solve problems.

You still know how to overcome challenges.

Your skills don't disappear just because a green square does.

Sometimes, losing something teaches us something new.

And honestly, I'm glad my streak broke because it gave me a new perspective.

Will I build another streak?

Yes.

But this time, I want every contribution to have meaning. I want to create things that add value, teach me something, or genuinely satisfy me as a developer.

And if my streak breaks again in the future, it won't be because I failed.

It will be because I chose to rest.

I'm currently a Master's student learning AI and Data Science, and during this journey, I also took a long break from writing.

When I returned, the first thing I did was read the comments people had left on my previous posts. Their words gave me new energy to start writing again.

This post isn't only about technology.

It's about balance.

It's about remembering that behind every GitHub profile is a real person, not a machine.

So if you've been stressing over your streak lately, this is your reminder:

Build skills, not pressure.

Create value, not meaningless commits.

Protect your passion, because consistency is important, but sustainability is even more important.

At the end of the day, your GitHub profile is only a small reflection of your journey. It is not the definition of who you are as a developer.

Thank you for reading. ❤️

Why You Should Start Using Linux

Ashish prajapati — Sun, 14 Jun 2026 18:30:19 +0000

A few years ago, I thought Linux was only for hackers, programmers, and people who spent their entire day inside a terminal.

I was wrong.

Linux is one of the most powerful, flexible, and reliable operating systems available today, and it's becoming easier to use than ever before.

🚀 Performance Matters

Many Linux distributions use significantly fewer system resources than Windows. Older laptops and desktops that struggle with modern operating systems often feel surprisingly fast again after switching to Linux.

🔒 Better Security

Linux is built with security in mind. Its permission system, open-source nature, and lower malware targeting make it a strong choice for users who care about protecting their data.

💰 Completely Free

No expensive licenses. No activation keys. No forced upgrades.

Most Linux distributions are completely free to download, use, and customize.

🛠 Perfect for Developers

Whether you're working with web development, cloud computing, containers, AI, cybersecurity, or DevOps, Linux provides a development environment that's hard to beat.

Many of the technologies powering the internet run on Linux servers.

🎨 Freedom and Customization

Want your desktop to look minimal? Modern? Futuristic?

Linux gives you complete control over your system. You can customize nearly every aspect of your experience.

🌍 Amazing Community

One of Linux's biggest strengths is its community. Thousands of developers and enthusiasts contribute to improving the ecosystem and helping newcomers learn.

Is Linux Perfect?

No.

Some specialized software and certain games may still work better on Windows. There can also be a learning curve when you're getting started.

But if you're curious about technology, want more control over your computer, or simply want a faster and more secure experience, Linux is absolutely worth trying.

You don't have to switch overnight.

Start with beginner-friendly distributions like Ubuntu, Linux Mint, or Fedora. Experiment, explore, and learn.

You might discover that the operating system you've been looking for has been open source all along.

Why CRUD Apps Are Slowly Dying

Ashish prajapati — Wed, 20 May 2026 16:17:06 +0000

It’s been a while since I last wrote something technical.

Academics, projects, and work kept me busy for quite some time, but now I finally have a little space to start writing and building consistently again.

And honestly, there’s no better topic to restart with than this.

For years, beginner developers were told to build CRUD applications.

Todo apps
Inventory systems
Basic dashboards
Admin panels

And honestly, that made sense.

CRUD apps taught developers the fundamentals of software engineering:

✅ Databases
✅ APIs
✅ Authentication
✅ Backend logic
✅ Frontend integration

They became the foundation of modern web development.

But the Industry Has Changed

Today, AI can generate a basic CRUD application in minutes.

Need:

a login system?
a product dashboard?
REST APIs?
database models?
admin panels?

AI tools can now build most of it instantly.

The barrier to creating repetitive software has collapsed.

Does That Mean Software Engineering Is Dead?

No.

It means the value has shifted.

Companies are no longer impressed by applications that only perform:

Create → Read → Update → Delete

Because CRUD is becoming automation-friendly.

What matters now is:

System architecture
Scalability
Security
AI integration
Real-time systems
Developer experience
Performance optimization
Solving actual business problems

The Real Shift Happening in Tech

The developers who will thrive in the AI era are not the ones who can only build forms and tables.

They are the ones who can:

Design scalable systems
Build intelligent workflows
Understand infrastructure
Optimize performance
Integrate AI into products
Think beyond boilerplate code

CRUD Is Becoming a Feature — Not the Product

That’s the biggest shift modern developers need to understand.

Building software is no longer just about:

createUser()
updateProduct()
deleteTask()

It’s about building systems that are:

intelligent
scalable
secure
adaptive
user-focused

Skills That Matter More in 2026

Modern developers should start learning:

AI-assisted development
Cloud & Edge Computing
DevSecOps
Scalable backend architecture
WebSockets & real-time systems
Vector databases & RAG
Cybersecurity fundamentals

Final Thought

AI is not replacing developers.

It’s replacing repetitive development.

The future belongs to developers who can:

build systems, solve problems, and think architecturally.

And honestly?

That shift is already happening.

Feels good to finally start writing again.

🚀 From Excel to Web App: How I Built a Smart Assignment Management System for 125 Students

Ashish prajapati — Sun, 12 Oct 2025 06:46:38 +0000

👋 Introduction

Hey everyone! I’m Ashish, an MCA student — and, like most developers, I can’t resist turning simple problems into full-on coding projects. 😅

This semester, my Python professor gave me a new role:

“You’ll be the Python subject representative. Help manage assignments and track student progress.”

Sounds easy, right? Well, not quite.

My actual task was to monitor assignment progress for all 125 students, help the professor communicate updates to the class, and ensure that everyone’s assignments were properly submitted and tracked.

The professor suggested the old-school route —

“Just keep it all in an Excel sheet.”

But come on... I’m a developer. Why settle for spreadsheets when I can build something better?

So, I decided to turn this Excel nightmare into a full-fledged web application that could handle everything — tracking, monitoring, communication, and analytics — all in one place.

That’s how Assignment Checklist was born. 🎯

💡 The Idea: Turning Manual Management into a Smart Web App

What started as a “track assignments” task quickly turned into something much bigger:
A complete Assignment Management and Progress Monitoring System for the entire class.

The goal?

Make it easy for teachers and reps to manage assignments, monitor student performance, and communicate updates efficiently.

No Excel sheets. No manual status updates. Just clean, digital automation.

🧭 What Is “Assignment Checklist”?

Assignment Checklist is a web application designed for teachers, subject representatives, and students to simplify assignment tracking, class communication, and progress monitoring.

Here’s what it can do:

✨ Key Features

🗂️ Assignment Management
Create, edit, and organize assignments with due dates and descriptions.
👨‍🎓 Student Progress Tracking (125+ Students)
Track every student’s assignment status — from Uncompleted to Pending to Completed.
📢 Professor–Class Communication
The app helps professors and class reps share important updates or reminders directly — no separate WhatsApp chaos.
📊 Live Analytics Dashboard
Visualize class-wide progress with interactive Chart.js graphs and summaries.
🔒 Secure Editing
Only authorized users (professors or reps) can modify student records or mark completion.
📈 Reports & Insights
Get instant overviews of overall performance — who’s on track and who’s falling behind.
💬 Simplified Collaboration
Makes it easy for the professor and subject rep to coordinate and track class-wide assignment flow.

🧰 Tech Stack

Technology	Purpose
PHP (Vanilla)	Backend logic and data handling
MySQL	Database for assignments & student records
Bootstrap 5	Clean, responsive user interface
Chart.js	Interactive charts for progress tracking
FontAwesome	Icons to improve UI clarity
HTML/CSS/JavaScript	Frontend structure and interactivity
XAMPP	Local development and testing environment

I kept it simple, lightweight, and deployable on any basic server — perfect for quick academic tools.

⚙️ Architecture & Documentation (Coming Soon!)

To make it scalable and maintainable, I’m documenting everything, including:

🧾 DFD (Data Flow Diagram) – Data movement between modules
🧱 ER Diagram – Entity relationships for assignments, students, and subjects
🎭 Use Case Diagram – Role-based system interactions
⚡ API Documentation – For potential integration with student/teacher login systems

All documentation will soon be available on the GitHub repo.

🖥️ Preview & Source Code

📂 GitHub Repository:
👉 Assignment Checklist Web App

🌐Preview(Static):

🌐 Live Preview:
Coming soon! (Will update once deployed publicly.)

🔍 Behind the Scenes: What I Learned

This project taught me way more than I expected:

Excel doesn’t scale — especially for 125 students 😅
UI/UX matters — teachers don’t want to “figure things out”; it has to just work
Database design is the backbone — normalization and relationships made progress tracking smooth
Automation saves time — what took hours in Excel now happens instantly
Collaboration needs structure — the app became the single source of truth for all assignment updates

💬 Future Plans

I’m currently expanding Assignment Checklist into something even more powerful:

🔐 User Authentication: Separate dashboards for teachers, reps, and students
📱 Mobile-First UI: Redesign using Tailwind CSS for smoother mobile access
📬 Automated Notifications: Email/SMS alerts for pending or upcoming assignments
📤 PDF Reports: One-click export of student progress for professors
☁️ Cloud Deployment: Online hosting for real-time access

🤝 Contributing

I’d love your thoughts, feedback, or pull requests!

Fork the repo
Create your feature branch
Submit a PR with your improvement

You can also connect directly via GitHub.
If you like the project, leave a ⭐ on the repo — it really helps!

👨‍💻 About the Author

Hey, I’m Ashish (aka Anticoder03) — a coding enthusiast, anime lover, and someone who believes in building solutions that make everyday life easier.

I enjoy taking small, repetitive academic tasks and turning them into creative coding projects. This one’s a perfect example — what started as “track Excel assignments” became a real working system that helps 125 students and my professor every day.

💡 “If a task feels repetitive, automate it. If it feels boring, make it creative.”

🏁 Final Words

This project started as a small helper tool for my class, but it became something way bigger — a digital system that connects professors, reps, and students, making academic coordination smoother and more efficient.

If you’re a student, rep, or teacher tired of manually updating spreadsheets, take it from me — building your own web app might just be the best learning experience you’ll have this semester.

Thanks for reading! ❤️
Let’s connect and collaborate —
🔗 GitHub: Anticoder03

🧩 TL;DR

Built a full web app to replace Excel-based assignment tracking and class communication for 125 students using PHP, MySQL, and Bootstrap — complete with analytics, reports, and secure access.

Because… developers don’t just manage data — they build systems. 💪

🚀 Build Your Own Anime Explorer with HTML, Tailwind & the Jikan API!

Ashish prajapati — Thu, 26 Jun 2025 05:25:19 +0000

Are you an anime fan and a web dev? Why not combine both and build something epic? 💥

Introducing AnimeForge – a fully responsive web app that shows top-rated anime, movies, and even lets you search and view detailed info using the Jikan API (MyAnimeList Unofficial API). This project is built with HTML, Tailwind CSS, and JavaScript – no frameworks, just clean code and otaku energy! ⚔️👨‍💻

🌟 Features

✅ Explore top-rated anime series

✅ Browse anime movies

✅ View full anime details (genre, episodes, rating, synopsis, etc.)

✅ Dark / Light Theme Toggle 🌗

✅ Live Search functionality 🔍

✅ Responsive layout with Tailwind CSS

✅ Built with 🧠 and ❤️ by a fellow otaku

🧪 Tech Stack

📄 HTML5
🎨 Tailwind CSS
🔥 Vanilla JavaScript
📡 Jikan API – for anime data

🖼️ Screenshots

All UI is responsive and works great on mobile & desktop.

📂 Project Structure

AnimeForge/
├── index.html             # Top Anime Page
├── movies.html            # Movie Page
├── anime.html             # Anime Details Page
├── about.html             # About Me Page
├── theme_change.js        # Dark mode logic
├── screenshorst/          # Screenshots
└── README.md / LICENSE

🔧 How It Works

We use the Jikan REST API to fetch:

📺 Top anime series → https://api.jikan.moe/v4/top/anime?type=tv
🎬 Top anime movies → https://api.jikan.moe/v4/anime?type=movie
🔍 Search anime by name → https://api.jikan.moe/v4/anime?q={search}

All cards are dynamically generated using plain JS DOM magic. Clicking on a card opens anime.html?id=XXXX, fetches full info, and renders a beautiful detail view.

💡 Live Demo

🚀 https://animeforge.netlify.app/

📁 Or just clone it and run locally:

git clone https://github.com/Anticoder03/animeforge.git
cd animeforge
open index.html

🙋‍♂️ About the Developer

Hey! I'm Ashish Prajapati – a full-stack learner, anime lover, and terminal ninja from 🇮🇳
Built this as a fun side project to combine code + anime 👨‍💻⚔️

🐙 GitHub: Anticoder03
📸 Instagram: @ashiah03_prajapati

📜 License

Licensed under the MIT License. Use it, remix it, share it freely 🪄

“Anime taught me never to give up. Code made me unstoppable.” – Ashish (Anticoder03)

✨ Let’s Connect!

💬 Drop a comment if you liked it or want more anime-themed dev content.
💡 Thinking of building a React/GSAP version next — who’s in?

🚀 Chrome 135 Brings `::scroll-button()` and `::scroll-marker()` — Say Goodbye to JavaScript Carousels

Ashish prajapati — Fri, 13 Jun 2025 05:00:18 +0000

With the release of Chrome 135, web developers finally get access to two powerful new pseudo-elements:

::scroll-button()
::scroll-marker()

These pseudo-elements unlock fully functional carousels, sliders, and scrollable components without a single line of JavaScript.

TL;DR: These new features make interactive scroll experiences accessible, stylable, and keyboard-friendly — all from your CSS file.

🆕 What Are `::scroll-button()` and `::scroll-marker()`?

`::scroll-button()`

This pseudo-element renders scroll control buttons — left/right or up/down depending on the scroll direction. You can style them like any element, and users can interact with them out of the box.

`::scroll-marker()`

Think of this like scrollable radio dots — showing the position of each scroll snap point. They’re interactive, accessible, and visual indicators of your scroll progress.

Why They're a Big Deal

✅ Automatically accessible (screen reader + keyboard support)
✅ Pairs with scroll-snap-type
✅ No JavaScript needed
✅ Fully stylable using CSS

🔥 Real-World Carousel Example (JavaScript Fallback)

Here’s a simple JavaScript-based carousel (for legacy support), which will soon be entirely CSS-driven using ::scroll-button() and ::scroll-marker() in Chrome 135+:

👉 Live Demo Here

<!-- Full working demo with scroll + JS -->
<div class="carousel">
  <!-- Slides -->
</div>

[Full code example here... already shown above]

💡 What This Will Look Like in Pure CSS

.scroll-container::scroll-button(start) {
  content: '◀';
  position: absolute;
  left: 0;
  top: 50%;
  transform: translateY(-50%);
}

.scroll-container::scroll-button(end) {
  content: '▶';
  position: absolute;
  right: 0;
  top: 50%;
  transform: translateY(-50%);
}

No JavaScript. No event listeners. Just drop in a scroll-snap container, and the browser handles it.

🎯 Why This Matters

Using ::scroll-button() and ::scroll-marker() means:

✅ Native accessibility (no ARIA hoops to jump through)
✅ Built-in keyboard support
✅ Zero JS needed for sliders
✅ Smaller bundle sizes, better perf

🧪 Browser Support (as of Chrome 135)

Browser	Support
✅ Chrome 135+	Full
⚠️ Edge (Chromium)	Behind flag
❌ Firefox	Not yet
❌ Safari	Not yet

To enable the feature in Chrome manually:

chrome://flags/#enable-experimental-web-platform-features

🧠 Final Thoughts

This is a huge leap for native web components. Once Firefox and Safari catch up, we’ll finally have fully accessible carousels and sliders without needing bloated libraries or JS hacks.

Until then — progressive enhancement is your best friend.

🙋‍♂️ Let’s Talk!

What would you build with ::scroll-button()?

A portfolio carousel?
A product slider?
An onboarding walkthrough?

Should developers ditch JS sliders forever? Or is it too early?

👉 Try the full responsive carousel demo:
🔗 https://clever-cocada-9cd821.netlify.app/

Follow me for more frontend deep dives!
#CSS #HTML #Chrome135 #Frontend #WebDev #Accessibility #scrollbutton #nativecarousel #DevTo

DEV Community: Ashish prajapati

🚀 Spring Boot Journey – Day 6: Securing My Application with Spring Security

🛡️ Adding Spring Security

🔑 Understanding Authentication

1️⃣ Default Authentication (Auto Generated)

2️⃣ Username & Password in Properties File

3️⃣ Custom Authentication

✅ In-Memory Authentication

✅ DAO Authentication

🔒 Understanding Authorization

🔑 Password Encryption

👥 Custom UserDetailsService

🗃️ Role-Based Database Design

🔄 Security Flow

📚 What I Learned Today

💡 My Biggest Takeaway

🚀 What's Next?

#SpringBootJourney Day 6

🚀 Spring Boot Journey – Day 5: Building a Complete Product Management UI with CRUD Operations

🎯 What I Built Today

📝 Product Registration Form

🖼️ Image Upload

✏️ Updating Products

❌ Delete Functionality

🔍 Category-Based Search

🎨 Improving the UI

🔄 Complete Application Flow

📚 What I Learned Today

💡 My Biggest Takeaway

🚀 What's Next?

#SpringBootJourney Day 5

🚀 Spring Boot Journey – Day 4: Building My First UI with Thymeleaf & Tailwind CSS

🎯 Why Move Beyond Postman?

🛠️ Setting Up Thymeleaf

📦 Creating the Product Page

📄 Displaying Dynamic Data

🎨 Styling with Tailwind CSS

🔄 MVC Architecture in Action

Model

View

Controller

📚 What I Learned Today

💡 My Biggest Takeaway

🚀 What's Next?

#SpringBootJourney Day 4

🚀 Spring Boot Journey – Day 3: Mastering CRUD Operations, Lombok & JPA Query Methods

📌 What I Learned Today

📚 Adding Multiple Records

⚡ Making Code Cleaner with Lombok

🗄️ Repository Layer with Spring Data JPA

🔍 JPA Query Methods

⚠️ Exception Handling

🏗️ Project Architecture

📖 Key Concepts Covered Today

💭 My Takeaway

#SpringBootJourney Day 3

🚀 Spring Boot Journey – Day 2: Setting Up My Development Environment & Building My First REST API

🛠️ Development Environment

📦 Creating My First Entity: Product

🗂️ Understanding Spring Boot Project Structure

📌 Controller Layer

GET /get-all

POST /save-prod

📌 Repository Layer

📌 Service Layer

🔄 Request Flow

📚 Concepts I Learned Today

💭 My Takeaway

#SpringBootJourney Day 2

🚀 Spring Boot Journey - Day 1: Introduction to Spring Boot

📌 What is Spring Boot?

✨ Key Features

⚙️ How Spring Boot Works

🎯 Advantages

📚 What I Learned Today

SpringBoot #Java #BackendDevelopment #Programming #LearningInPublic #JavaDeveloper #100DaysOfCode #SoftwareDevelopment #CodingJourney #Developers

My GitHub Streak Broke

My GitHub Streak Broke, and It Taught Me an Important Lesson

Why You Should Start Using Linux

🚀 Performance Matters

GET `/get-all`

POST `/save-prod`

🆕 What Are `::scroll-button()` and `::scroll-marker()`?

`::scroll-button()`

`::scroll-marker()`