DEV Community: Shubham Pancharas

I Built InspireX to Fight the Short-Form Content Trap

Shubham Pancharas — Tue, 25 Aug 2026 04:35:11 +0000

Short-form content is incredibly good at one thing: keeping you scrolling.

You open Instagram or YouTube Shorts intending to watch one thing. Thirty minutes later, you've consumed dozens of videos and remember almost none of them.

I wanted to experiment with a different approach.

So I started building InspireX, a project focused on creating a more intentional way to discover and consume content.

The Problem

The problem isn't that short-form content is inherently bad.

The problem is the recommendation loop.

Most platforms optimize for metrics like:

Watch time
Engagement
Retention
More sessions
More content consumed

That creates a system where the easiest way to keep a user engaged is to continuously remove the friction between one piece of content and the next.

I wanted to explore the opposite question:

What if a content platform optimized for what the user actually gets from the content?

Instead of building another infinite feed, InspireX is an experiment around intentional content discovery.

What I'm Building

The initial idea behind InspireX is simple:

Help people discover useful and inspiring content without getting trapped in an endless consumption loop.

The project is still evolving, but the direction is to combine:

Curated content
A focused discovery experience
Better content organization
A cleaner interface
Eventually, AI-assisted content processing and automation

The interesting part isn't just building the UI.

It's figuring out what the product should actually optimize for.

Why I Built It

I originally approached this as a frontend project.

That quickly became insufficient.

Building another React interface is not particularly difficult anymore. AI can generate a decent-looking interface in minutes.

The harder questions are:

What problem am I actually solving?
Who has this problem?
What behavior am I trying to change?
What should the product optimize for?
How do I know whether the solution is useful?
How do I get real people to use it?

Those questions turned InspireX from a simple coding project into a product experiment.

Engineering Lessons

One of the biggest lessons so far has been that building the feature is only one part of building a real product.

I've had to deal with things that aren't particularly glamorous:

Deployment

Getting the application deployed is easy.

Getting it to behave correctly in production is another story.

Routing, caching, asset handling, refresh behavior, and environment configuration can all create problems that don't appear during local development.

A project that works perfectly on localhost is not necessarily a working product.

Humanity continues to discover this the hard way.

SEO

I also started looking more seriously at technical SEO.

That meant dealing with things such as:

Page titles
Meta descriptions
Canonical URLs
Indexability
Route configuration
Crawlability
Duplicate content
Sitemap configuration
Production rendering

This forced me to think about the application as something that has to be discovered, not just something that has to be built.

Debugging

Another important lesson has been learning to distinguish between:

"The code is broken."

and

"The code works, but the environment around it is behaving differently than expected."

That sounds obvious.

It wasn't obvious when I started.

I've had issues where the application itself was functioning correctly but caching or deployment behavior made it look broken.

Learning to debug systematically instead of randomly changing code has probably been more valuable than learning another framework.

Where AI Fits

I'm also exploring how AI and automation could extend InspireX.

One possible direction is a pipeline where long-form content can be:

Discovered
Evaluated
Extracted
Summarized
Converted into smaller pieces
Categorized
Presented through a focused discovery experience

For example, useful long-form YouTube content could potentially become structured, concise pieces of content instead of requiring users to consume an entire video just to discover whether it is useful.

But I'm deliberately treating this as an experiment rather than blindly adding AI because every project apparently needs an AI sticker now.

The AI needs to solve a real bottleneck.

The Bigger Goal

InspireX is also part of a bigger goal I'm working toward.

I don't want to only become someone who can build interfaces.

I want to become someone who can take a problem from:

Problem → Research → Product → Engineering → Deployment → Distribution → Feedback → Iteration

That's a much harder skill set.

And it is much more useful than being able to reproduce another dashboard from a tutorial.

What's Next

The next stage for InspireX is less about adding random features and more about validating the core idea.

I'm focusing on:

Improving the current user experience
Fixing production and SEO issues
Understanding what content users actually find valuable
Experimenting with content curation
Exploring AI-assisted content processing
Measuring actual usage instead of assuming the product is useful

The goal isn't to build the most complicated system.

The goal is to find out whether the underlying idea is worth building.

Final Thoughts

InspireX started as a project.

It's becoming an experiment in product development.

The biggest thing I'm learning is that software engineering doesn't end when the application runs.

A real product has to survive production, be discoverable, solve an actual problem, and give users a reason to come back.

That's the part I'm interested in learning.

And InspireX is currently my laboratory for doing exactly that.

check-out source code - https://github.com/pancharasshubham/inspirex

Basic JavaScript Through the Salaar Lens - Part 1

Shubham Pancharas — Tue, 11 Mar 2025 21:03:25 +0000

Introduction

JavaScript is one of the most powerful programming languages used for web development. But what if we could make learning JavaScript as thrilling as the world of Salaar? By drawing parallels between JavaScript concepts and the epic saga of Salaar, we can make learning more engaging and memorable. In this guide, we'll explore JavaScript through the lens of Salaar, comparing programming principles with warriors, clans, and battle strategies.

console.log("Welcome to JavaScript, the Salaar way!");

Story of var, let, and const in Salaar

Scope and Hoisting in the Kingdom of Khansaar

var – The Old Ruler of Khansaar

var is like the old ruling system of Khansaar—powerful but outdated.
It has function scope but no block scope, which can create unexpected results.
It is hoisted but initialized with undefined.

console.log(leader); // undefined (hoisted but not assigned)
var leader = "Old King of Khansaar";

let – The Strategic War General

let is like Deva, the rising warrior who follows structured war strategies.
It has block scope, meaning it is only accessible within the block it is declared in.
Unlike var, it is hoisted but not initialized.

if (true) {
  let warPlan = "Attack at dawn";
  console.log(warPlan); // Accessible inside the block
}
console.log(warPlan); // Error: warPlan is not defined

const – The Unshakable Khansaar Throne

const represents the Supreme Leader—unchanging and absolute.
It has block scope like let, but once assigned, its value cannot be changed.

const supremeLeader = "Khansaar King";
supremeLeader = "New King"; // Error: Cannot reassign a constant variable

Best Practices / Important Notes

Use console.table instead of console.log

accountId = 46
accountEmail = "rajmanar_ka_salaar@gmail.com"
accountPassword = "Maa@143"
accountCity = "Tinsukia"
accountState = "Assam"

console.table([accountId, accountEmail, accountPassword, accountCity, accountState])

Important Primitive Data Types

String (Represents text)

let warrior = "Deva"; // Name of the warrior

2.
Number (Represents numerical values)

let age = 35; // Deva's age

3.
Boolean (Represents true/false values)

let isKaaparWarrior = true; // Deva belongs to Kaapar clan

Undefined (A variable that has been declared but not assigned a value)

let weapon;
console.log(weapon); // undefined (Deva's weapon is not assigned yet)

5.
Null (Represents an empty or unknown value)

let throne = null;             // Throne of Khansaar is currently empty
console.log((throne));         // null 
console.log(typeof(throne));   // object

Symbol (Represents a unique value)

let uniqueID = Symbol("deva");
console.log(uniqueID); // Symbol(deva)
console.log(typeof(uniqueID)); // symbol

BigInt (Used for very large numbers beyond the safe integer limit)

let kingdomWealth = BigInt(9876543210123456789);

Best Practices / Important Notes

Type of Null Datatype is object. Refer to Null Datatype.

console.log(typeof(throne));     // object

"use strict"

Imagine Khansaar had a chaotic rule earlier where warriors could take any weapon without permission (non-strict mode). Now, with Rajamannar disciplined leadership (strict mode), every action is monitored and mistakes are punished.

"use strict";

warrior = "Deva"; // ❌ Error: warrior is not defined (undeclared variable)
console.log(warrior);

Without "use strict", JavaScript would assume warrior is a global variable and run without error. But in strict mode, it prevents such mistakes, enforcing proper variable declarations.

Data Types Conversions

1.
String to Number

Deva wants to convert his warrior rank (stored as a string) into a number.

let rank = "1"; 
let numericRank = Number(rank);  
console.log(numericRank); // Output: 1

2.
Number to String

Vardha wants to convert his power level into a string.

let powerLevel = 9000;
let powerStr = String(powerLevel);
console.log(powerStr); // Output: "9000"

3.
Boolean to Number

A warrior’s loyalty (true or false) is converted into a number.

let isLoyal = true;
let loyalNumber = Number(isLoyal);
console.log(loyalNumber); // Output: 1

4.
Number to Boolean

If an army size is 0, it means no warriors. Any non-zero value means they exist.

let armySize = 100;
let hasArmy = Boolean(armySize);
console.log(hasArmy); // Output: true

5.
String to Boolean

A non-empty string means a warrior exists.

let warriorName = "Deva";
console.log(Boolean(warriorName)); // Output: true

let emptyName = "";
console.log(Boolean(emptyName)); // Output: false

What is a web server ?

Shubham Pancharas — Sun, 08 Sep 2024 19:53:45 +0000

Web server refers to both hardware and software.

A web server is not like a supercomputer or any other large machine.

** Basically web server is another computer that acts as a host to store webpage files and software. **

A web server is like a special computer that stores all the parts of a website, like the text, images, and styles. It connects to the Internet so people can visit the website from their own devices.

The web server also has software that knows how to handle requests when someone types a web address (URL) in their browser. It understands these requests and sends back the right content from the website to the person’s device so they can see the webpage.

A web server is a computer that helps people visit websites. It has special software called an HTTP server that understands website addresses (URLs) and uses a language called HTTP to show pages in your browser. When you type a website's address, the server sends the right pages to your device so you can see them.

When your browser asks for a file from a web server, it sends a request using HTTP. The server then finds the file and sends it back to your browser so you can view it. If the file isn't there, the server tells you with a “404 error,” which means the page can’t be found.